Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 10, Issue 18;   May 5, 2010: Problem Not-Solving

Problem Not-Solving

by

Group problem solving is a common purpose of meetings. Although much group problem solving is constructive, some patterns are useless or worse. Here are some of the more popular ways to engage in problem not-solving.
A Lockheed L-1011 Tristar aircraft like the one flown by Eastern Airlines flight 401

A Lockheed L-1011 Tristar aircraft like the one flown by Eastern Airlines flight 401. On the night of December 29, 1972, Eastern Airlines flight 401 crashed into the Florida Everglades on approach to the airport in Miami, causing 101 fatalities. As is the case in most disasters, the outcome was the result of multiple contributing factors, including the design and operation of the autopilot. Still, one of the contributing factors was the problem-solving approach used by the cockpit crew when they discovered that the landing gear indicator light would not illuminate to indicate that the landing gear were down and locked. Believing that the autopilot was guiding the aircraft, the crew focused essentially all its attention on solving the indicator light problem, and did not realize until too late that the autopilot had disengaged. In a now-classic example of Rearranging the Deck Chairs, group dynamics — abetted by cockpit control system design flaws — led the crew to focus on a less-important aspect of the overall problem of landing the aircraft safely. Photo by U.S. National Aeronautics and Space Administration courtesy Wikimedia.

The purpose of many meetings is solving specific problems. We bring people together to collaborate because we seek contributions from a variety of sources, and because we hope people will think in new ways. Usually, it works.

But creativity can be misdirected. Just as we can combine our talents, skills, and knowledge to solve problems, we can collaborate to avoid solving those same problems.

If we educate ourselves in advance about the common approaches to not-solving problems, we can more easily recognize these patterns, even when we're participating in them ourselves. Here are a few of the more common ways groups avoid solving the problems they believe they're solving.

Even though these tactics are group phenomena, I've given the name Oscar to the obstructor, and the names Paul and Pam to proposers of solutions.

Yes-but
When Paul proposes a potential solution, Oscar says, "Yes, but…" and then reveals additional information that rules out Paul's proposal.
One motivation for Yes-But can be Oscar's sense that since he's stumped by the problem, solution by the group — or by anyone else — reflects badly on him.
Deflecting
When Pam proposes an approach, rather than addressing it or commenting on it, Oscar raises another problem, possibly unrelated to Pam's idea, thereby deflecting the group from considering the proposal.
This technique Just as we can combine our talents,
skills, and knowledge to solve
problems, we can collaborate to avoid
solving those same problems
is especially useful when Oscar doesn't immediately know how to apply Yes-But. When he can't see anything wrong with Pam's idea — or when he simply doesn't understand it — he can still deflect the group's attention.
Rearranging the deck chairs
Sometimes the group collaborates in addressing something that's either unimportant or irrelevant or both. This special case of Deflecting is sometimes known as "Rearranging the Deck Chairs on the Titanic."
Groups that often do this might be lacking in leadership, but replacing the leader rarely helps. It's usually a group dysfunction.
Diversion
In Diversion, Oscar (or somebody else) uses anger, conflict, humor, or other techniques to focus attention anywhere but on the proposed solution. One favorite: "What's for lunch?"
This approach is useful when Oscar can't think of another irrelevant problem for people to consider.
I'm so smart
People dedicated to this pattern apply their intelligence — creatively — to demonstrating their intelligence. For instance, Oscar might withhold key information until needed to disprove the viability of a proposed solution. Or he might "info-dump" — emit a stream of information at such a rate, so filled with jargon and acronyms, and so disorganized as to be indigestible. In that form, the pattern might be called "You can't catch up to me."
This style of participation in group problem solving is best treated as a performance issue.

If talking about these patterns in your team — outside the context of a problem-solving session — doesn't make your next session much more productive, your team might have a serious group process problem. Try solving that problem first. Get help if necessary. Go to top Top  Next issue: Unwanted Hugs from Strangers  Next Issue

101 Tips for Effective MeetingsDo you spend your days scurrying from meeting to meeting? Do you ever wonder if all these meetings are really necessary? (They aren't) Or whether there isn't some better way to get this work done? (There is) Read 101 Tips for Effective Meetings to learn how to make meetings much more productive and less stressful — and a lot more rare. Order Now!

Your comments are welcome

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

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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 Problem Solving and Creativity:

PizzaCritical Thinking and Midnight Pizza
When we notice patterns or coincidences, we draw conclusions about things we can't or didn't directly observe. Sometimes the conclusions are right, and sometimes not. When they're not, organizations, careers, and people can suffer. To be right more often, we must master critical thinking.
Dunlin flock at Nelson Lagoon, AlaskaProject Improvisation as Group Process
When project plans contact reality, things tend to get, um, a bit confused. We can sometimes see the trouble coming in time to replan thoughtfully — if we're nearly clairvoyant. Usually, we have to improvise. How a group improvises tells us much about the group.
A waterfall and spray cliff in the mountains of VirginiaDecisions: How Looping Back Helps
Group decision making often proceeds through a series of steps including forming a list of options, researching them, ranking them, reducing them, and finally selecting one. Often, this linear approach yields disappointing results. Why?
Robert S. McNamara as Secretary of the U.S. Department of DefenseThe McNamara Fallacy
The McNamara Fallacy is the idea that measuring properly chosen attributes of inputs and outputs provides all we need for decisions about organizational and human performance. And we can safely ignore anything that can't be measured. It doesn't work.
Charles Goodhart delivers the keynote speech in the 2012 Long Finance Spring ConferenceGoodhart's Law and Reification
Goodhart's Law, applied to organizations, is an observation about managing by metrics. When we make known the goals for our metrics, we risk having the metrics lose their ability to measure. The risk is elevated when we try to "measure" abstractions.

See also Problem Solving and Creativity and Effective Meetings for more related articles.

Forthcoming issues of Point Lookout

Three gears in a configuration that's inherently locked upComing April 24: Antipatterns for Time-Constrained Communication: 1
Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.
A dangerous curve in an icy roadAnd on May 1: Antipatterns for Time-Constrained Communication: 2
Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.

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:

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

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, 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.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
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.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.