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 Root Cause Analysis |  Operations Kepner-Tregoe |
|---|---|---|---|
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 keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 h | 1-4 h | 2-8 h |
Participantsdifferent | 3-8 | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | FailureResilienceRisk | Root causeProblem solvingQualityIncident | Problem solvingRoot causeDecisionOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
