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 Architecture Decision Record |  Decision Making Argument Mapping |  Operations MORT Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 15-45 min | 1-3 h | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 1-3 | 1-8 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |