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 Pre-Mortem |  DevOps Blameless Postmortem |  Decision Making Force Field Analysis |  Decision Making Constraint Analysis |
|---|---|---|---|---|
Purposedifferent | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20–45 min | 30-90 min | 45-90 min | 30-90 min |
Participantsdifferent | Small cross-functional group | 3-12 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Postmortem Doc, Action Items, Timeline | Force Field Map, Change Levers, Risk Notes | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | RiskDecisionFailurePlanning | Site Reliability EngineeringIncidentLearningReliability | ChangeDecisionStrategy | ConstraintsDecisionPlanningOptions |