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 |  Decision Making OODA Loop |  Operations Family Tree Analysis |  DevOps Blameless Postmortem |
|---|---|---|---|---|
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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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 an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Mehrere Tage bis Wochen | 15-60 min je Zyklus | 2-4 h | 30-90 min |
Participantsdifferent | 2-6 | 1-8 | 2-6 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Situation Assessment, Decision Loop, Action Updates | Family Tree Diagram, Pattern Notes, Systemic Measures | Postmortem Doc, Action Items, Timeline |
Tagsno overlap | Root causeSafetySystemicIncident | DecisionChangeLearningStrategy | Root causePatternsIncidentSystemic | Site Reliability EngineeringIncidentLearningReliability |