Nine Project Management Fallacies: IV

Nan picked up the last chunk of cookie and ate it. Peter and Trish had long ago finished theirs, but Nan liked making cookies last. "The critical thinking fallacies were my favorites," she said. "I like learning how to think more clearly."

Peter sipped his coffee. "Mmm." He swallowed. "But how do we avoid those fallacies?"

Nan had an idea. "Maybe we should inspect our project plans, like we inspect components."

Trish was intrigued. "Yeah, and I know what I'd put at the top of the checklist."

"OK, I'll bite," said Peter. "What?"

Trish was ready. "The Nine Project Management Fallacies."

Not a bad idea. These last three fallacies (Part IV of a little catalog of the fallacies of project management) are errors of critical thinking. For Part III, see "Nine Project Management Fallacies: III," Point Lookout for December 28, 2005.

The Normative Fallacy

This fallacy holds that when we ask some people their opinions, and most of them agree, then they're correct. Usually we select people non-randomly, choosing those who will give us desirable answers, or those we can trust, or those of high rank.

Non-random polling might provide comfort, but it's hardly scientific, and it almost always leads to biased conclusions.

To get truly useful polling data, you must poll people randomly.

The Availability Heuristic

In risk management, we often estimate the probabilities of certain events. We're using the Availability Heuristic [Tversky 1973] when we estimate these probabilities by sensing the difficulty of imagining or understanding the string of events that lead to the risk.

For instance, when we ask people whether death resulting from being attacked by a shark is more or less likely than from being hit by falling airplane parts, they usually answer that death by shark attack is more likely. Actually, death from being hit by falling airplane parts is 30 times more likely, but people are fooled because it's easier to imagine shark attacks, which are more common.

Estimating probabilities is unlikely to produce reliable results. For this reason, the Availability Heuristic is usually considered an example of a cognitive bias. Use real data, or use huge error bars.

The Grandiosity Fallacy

Confronting a problem, we sometimes address a generalization of the problem instead, hoping to solve a host of similar problems, and thereby solving the original problem almost "for free." Rarely does the reality match the wish.

Grandiosity usually generates two kinds of trouble. First, it's often more expensive and time-consuming than originally estimated. Second, the people of the organization rarely want the general solution. If they did, they probably would have sought it in the first place.

Sometimes customers don't know the value of the general solution, and telling them about it might produce a better outcome. But usually they want only what they asked for. Work with them on that first.

Track the incidence of these nine fallacies in your organization. Use them to inspect project plans. Probably your projects will have fewer surprises, or at least you'll be just a little less likely to be hit by falling airplane parts. First 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!

For more on cognitive biases, see "The Focusing Illusion in Organizations," Point Lookout for January 19, 2011.

Footnotes

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.

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:

Make a Project Family Album

Like a traditional family album, a project family album has pictures of people, places, and events. It builds connections, helps tie the team together, and it can be as much fun to look through as it is to create.

Toxic Projects

A toxic project is one that harms its organization, its people or its customers. We often think of toxic projects as projects that fail, but even a "successful" project can hurt people or damage the organization — sometimes irreparably.

Personnel-Sensitive Risks: I

Some risks and the plans for managing them are personnel-sensitive in the sense that disclosure can harm the enterprise or its people. Since most risk management plans are available to a broad internal audience, personnel-sensitive risks cannot be managed in the customary way. Why not?

Ten Approaches to Managing Project Risks: II

Managing risk entails coping with unwanted events that might or might not happen, and which can be costly if they do happen. Here's Part II of our exploration of coping strategies for unwanted events.

Yet More Obstacles to Finding the Reasons Why

Part III of our catalog of obstacles encountered in retrospectives, when we try to uncover why we succeeded — or failed.

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

Forthcoming issues of Point Lookout

Coming August 22: Dealing with Credit Appropriation

Very little is more frustrating than having someone else claim credit for the work you do. Worse, sometimes they blame you if they get into trouble after misusing your results. Here are three tips for dealing with credit appropriation. Available here and by RSS on August 22.

And on August 29: Please Reassure Them

When things go wildly wrong, someone is usually designated to investigate and assess the probability of further trouble. That role can be risky. Here are three guidelines for protecting yourself if that role falls to you. Available here and by RSS on August 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenXHJgyCsPbhYFkPiSner@ChacDhceXwzADlwOrHCXoCanyon.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, USD 11.95)
• Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
• Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
• Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)

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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.