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 Barrier Analysis |  Operations Fault Tree Analysis |  Architecture Architecture Decision Record |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 2-4 h | 2-6 h | 15-45 min | 15-30 min |
Participantsdifferent | 2-6 | 3-8 | 1-3 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures |
Tagsno overlap | Root causeSafetyIncident | RiskRoot causeSafety | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving |