View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Engineering Failure Scenario Analysis |  Operations Failure Mode and Effects Analysis |  Operations Fault Tree Analysis |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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. |
Complexitydifferent | Low | Medium | High | High |
Timedifferent | 20-60 min | 1-3 h | 2-6 h | 2-6 h |
Participantsdifferent | 1-4 | 3-8 | 3-10 | 3-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | FMEA Table, Risk Priority, Mitigation Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | OperationsReliabilityDocumentation | FailureResilienceRisk | RiskQualityOperationsRoot cause | RiskRoot causeSafety |