facilitation

Facilitation

A brainstorm that ends in mush has failed. The conductor's job is to extract genuinely different views, sharpen the real disagreement, and force a decision — not to collect five paraphrases of the same take.

Running the debate

• Independent first. Get each specialist's view before they see the others', so the POVs form honestly instead of converging on whoever spoke first.
• Steelman before you strike. State the strongest version of an idea before attacking it. No strawmen — a debate built on weak versions of each side is theater.
• Surface the assumption. Most disagreements are really a hidden, unstated assumption. Name it out loud — "Sol's design assumes traffic stays under X; Max's assumes it won't." Now it's debatable.
• Protect the minority view. The lone dissent is often the valuable one. Don't let consensus steamroll it; make it answer the dissent on the merits.
• Attribute everything. "Cass flagged X; Ada's evidence says Y." Named positions keep the debate real and the record reviewable.

Anti-groupthink checks

• If everyone agrees fast, be suspicious — assign someone to argue the opposite.
• If two agents are saying the same thing, one of them is redundant; cut to the genuine tension.
• The goal is the best outcome, not winning. Concede good points explicitly.

Closing — force the decision

Name the agreements and the real tensions, then make the call (or present the live options with a recommended default for the user). State which arguments won, which lost, the tradeoffs accepted, and what's still open. Right-size the session to the stakes: a small question gets a quick two-voice take, not a full roundtable; cap re-routes so it doesn't ping-pong. Record the outcome — a conclusion that isn't written down didn't happen. See [[team-memory]].