Nine Project Management Fallacies: I

Nan pushed the door open, and she and Trish stepped out of the conference center into the morning air. On their first break from the off-site meeting, they hadn't quite yet relaxed from the pressure cooker that was the final stretch of Marigold, their latest project. It hadn't gone well, and they were all spending three days trying to figure out what happened.

"So what do you think?" Nan opened.

"I've been to off-sites before," said Trish. "But this is the first time I've felt hopeful that truth would come out."

Nan agreed. "Me too. I liked the bit about myths and fallacies."

Nan sat down on one of the plastic chairs. Trish sat too. "But knowing these fallacies," she asked, "won't we just get better at fooling ourselves? If we could get any better which I seriously doubt."

Nan smiled. "Well, I think his point was that by naming the fallacies, it gets harder to use them."

And Nan is right about that. By naming the fallacies, the patterns become obvious to everyone, which deters us from using them. Here's Part I of a little catalog of the fallacies of project management. For Part II, see "Nine Project Management Fallacies: II," Point Lookout for December 14, 2005.

The Fallacy of Positivism

The Fallacy of Positivism holds that if we believe we can accomplish something, we're more likely to actually accomplish it; and inversely, if we express doubts about accomplishing something, we're less likely to execute it successfully.

This fallacy is especially tempting to leaders who want to motivate reluctant teams to attempt (or keep trying to do) the impossible. They're using it as a tool of manipulation.

All things being equal, it's probably helpful to have a positive attitude. But Truth is most important. Be positive when it's appropriate, and express doubts when they're real and relevant. Both staying positive and expressing doubt inappropriately can lead to catastrophe.

The Bad Actor Fallacy

If a team exhibits a repeated pattern of dysfunction, we commit the Bad Actor Fallacy when we assume that one single team member is the likely cause of the problem.

Isolating the cause of a team problem to a single individual is tempting because it suggests that dealing with that individual can resolve the problem. No need for messy and expensive team interventions; no need for involving more than one person.

While it's possible for a single individual to keep a team in a state of dysfunction, more typically many individuals contribute to team problems. Team performance is an attribute of the team's system, and the organization in which that team is embedded.

One more fallacy is perhaps most common: the Purity Fallacy, which holds that we are personally pure: we never use fallacies ourselves. We all use them, of course — we're human. The trick is to catch yourself when you do.  Next in this series  Top    Next Issue

Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Project Management:

Nonlinear Work: When Superposition Fails

Much of the work we do is confounding, because we consistently underestimate the effort involved, the resources required, and the time required to get it done. The failure of superposition can be one reason why we get it wrong.

Projects as Proxy Targets: I

Some projects have detractors so determined to prevent project success that there's very little they won't do to create conditions for failure. Here's Part I of a catalog of tactics they use.

Power Distance and Risk

Managing or responding to project risks is much easier when team culture encourages people to report problems and to question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk.

The Planning Dysfunction Cycle

Some organizations consistently choose not to allocate enough resources or time to planning for their most complex undertakings. Again and again, they decline to plan carefully enough despite the evidence of multiple disappointments and chaotic performance. Resource contention and cognitive biases conspire to sustain this cycle of dysfunction.

Vendor Mismanagement

When we outsource knowledge work to vendors, we expect to achieve the desired result with less risk and uncertainty than if we did the work ourselves. But mission creep, mission retrenchment and employee capture can lead to less welcome results.

See also Project Management and Critical Thinking at Work for more related articles.

Forthcoming issues of Point Lookout

Coming May 15: Should I Write or Should I Call?

After we recognize the need to contact a colleague or colleagues to work out a way to move forward, we next must decide how to make contact. Phone? Videoconference? Text message? There are some simple criteria that can help with such decisions. Available here and by RSS on May 15.

And on May 22: Rescheduling Collaborative Work

Rescheduling is what we do when the schedule we have now is so desperately unachievable that we must let go of it because when we look at it we can no longer decide whether to laugh or cry. The fear is that the new schedule might come to the same end. Available here and by RSS on May 22.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info