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 Fishbone Diagram |  Operations Root Cause 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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 | Low | Medium | High |
Timedifferent | 1-3 h | 30-60 min | 1-3 h | Halber Tag |
Participantsdifferent | 3-8 | 2-8 | 2-8 | 5-20 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Fishbone Diagram, Cause Categories, Investigation Backlog | Cause Tree, Evidence Notes, Countermeasures | Simulation Notes, Gaps List, Updated Runbooks |
Tagsno overlap | FailureResilienceRisk | Root causeQualityOperations | Root causeTreeIncidentQuality | ResilienceOperationsIncident |