View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Operations Failure Mode and Effects Analysis |  Operations Fault Tree Analysis |  DevOps Game Day |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to 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. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 1-3 h | 2-6 h | 2-6 h | Halber Tag |
Participantsdifferent | 3-8 | 3-10 | 3-8 | 5-20 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | FMEA Table, Risk Priority, Mitigation Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Simulation Notes, Gaps List, Updated Runbooks |
Tagsno overlap | FailureResilienceRisk | RiskQualityOperationsRoot cause | RiskRoot causeSafety | ResilienceOperationsIncident |