Facilitation: Separating Curiosity From Judgment
What This Concept Is
In a review, participants make two kinds of statements:
- Curiosity. "Why did you choose Postgres over DynamoDB here?" The asker wants to understand the reasoning, and is open to being convinced.
- Judgment. "Postgres is the wrong choice for this workload." The asker has already concluded and is now defending.
Both are legitimate, but they require different facilitation. Curiosity should come first, unblock the room's understanding, and often resolves the disagreement on its own. Judgment should come second, as an explicit, named position - not smuggled into a question.
The facilitator's job is to keep the two separated: to invite curiosity early, hold judgment until understanding is shared, and make sure the author is not defending when they should be explaining.
Why It Matters Here
Reviews fail when judgment arrives too early. The author goes into defense mode, the reviewer doubles down, and the rest of the room watches. No amount of prepared agenda survives this pattern.
Good facilitation prevents it by sequencing: first understanding, then evaluation, then decision. This also produces better ADRs, because the Context section ends up reflecting what the room actually asked, not just what the author remembered.
Concrete Example
A 30-minute review, well-facilitated.
Minute 0-5. Author restates the problem. Facilitator asks the room: "Does anyone's understanding of the problem disagree with that?" One reviewer says yes and rephrases. Author confirms or corrects.
Minute 5-15. Curiosity round. Facilitator explicitly asks for "questions where you are not yet sure of the answer." Reviewers ask:
- "Why Kafka over Redpanda for the transport?"
- "What did you try before deciding this was the problem?"
- "What is the constraint from ops that I am not seeing?"
Author answers. No one critiques during this round. Facilitator intervenes if a "question" is actually a judgment ("Wouldn't it be better to just ..."), gently: "Let's hold that as a judgment for the next round."
Minute 15-25. Judgment round. Each reviewer states their position explicitly:
- "I am convinced."
- "I am not convinced: I think the latency cost is underestimated, here is why."
- "I am indifferent; I trust the team on this."
Author responds, point by point, in writing.
Minute 25-30. Decision. Facilitator asks: "Given what was said, what is the decision?" The room names it. ADR is updated before the call ends.
The shape of the meeting is the facilitator's work. The substance is everyone else's.
Common Confusion / Misconception
"Facilitation means being neutral on content." It does not mean neutral on the content; it means not advocating during facilitation. You can facilitate a review where you also have a position - but separate the roles explicitly, or hand off facilitation when you speak.
"Let the conversation flow naturally." "Natural" conversations in review meetings default to the loudest person deciding. Structure exists to counteract that.
"A tough reviewer is a good reviewer." A reviewer who is only judgment and no curiosity produces defensive authors, who produce worse ADRs, which produce worse decisions.
How To Use It
Facilitation moves:
- Name the phase. "We are in the curiosity round." "We are in the judgment round." This alone changes behavior.
- Redirect mislabeled contributions. "You phrased that as a question - is it a question or a position?"
- Write as you go. Anything important goes into the ADR or the review notes within the minute it is said.
- Force a decision statement. Before the meeting ends, say the decision out loud and check it against the written ADR.
Self-check: if your review meetings produce "we should schedule a follow-up" more than once in a row, facilitation is the broken link.
Check Yourself
- Rewrite this as a curiosity question and a judgment statement: "Isn't it kind of risky to put the cache in front of the auth call?"
- Why is it a bad sign when the author spends more time talking than the reviewers during the judgment round?
- What does it mean if you finish a review meeting and the ADR is unchanged?