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 5 Whys |  Agile Example Mapping |  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. | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | 15-30 min | 30-60 min | 2-4 h |
Participantsdifferent | 2-6 | 2-6 | 3-7 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Root cause notes, Countermeasures | Example Map, Acceptance Criteria, Open Questions | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeSafetySystemicIncident | Root causeIncidentLeanProblem solving | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causePatternsIncidentSystemic |