View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Scenario AnalysisFault Tree AnalysisArchitecture Decision RecordFailure Mode and Effects Analysis
| Criterion |  Engineering Failure Scenario Analysis |  Operations Fault Tree Analysis |  Architecture Architecture Decision Record |  Operations Failure Mode and Effects 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-3 h | 2-6 h | 15-45 min | 2-6 h |
Participantsdifferent | 3-8 | 3-8 | 1-3 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | FailureResilienceRisk | RiskRoot causeSafety | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause |