practice
Facilitation
Running a discussion so that a group reaches a decision — a distinct skill from having the best answer.
Definition
Facilitation is guiding a group to an outcome. For architects it applies to design workshops, review sessions, incident reviews and cross-team disputes — situations where the answer must be owned by the group rather than supplied by an individual.
Before the session
- State the decision to be made in the invitation. A session without a stated decision produces a discussion.
- Invite the people who can decide, and no more. A room of twelve makes no decisions.
- Circulate the material in advance, and expect it to have been read. A session spent presenting is a session not spent deciding.
- Find the objections beforehand. A review where everyone sees the design for the first time will not conclude.
During
- Separate divergence from convergence. Generate options first, evaluate second. Mixing them means the first idea is critiqued and the rest are never offered.
- Make the trade-offs visible rather than the preferences. "Option A costs latency and buys simplicity" moves a discussion forward; "I prefer A" does not.
- Manage the loudest voice, and actively draw out the quietest — who is frequently the one closest to the system.
- Timebox, and say what happens if time runs out.
- Write on a shared surface as you go, so the group is reacting to the same artefact rather than to their recollection of what was said.
- Name disagreements explicitly rather than smoothing them. An unspoken disagreement resurfaces during implementation.
Ending
- State the decision, the owner and the next action, out loud, before anyone leaves.
- Record it within the day, while it is accurate.
- Note what was not decided and when it will be, so the open items do not vanish.
The trap for architects specifically
Facilitating and advocating at once. If you have a strong view, say so explicitly and hand the facilitation to someone else — otherwise the group correctly suspects the process is steering toward your answer, and the outcome will not be owned.
Failure scenarios
- No decision stated, so the session is a discussion.
- Too many people, so nobody decides.
- The senior person's view adopted by default, with dissent unspoken.
- No record, so it is re-litigated in a fortnight.
- Facilitator advocating, so the process is distrusted.
Interview question
"Two teams disagree strongly about a boundary. How do you run the session that resolves it?"