openskills.info

Collaborative Problem Solving

Using a group to reach a better answer than any one member would have found.

A group solving a problem together has one real advantage over a capable individual: it holds more independent information and more ways of being wrong, so between them they can catch errors none of them would catch alone. That advantage is fragile. It disappears the moment people stop contributing what they actually think — because the first confident suggestion has set the direction, because disagreeing feels expensive, or because the group is optimizing for finishing the meeting. Collaborative problem solving is mostly the work of keeping that from happening: agreeing what the problem is, getting genuinely different options on the table before narrowing, and making it cheap to say the inconvenient thing.

Mostly Harmless

The Premature Converger

Hears the first plausible suggestion and treats it as the plan, largely because a decision has now technically been made and everyone can go. The suggestion may well be fine. Nobody will ever find out, because the two better options that existed were never said aloud, their owners having correctly read the room as being finished with the divergent part of the discussion. Records the meeting as efficient, which by the only metric anyone applied it was.

The Requirements Archaeologist

Responds to any sign of convergence by reopening the question of what the problem really is. Each time the group nears a decision, unearths an assumption from an earlier layer that must first be examined. The excavation is always defensible and never concludes. Six weeks in, the team knows the problem extremely well and has not begun to solve it, a condition the Archaeologist regards as rigour and everyone else has stopped regarding at all.

The Afterwards Objector

Holds, throughout the meeting, the single observation that would have changed the decision, and says nothing, the moment for it never feeling quite right. Raises it afterward in a message to one person, or at the next meeting once the work has started. The objection is correct. It is now also expensive, and arrives with a faint implication that the group should have thought of it, which is true, and would have been easier had anyone said so.

The Whiteboard Mirage

Facilitates the group to a diagram of real beauty — boxes, arrows, colour-coding, a legend — and mistakes the diagram for a decision. Photographs it. The photograph is shared, admired, and never converted into anything anybody owns. The problem remains exactly as unsolved as before, now with excellent documentation, and the session is remembered fondly by everyone who attended it as the day things finally came together.

Scenarios

Someone proposes a solution in the first two minutes and the group starts refining it. What would you do — refine it, since it's reasonable, or ask for two more options first so there's something to compare it against?

You're the most senior person in the room and you have a view. What would you do — state it early so the group has direction, or hold it until others have gone, knowing your view will otherwise become the anchor everyone works from?

A quiet team member gives you the decisive objection privately after the meeting. What would you do — act on it and move on, or also find out what made saying it in the room feel like a bad idea?

Takeaway

  • Agree what problem you're solving before anyone proposes a solution. Most stuck discussions are two people solving different problems.
  • Get more than one real option on the table before narrowing. A single proposal isn't a decision, it's a default.
  • If you're the senior voice, speak last. Your early opinion costs the group the independent views it was there to collect.
  • Ask directly for the objection: "what would make this fail?" is easier to answer than "any concerns?"
  • Turn the outcome into an owner and a next step. A diagram is not a decision and a decision without an owner is not a plan.

Go deeper

Awesome Links