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 Family Tree Analysis |  Decision Making OODA Loop |  DevOps Blameless Postmortem |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h | 15-60 min je Zyklus | 30-90 min | 15-30 min |
Participantsdifferent | 2-6 | 1-8 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Family Tree Diagram, Pattern Notes, Systemic Measures | Situation Assessment, Decision Loop, Action Updates | Postmortem Doc, Action Items, Timeline | Root cause notes, Countermeasures |
Tagsno overlap | Root causePatternsIncidentSystemic | DecisionChangeLearningStrategy | Site Reliability EngineeringIncidentLearningReliability | Root causeIncidentLeanProblem solving |