View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Force Field Analysis |  DevOps Blameless Postmortem |  Operations Family Tree Analysis |  Decision Making OODA Loop |
|---|---|---|---|---|
Purposedifferent | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 45-90 min | 30-90 min | 2-4 h | 15-60 min je Zyklus |
Participantsdifferent | 3-12 | 3-12 | 2-6 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Postmortem Doc, Action Items, Timeline | Family Tree Diagram, Pattern Notes, Systemic Measures | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ChangeDecisionStrategy | Site Reliability EngineeringIncidentLearningReliability | Root causePatternsIncidentSystemic | DecisionChangeLearningStrategy |