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 Process Mapping |  Operations MORT Analysis |  Operations Family Tree Analysis |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 h | Mehrere Tage bis Wochen | 2-4 h | 20-45 min |
Participantsdifferent | 3-10 | 2-6 | 2-6 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic | LearningOperationsImprovement |