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 |  Decision Making Assumption Surfacing |  Operations 5 Whys |  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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. | 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 | Low | Medium |
Timedifferent | Mehrere Tage bis Wochen | 45-90 min | 15-30 min | 2-4 h |
Participantsdifferent | 2-6 | 2-8 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Assumption List, Critical Assumptions, Learning Plan | Root cause notes, Countermeasures | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeSafetySystemicIncident | AssumptionsRiskDecisionDiscovery | Root causeIncidentLeanProblem solving | Root causePatternsIncidentSystemic |