June 25, 2008	Volume 8, Issue 26
Recommend this issue to a friend Join the Friends of Point Lookout HTML to link to this article…	Archive: By Topic    By Date Links to Related Articles Sign Up for A Tip A Day!
Create a perpetual bookmark to the current issue
| Follow @RickBrenner	Random Article

Unintended Consequences

by Rick Brenner

Sometimes, when we solve problems, the solutions create new problems that can be worse than the problems we solve. Why does this happen? How can we limit this effect?

ou and your team have just solved a problem. It was difficult. It took some creative thinking. The solution now in place, forward progress resumes — for a while. Suddenly, a new problem appears. Progress halts, and you're back in deep yogurt.

Ice on the launch pad on January 28, 1986, the day of the last Challenger Launch (STS-51-L). The unusually cold weather was well beyond the tolerances for which the rubber seals of the solid rocket boosters were approved, and it most likely caused the O-ring failure. In meetings on the night before the launch, Morton Thiokol engineers and engineering managers confronted the problem. One of the candidate solutions was to recommend that the launch be scrubbed. Another was to recommend launch despite the weather. Politics, budget and schedule undoubtedly played roles in their decision. Nevertheless, it would be a mistake to view that decision as an aberration. NASA, as an organization, was seriously flawed at the time, and had made other decisions of equally questionable merit. See, for example, Howard S. Schwartz, Narcissistic Process and Corporate Decay, New York University Press, 1992. () Photo by Michael Hahn, courtesy U.S. National Aeronautics and Space Administration.

It's a pattern so familiar that we have a name for it: "unintended consequences." The term arose in the context of economics, but the concept is so useful that it has been applied in politics, game design, engineering — everywhere.

In problem solving, we can use the concept to help limit the risk that a solution to one problem creates a new one.

Probably there are numerous ways for solutions to create new problems, but here are a few of those more common in my own experience and the experiences of my clients.

Missing knowledge or incorrect knowledge

We didn't know what we needed to know to get it right the first time, or some of what we "knew" was wrong.

Test what you do know for completeness and correctness. How do you know what you know?

Dogma, politics, budget, and schedule

We tend to be biased in favor of candidate solutions that are consistent with our cherished beliefs, or which satisfy political, budgetary, or schedule constraints; we tend to eliminate from consideration, prematurely, those that do not. And sometimes, when these factors get in the way, we don't even see some workable solutions.

What are the dogma, political, budgetary, or schedule factors affecting your problem? How biased are you?

Dirty work

We tend to be biased in favor of
candidate solutions that are consistent
with our cherished beliefs or with
external organizational constraints

When the full solution requires that we grapple with parts of the problem that we find distasteful, dull, or pedestrian, we can be so averse to that part of it that we do a bad job of it.

What part of what you need to do is distasteful or low status work?

Subtlety and difficulty

Even when we have access to all the information we need, the problem can be difficult to solve properly. A solid solution might require seeing the world from perspectives with which we have little experience.

Get fresh eyes. Talk to people who have the perspective you need.

Illusory similarity

Sometimes we notice similarities between the problem at hand and problems previously solved. Then, without stopping to prove that they are similar enough, we apply methods that worked in the past.

Look for proof that this problem is close enough to the problem previously solved. If you can't find proof, ask whether the differences really matter.

If you extend this list for your problem space, beware the unintended consequence of overconfidence. However complete your list becomes, unintended consequences might still emerge.  Top    Next Issue

Love the work but not the job? Bad boss, long commute, troubling ethical questions, hateful colleague? This ebook looks at what we can do to get more out of life at work. It helps you get moving again! Read Go For It! Sometimes It's Easier If You Run, filled with tips and techniques for putting zing into your work life. Order Now!

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.

What Haven't I Told You?

When a project team hits a speed bump, it often learns that it had all the information it needed to avoid the problem, sometimes months in advance of uncovering it. Here's a technique for discovering this kind of knowledge more systematically.

Figuring Out What to Do First

Whether we belong to a small project team or to an executive team, we have limited resources and seemingly unlimited problems to deal with. How do we decide which problems are important? How do we decide where to focus our attention first?

Poverty of Choice by Choice

Sometimes our own desire not to have choices prevents us from finding creative solutions. Life can be simpler (if less rich) when we have no choices to make. Why do we accept the same tired solutions, and how can we tell when we're doing it?

Finger Puzzles and "Common Sense"

Working on complex projects, we often face a choice between "just do it" and "wait, let's think this through first." Choosing to just do it can seem to be the shortest path to the goal, but it rarely is. It's an example of a Finger Puzzle.

Help for Asking for Help

When we ask for help, from peers or from those with organizational power, we have some choices. How we go about it can determine whether we get the help we need, in time for the help to help.

See also Problem Solving and Creativity, Emotions at Work and Critical Thinking for more related articles.

Coaching services

Get the e-book!

• Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
• Get 2003-4 in Why Dogs Wag Their Tails (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 ten years (2001-2010) in Ten Years of Point Lookout (PDF, USD 28.95)

Public seminars

Person-to-Person Communication for Project Managers

When we talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program you'll learn a model of inter-personal communications that can help you stay out of the ditch. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here are some upcoming dates for this program:

• Download to
  your calendarDes Moines, IA: February 16, Breakfast Meeting, Central Iowa Chapter of The Project Management Institute. Register now.
   
• Download to
  your calendarDes Moines, IA: February 16, Lunch Meeting, Central Iowa Chapter of The Project Management Institute. Register now.
   
• Houston, Texas: May 8, Monthly Meeting, Houston Chapter of the Project Management Institute.
   
• Houston, Texas: May 9, Monthly Meeting, Houston Chapter of the Project Management Institute.
   

The Race to the South Pole: The Power of Agile Development

On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:

• Download to
  your calendarSt. George Banquet Hall, Kitchener, Ontario: March 6, Dinner Meeting, Canada's Technology Triangle Chapter of the Project Management Institute. Register now.
   

Human-Centered Risk Management

Most of us can assess technological risks, but risks related to human behavior tend to resist our best efforts. This session provides a framework for evaluating risks related to the behavior of individuals, teams, organizations and people generally. Human-centered risk differs from technological or market risk, because objective evaluation requires acknowledging personal and organizational limitations and failures. Since some of those limitations and failures might apply to the people assessing the risks, or to their superiors, there's a tendency to deny them or to explain them away. Our approach examines capability, organization, context, risk mitigation, and workplace politics. It has tools for guiding the assessment and management of human-centered risk, and we show how to extend these tools to suit your situation. You'll learn how to identify sources of risk in human behavior; recognize systemic and individual barriers to acknowledging risk; assess the effects of organizational turbulence; determine the risk associated with inappropriate internal risk transfer; estimate the effects of team dysfunction, toxic conflict and turnover; and measure the impact of workplace politics. Read more about this program. Here's an upcoming date for this program:

• Download to
  your calendarMITRE, in Bedford, Massachusetts: March 20, Monthly Meeting, Boston SPIN. Register now.
   

The Race to the South Pole: Ten Lessons for Project Managers

On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

• Columbia, Missouri: May 17, Full-Day Workshop, Mid Missouri Chapter of the Project Management Institute.
   

Project Management in Fluid Environments

Most people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what's coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help project managers who work in fluid environments. Read more about this program. Here's an upcoming date for this program:

• Columbia, Missouri: May 17, Monthly Meeting, Mid Missouri Chapter of the Project Management Institute.
   

The Politics of Meetings for People Who Hate Politics

There's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here's an upcoming date for this program:

• Rochester, New York: May 24, Professional Development Day, Rochester Chapter of the Project Management Institute.