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 Start Stop Continue |  Operations Family Tree Analysis |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Mehrere Tage bis Wochen | 30-60 min | 2-4 h | 45–75 min |
Participantsdifferent | 2-6 | 3-12 | 2-6 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Start Stop Continue Board, Improvement Actions | Family Tree Diagram, Pattern Notes, Systemic Measures | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Root causeSafetySystemicIncident | RetrospectiveImprovementTeamReflection | Root causePatternsIncidentSystemic | RetrospectiveLearningReflectionTeam |