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 |  Operations MORT Analysis |
|---|---|---|---|---|
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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h | 1-3 h | Mehrere Tage bis Wochen |
Participantsdifferent | 3-20 Reviewer | 2-6 | 1-8 | 2-6 |
Formatdifferent | Async | Workshop + 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 | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Root causeSafetyIncident | SensemakingDecisionRationale | Root causeSafetySystemicIncident |