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 |  Operations Family Tree Analysis |  Architecture Architecture Decision Record |  Operations 5 Whys |
|---|---|---|---|---|
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. | 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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Mehrere Tage bis Wochen | 2-4 h | 15-45 min | 15-30 min |
Participantsdifferent | 2-6 | 2-6 | 1-3 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures |
Tagsno overlap | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving |