Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 14, Issue 16;   April 16, 2014: Design Errors and Groupthink

Design Errors and Groupthink

by

Design errors cause losses, lost opportunities, accidents, and injuries. Not all design errors are one-offs, because their causes can be fundamental. Here's a first installment of an exploration of some fundamental causes of design errors.
Ice on Challenger's launch pad hours before the launch

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 that led to the Challenger loss. Groupthink probably provides a solid explanation for the flawed launch decision, but it can do much more. The string of decisions that led to the design of the space shuttle itself might also have benefited from scrutiny from the perspective of groupthink. Even more important, though, is the organizational design of NASA. There was a belief both inside NASA and out that it was an elite organization that always got things right. That belief is one of the fundamental characteristics that makes groups and organizations susceptible to groupthink. Only after the loss of Challenger did the question of the design of NASA come into focus. See, for example, Howard S. Schwartz, Narcissistic Process and Corporate Decay, New York University Press, 1992. (Order from Amazon.com) Photo by Michael Hahn, courtesy U.S. National Aeronautics and Space Administration.

Design is the articulation of intent to achieve a goal, including plans for executing that intention. We're engaged in design whenever we devise products, services, procedures, tests, policies, legislation, campaigns — just about anything in the modern knowledge-oriented workplace. And when we design, we risk error. Our design might not achieve all we hoped, or it might not achieve the goal at all. Or we might discover that the goal we were aiming for isn't what we actually wanted. So much can go wrong that attaining even a measured success sometimes feels thrilling.

Design errors are more common than we imagine. When a system produces disappointing results, we cannot always distinguish design errors from user errors or implementation errors. And we don't always know whether the system was being used in an environment for which it was designed. That's why we sometimes mistakenly attribute system failures to something other than design error, even when design errors played a role.

Because we usually use the term error for undesirable outcomes, the language we use to describe design errors carries connotations that limit our thinking. For this discussion, we use error to mean merely unintended as opposed to unintended and unfavorable. With this in mind, when a design "goes wrong" we mean that it didn't achieve the goal, or that we discovered an even more desirable goal. We must therefore classify as design errors those exciting surprises that bring welcome results. Typically, we take credit for these as if we intended them, but their sources are often simple design errors.

The Design errors are more
common than we imagine
kind of design errors I find most fascinating are those that arise from the way humans think and interact. Let's begin with one of the most famous of group biases, groupthink.

Groupthink happens when groups fail to consider a broad enough range of alternatives, risks, interpretations, or possibilities. Groups are at elevated risk of groupthink if they aren't diverse enough, or lack sufficient breadth of experience, or feel infallible, or want to preserve their elite status, or have an excessive desire for order.

For example, if an elite review team is pressed for time and must review two designs — one by an elite development team, and one by a less accomplished team, it might decide to do a less-than-thorough job on the work of the elite development team so as to make time for careful review of the work of the less-accomplished development team. Because the review team values its reputation for getting work done on time, and because it feels an affinity for the elite developers, an error in the elite developers' work can squeeze through. That might not be a bad thing, of course. Some design errors produce favorable outcomes. Such beneficial errors are rare, but we ought not dismiss the possibility out of hand.

We'll continue next time with an examination of more group biases.  Next in this series Go to top Top  Next issue: Design Errors and Group Biases  Next Issue

303 Secrets of Workplace PoliticsIs every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info

Your comments are welcome

Would you like to see your comments posted here? rbrenALGIHPwelBNwWoafner@ChacNnMnkkCoqimEvTQZoCanyon.comSend me your comments by email, or by Web form.

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 Problem Solving and Creativity:

Wheelchair basketballBonuses
How we deal with adversity can make the difference between happiness and something else. And how we deal with adversity depends on how we see it.
Problem solving often requires collaborationTen Tactics for Tough Times: Part I
When you find yourself in a tough spot politically, what can you do? Most of us obsess about the situation for a while, and then if we still have time to act, we do what seems best. Here's Part I of a set of approaches that can organize your thinking and shorten the obsessing.
Tenacious under full sailThe Solving Lamp Is Lit
We waste a lot of time finding solutions before we understand the problem. And sometimes, we start solving before everyone is even aware of the problem. Here's how to prevent premature solution.
The Johari WindowAssumptions and the Johari Window: Part II
The roots of both creative and destructive conflict can often be traced to the differing assumptions of the parties to the conflict. Here's Part II of an essay on surfacing these differences using a tool called the Johari window.
COL Michael Wyly, USMC (ret)Call in the Right Expert
When solving a problem is beyond us, we turn to experts, but sometimes we turn to the wrong experts. That can make the problem even worse. Why? How does this happen? What can we do about it?

