Seven More Planning Pitfalls: I

In the first three posts in this series, I described seven thought patterns that cause individual planners to think in ways that lead to plans with inherent weaknesses. These phenomena influence planners even when planners have enough time and resources to execute the planning exercise. They include widely held but inapplicable beliefs, several cognitive biases, and several organizational influences. But for plans devised by teams, there are additional effects that cause trouble as well. These phenomena are related to how teams think collectively. Let's begin with Group Polarization and Trips to Abilene.

Group polarization

Group polarization is the tendency of groups to adopt positions more extreme than any of their members would adopt if acting individually. When group members learn that their own more radical inclinations are shared by other group members, they tend to assess those inclinations as validated. This experience propagates through the group, in an emergent fashion, each member influencing the others, until the more radical position is firmly held by all. Members then feel comfortable abandoning any remaining reluctance or doubt.

Planning teams are susceptible to group polarization. For example, when assessing risks for particular options, they must make judgments as a group. Judging a risk as high or low can determine whether or not they adopt a particular plan option. Other vulnerable judgments include vendor selection, staff assignments, effort estimates — almost anything the team must decide.

Secret ballots provide one approach to mitigating group polarization. But the safety secret ballots provide is limited, because the team must necessarily engage in open discussion. For protection in open discussion, the team can appoint a "Curmudgeon Team" to oppose radical positions as they appear. Read about curmudgeon teams.

Trips to Abilene

In an insightful work, The Abilene Paradox, Jerry Harvey describes how a group can commit to a course that no group member favors. [Harvey 1988] When a group takes a "trip to Abilene," nobody feels that the group is behaving sensibly. Because they all feel that everyone else favors the group's choice, no one questions it openly. The group then takes action that no member agrees with.

Planning teams, like all teams, are susceptible to the Abilene Paradox. They are especially susceptible when one of the team members is much more influential or powerful than the others. For the moment, call that person Gandalf. If Gandalf makes an off-hand comment that others interpret as a statement of preference, they might express support for it. And in an analogy to Group Polarization, the entire group might adopt Gandalf's idea enthusiastically, even though no one is enthusiastic about it. But unlike Group Polarization, the idea might not be radical. In some sense a trip to Abilene can be the "meh" form of Group Polarization.

To a Group polarization and trips
to Abilene are examples of
emergent group behavior that
can lead to unworkable planslimited extent, groups can inoculate themselves against trips to Abilene by learning about the phenomenon and then adopting an intervention protocol consisting of three steps: noticing your own doubts, inquiring when you're uneasy, and checking for the Abilene itinerary. Read more about trips to Abilene.

Three other emergent phenomena that lead groups astray are False Consensus, Groupthink, and Shared Information Bias. We'll explore how they can affect planners next time.  Next in this series

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!

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.

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 Cognitive Biases at Work:

Self-Serving Bias in Organizations

We all want to believe that we can rely on the good judgment of decision makers when they make decisions that affect organizational performance. But they're human, and they are therefore subject to a cognitive bias known as self-serving bias. Here's a look at what can happen.

Scope Creep, Hot Hands, and the Illusion of Control

Despite our awareness of scope creep's dangerous effects on projects and other efforts, we seem unable to prevent it. Two cognitive biases — the "hot hand fallacy" and "the illusion of control" — might provide explanations.

Scope Creep and Confirmation Bias

As we've seen, some cognitive biases can contribute to the incidence of scope creep in projects and other efforts. Confirmation bias, which causes us to prefer evidence that bolsters our preconceptions, is one of these.

Motivated Reasoning

When we prefer a certain outcome of a decision process, we risk falling into a pattern of motivated reasoning. That can cause us to gather data and construct arguments that erroneously lead to the outcome we prefer, often outside our awareness. And it can happen even when the outcome we prefer is known to threaten our safety and security.

Risk Acceptance: One Path

When a project team decides to accept a risk, and when their project eventually experiences that risk, a natural question arises: What were they thinking? Cognitive biases, other psychological phenomena, and organizational dysfunction all can play roles.

See also Cognitive Biases at Work and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming May 8: Antipatterns for Time-Constrained Communication: 3

Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 3 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing past experiences of participants. Available here and by RSS on May 8.

And on 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.

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