View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Operations A3 Problem Solving |  Facilitation Consensus Workshop |
|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 2-5 | 5-30 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | A3 Report, Action Plan, Root Cause Analysis | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | LeanProblem solvingCoachingOperations | FacilitationConsensusWorkshopAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
