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 |  Facilitation Responsibility Poker |  Operations Root Cause Analysis |  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. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | 45-90 min | 1-4 h | 2-4 h |
Participantsdifferent | 2-6 | 3-10 | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Responsibility Map, Role Agreements, Open Questions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeSafetySystemicIncident | RolesResponsibilityTeamFacilitation | Root causeProblem solvingQualityIncident | Root causePatternsIncidentSystemic |