intermediate
2 min answer
A cross-team design session for a shared capability produces no decision after ninety minutes. What went wrong in the facilitation?
Show the full answer Hide the answer
The usual causes
- No stated decision. A session convened to "discuss the approach" will discuss the approach. A session convened to "choose between A and B by the end of the hour" behaves differently.
- No pre-read, so the first forty minutes are spent establishing shared context that a document would have provided asynchronously.
- The wrong people, either missing someone whose objection will block it, or including so many that nobody can contribute.
- No decision-maker identified, so the session is looking for consensus, and consensus among eight people on an architectural trade-off is rare.
- Unresolved disagreement about the problem, which surfaces as disagreement about solutions and cannot be resolved at the solution level.
What good facilitation does
- Circulate a pre-read with the problem, the constraints and the options, and require it to be read.
- State the decision to be made and who will make it, at the start.
- Separate divergence from convergence. Generate options first without evaluating; evaluate afterwards. Mixing them means the first option proposed is defended rather than compared.
- Timebox each part, and enforce it.
- Capture the decision and the dissent in the room, before people leave, since reconstruction afterwards produces a different decision from the one people believe was made.
- End with owners and dates, or the session's output is a shared feeling.
The specific move for a stalled session
Ask what would change each person's mind. If nobody can answer, the disagreement is about values and the session should stop and route to a decision-maker. If they can, the session's output is an experiment rather than a decision, and that is a legitimate and often better outcome.
The preparation that matters most
Talk to the two or three people whose objection would block it, beforehand. Most objections are surfaced and absorbed there, and the session then confirms a decision rather than discovering a conflict — which is what distinguishes a productive design session from a long one.