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 Fault Tree Analysis |  DevOps Game Day |  Operations MORT Analysis |
|---|---|---|---|---|
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 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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 1-3 h | 2-6 h | Halber Tag | Mehrere Tage bis Wochen |
Participantsdifferent | 3-8 | 3-8 | 5-20 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Simulation Notes, Gaps List, Updated Runbooks | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | FailureResilienceRisk | RiskRoot causeSafety | ResilienceOperationsIncident | Root causeSafetySystemicIncident |