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 |  Decision Making Force Field Analysis |  Operations MORT 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. | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 30-90 min | 45-90 min | Mehrere Tage bis Wochen |
Participantsdifferent | 3-12 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Force Field Map, Change Levers, Risk Notes | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | ChangeDecisionStrategy | Root causeSafetySystemicIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