See also Problem Solving and Creativity and Project Management for more related articles.

Forthcoming issues of Point Lookout

Balancing talk time and the value of the contributionComing March 29: Virtual Blowhards
Controlling meeting blowhards is difficult enough in face-to-face meetings, but virtual meetings present next-level problems, because techniques that work face-to-face are unavailable. Here are eight tactics for controlling virtual blowhards. Available here and by RSS on March 29.
kudzu enveloping a Mississippi landscapeAnd on April 5: Listening to Ramblers
Ramblers are people who can't get to the point. They ramble, they get lost in detail, and listeners can't follow their logic, if there is any. How can you deal with ramblers while maintaining civility and decorum? Available here and by RSS on April 5.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenNwZwLNfVaMZNjvaKner@ChackMrIBhbFvATStoqcoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

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

Changing How We Change: The Essence of Agility
MasteChanging How We Change: The Essence of Agilityry of the ability to adapt to unpredictable and changing circumstances is one way of understanding the success of Agile methodologies for product development. Applying the principles of Change Mastery, we can provide the analogous benefits in a larger arena. By exploring strategies and tactics for enhancing both the resilience and adaptability of projects and portfolios, we show why agile methodologies are so powerful, and how to extend them beyond product development to efforts of all kinds. Read more about this program. Here are some upcoming dates for this program:

Conflict Resolution Skills for Leaders
ConflConflict Resolution Skills for Leadersict is inherent in collaborative work. When conflict is constructive, it produces better outcomes. When it's destructive, it can be an insurmountable obstacle to success. In this program, we explore the connections between the outcomes of collaboration and conflict in both of its forms. And we emphasize the skills needed most by leaders. The leader's task is to manage conflict so as to ensure that the group achieves its objective with its capacity to collaborate intact, or even enhanced. Rick Brenner shows team leaders and team sponsors the techniques they need to manage team conflict for relationship safety and better outcomes. Read more about this program. Here's an upcoming date for this program:

Influencing Outcomes Without Authority
Your Influencing Outcomes Without Authorityability to influence others — whether upward, downward, laterally, or within a team — always depends on both the quality of your relationships with the people you influence, and on your perception and their perception of your personal power. In this program, Rick Brenner shows you the techniques for making things happen not by using formal organizational power, but by using informal, personal power. Read more about this program. Here's an upcoming date for this program:

Strategies for Leading Teams in Hard Times
When Strategies for Leading Teams in Hard Timesa project team is on task, the contributions of leaders are important, and little noticed. Sometimes the team encounters unexpected difficulty, or requirements change, or budgets are reduced, or any of a number of other things might happen. In these cases, the leader must make or facilitate decisions about how to respond or how to revise the plan. We get through it somehow. Hard times are something else altogether. Despondency, disillusionment, resource shortages, unexpected and severe failure of the plan, and toxic conflict can erode morale. How can leaders deal with such situations? Read more about this program. Here's an upcoming date for this program:

Strategies for Technical Debt: A Workshop for Enterprise Leaders
TechnTechnical Debt Management for Enterprise Leadersical debt is more than mere IT jargon. It's a metaphor that refers to the accumulation of technical artifacts that really ought to be retired, replaced, rewritten, re-implemented, or, if absent, created. We can find technical debt in almost any system, including those that seem to be working well. So what's the problem? The problem is the "interest charges." Systems carrying technical debt are more difficult to maintain, more difficult to extend or enhance, and more difficult to use, than they would be if we "retired" the debt. This engaging and eye-opening program points the way to a path that leads your organization out of technical debt, to make it more adaptable, more transformable, and more agile. Read more about this program. Here's an upcoming date for this program:

Creating High Performance Virtual Teams
Many Creating High Performance Virtual Teamspeople experience virtual teams as awkward, slow, and sometimes frustrating. Even when most team members hail from the same nation or culture, and even when they all speak the same language, geographic dispersion or the presence of employees from multiple enterprises is often enough to exclude all possibility of high performance. The problem is that we lead, manage, and support virtual teams in ways that are too much like the way we lead, manage, and support co-located teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance. Read more about this program. Here's an upcoming date for this program:

The Race to the South Pole: Ten Lessons for Project Managers
On 14The Race to the Pole: Ten Lessons for Project Managers 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 organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
21st Century Business TravelAre your business trips long chains of stressful misadventures? Have you ever wondered if there's a better way to get from here to there relaxed and refreshed? First class travel is one alternative, but you can do almost as well (without the high costs) if you know the tricks of the masters of 21st-century e-enabled business travel…
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.