View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Blameless Postmortem |  Operations MORT Analysis |  Decision Making Force Field Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 30-90 min | Mehrere Tage bis Wochen | 45-90 min | 2-4 h |
Participantsdifferent | 3-12 | 2-6 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Force Field Map, Change Levers, Risk Notes | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | Root causeSafetySystemicIncident | ChangeDecisionStrategy | Root causePatternsIncidentSystemic |