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 |  DevOps Blameless Postmortem |  Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Mehrere Tage bis Wochen | 15-60 min je Zyklus | 30-90 min | 45-90 min |
Participantsdifferent | 2-6 | 1-8 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Situation Assessment, Decision Loop, Action Updates | Postmortem Doc, Action Items, Timeline | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Root causeSafetySystemicIncident | DecisionChangeLearningStrategy | Site Reliability EngineeringIncidentLearningReliability | ChangeDecisionStrategy |