Review Facilitation Techniques

The architecture review is not a presentation. It is a structured decision-making session. The facilitator's job is not to present the architecture — the pre-read handles that. The facilitator's job is to guide the room toward decisions: which design option to select, which trade-offs to accept, which risks to mitigate. Every minute spent on walkthrough is a minute not spent on decision-making.

1. Pre-Read Accountability Distribute the architecture document 48 hours before the review. Begin the review by asking: "Does anyone need a walkthrough, or are we ready to discuss the open decisions?" If more than two attendees need a walkthrough, the pre-read failed — either the document was unclear or the attendees did not prioritize it. Address the root cause for next time, provide the walkthrough this time, and accept the time cost.
2. Decision Queue Open with the list of decisions that need to be made. "We have three decisions today: the communication pattern between order and inventory, the data store for the analytics service, and whether to build or buy the notification system." The decision queue focuses the room. Every discussion is tethered to a specific decision. Tangents are captured in a parking lot and addressed after the queue is clear.
3. Disagree and Commit When the room cannot reach consensus, the decision authority — the architect or the technical lead — makes the call. Dissenting opinions are documented in the ADR. The team commits to the decision even if they disagree. "I disagree with this approach because I believe the eventual consistency will create user-facing issues, but I commit to implementing it and we will revisit at the 90-day review trigger." Documented dissent is healthy. Unresolved disagreement is paralysis.