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 Barrier Analysis |  Decision Making Argument Mapping |
|---|---|---|---|
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 risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 2-6 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Root causeSafetyIncident | SensemakingDecisionRationale |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
