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 ABC Analysis |  DevOps Game Day |  Decision Making Pre-Mortem |
|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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. |
Complexitydifferent | Low | High | Low |
Timedifferent | 30-60 min | Halber Tag | 20–45 min |
Participantsdifferent | 1-5 | 5-20 | Small cross-functional group |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | ABC Classification, Focus Rules, Control List | Simulation Notes, Gaps List, Updated Runbooks | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | PrioritizationOperationsPortfolio | ResilienceOperationsIncident | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
