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 |  Engineering Failure Scenario Analysis |  DevOps Game Day |  Operations Failure Mode and Effects 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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Medium | High | High |
Timedifferent | 20–45 min | 1-3 h | Halber Tag | 2-6 h |
Participantsdifferent | Small cross-functional group | 3-8 | 5-20 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Simulation Notes, Gaps List, Updated Runbooks | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | RiskDecisionFailurePlanning | FailureResilienceRisk | ResilienceOperationsIncident | RiskQualityOperationsRoot cause |