When groups solve problems collaboratively, discussions sometimes develop chaotic patterns of considering what the solution must do, when it must be completed, how much it will cost, who will lead the work, what additional information is required, and on and on.
Chaotic wandering through this tangle can set in almost before the group realizes it. And once the chaos comes to their attention, disagreements about how to manage it become the next obstacles. Here are some suggestions for dealing with the tangles.
- Focus first on options for "what"
- The "what" of a candidate solution is its essential concept — the strategy it embodies. For each candidate solution, devise a few words or phrases that capture its essence. Then without evaluating the solution's merits, without considering costs, schedule, or any of its other attributes, move on to the next candidate.
- The effort of crafting concept statements for candidate solutions has a high and immediate return. It creates consensus about what each candidate is, it stimulates thinking about new candidates, and it brings clarity and definition to the next steps of the discussion.
- Consider the politics of leader choice
- Sometimes people contend for the leadership role for a solution; sometimes they run from it. Ownership of the solution effort can generate analogous responses. In either case, the opinions about solution attributes voiced by candidates for leader or owner might be more closely related to their agendas with respect Using rough estimates to
rank order candidate solutions
is probably not sensibleto leadership or ownership, than they are related to the attributes under discussion. - Examine the contributions of leader or owner candidates and their advocates very closely. Accepting their comments at face value might be unwise.
- Use budget and schedule considerations as screens
- The costs and timelines of candidate solutions are usually difficult to project with any accuracy at this stage of the discussion. Estimation errors generally don't allow for comparison of different solutions, except when the differences are very dramatic.
- Using rough estimates to eliminate candidate solutions can be an effective way to focus the field of candidate solutions. Using these same estimates to rank order the surviving candidate solutions is probably less sensible.
- Consider the politics of bottlenecks
- Shortages of particular skills are the usual cause of bottlenecks. If a candidate solution requires contributions from people who are required elsewhere, selecting that solution likely will place the effort in direct contention with other efforts.
- Sometimes the people with rare skills enjoy or seek the contention; sometimes they abhor it. Any discussion of solutions requiring rare resources is therefore fundamentally political. Unless you have what's needed to entice, enlist, secure, and defend your claim to the people with rare skills, pursuing solutions that need them might be risky.
When addressing the problem of effective group problem solving, some of these same tangles arise, but the place to begin is still "what." Top Next Issue
Is 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? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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.
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:
- Annoyance to Asset
- Unsolicited contributions to the work of one element of a large organization, by people from another,
are often annoying to the recipients. Sometimes the contributors then feel rebuffed, insulted, or frustrated.
Toxic conflict can follow. We probably can't halt the flow of contributions, but we can convert it from
a liability to a valuable asset.
- Exploiting Failed Ideas
- When the approach you've been using fails, how do you go about devising Plan B? Or Plan C? Here are
some ways to find new approaches by examining failures.
- Is the Question "How?" or "Whether?"
- In group decision making, tension sometimes develops between those who favor commitment to the opportunity
at hand, and those who repeatedly ask, "If we do that, how will we do it?" Why does this happen?
- Design Errors and Group Biases
- Design errors can cause unwanted outcomes, but they can also lead to welcome surprises. The causes of
many design errors are fundamental attributes of the way groups function. Here is Part II of our exploration.
- Brainstorming and Speedstorming: I
- Recent research suggests that brainstorming might not be as effective as we would like to believe it
is. An alternative, speedstorming, might have some advantages for some teams solving some problems.
See also Problem Solving and Creativity and Problem Solving and Creativity for more related articles.
Forthcoming issues of Point Lookout
- Coming January 22: Storming: Obstacle or Pathway?
- The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.
- And on January 29: A Framework for Safe Storming
- The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed