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 |  Engineering Hypothesis-Driven Troubleshooting |  Operations Family Tree Analysis |  Operations Barrier 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. | 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. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Mehrere Tage bis Wochen | 30-240 min | 2-4 h | 2-4 h |
Participantsdifferent | 2-6 | 1-6 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Family Tree Diagram, Pattern Notes, Systemic Measures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Root causeSafetySystemicIncident | TroubleshootingProblem solvingDiagnosis | Root causePatternsIncidentSystemic | Root causeSafetyIncident |