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 8D Problem Solving |  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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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 | High | Medium |
Timedifferent | Mehrere Tage bis Wochen | 45-90 min | 1-6 Wochen | 2-4 h |
Participantsdifferent | 2-6 | 3-10 | 4-10 | 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 | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeSafetySystemicIncident | RolesResponsibilityTeamFacilitation | QualityProblem solvingRoot cause | Root causePatternsIncidentSystemic |