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 |  Architecture Architecture Decision Record |  Operations Fault Tree 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. | 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 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 | Medium | Low | High |
Timedifferent | 1-3 h | 15-45 min | 2-6 h |
Participantsdifferent | 3-8 | 1-3 | 3-8 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | ADR File, Decision Log, Rationale | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | FailureResilienceRisk | ArchitectureRationaleDocumentationGovernance | RiskRoot causeSafety |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
