View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations MORT Analysis |  Architecture Architecture Decision Record |  Architecture Request for Comments |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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 | High | Low | Medium | Medium |
Timedifferent | Mehrere Tage bis Wochen | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 2-4 h |
Participantsdifferent | 2-6 | 1-3 | 3-20 Reviewer | 2-6 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeSafetySystemicIncident | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | Root causePatternsIncidentSystemic |