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 |  Agile 4Ls Retrospective |  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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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 |
Timedifferent | Mehrere Tage bis Wochen | 45–75 min | 2-4 h |
Participantsdifferent | 2-6 | Team members involved | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | 4Ls Board, Learning Themes, Improvement Actions | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Root causeSafetySystemicIncident | RetrospectiveLearningReflectionTeam | Root causePatternsIncidentSystemic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
