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 |  Engineering Hypothesis-Driven Troubleshooting |  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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 | 30-240 min | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 1-6 | 5-30 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Consensus Clusters, Theme Titles, Priority Areas |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | TroubleshootingProblem solvingDiagnosis | FacilitationConsensusWorkshopAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
