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 Game Day |  DevOps Incident Command |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 20–45 min | Halber Tag | As needed | 45-90 min |
Participantsdifferent | Small cross-functional group | 5-20 | 4-15 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Simulation Notes, Gaps List, Updated Runbooks | Incident Log, Action Tracker, Stakeholder Updates | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskDecisionFailurePlanning | ResilienceOperationsIncident | IncidentOperationsReliability | AssumptionsRiskDecisionDiscovery |