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 Fault Tree Analysis |  Operations 5 Whys |  Operations Family Tree Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | 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. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 2-6 h | 15-30 min | 2-4 h | 2-4 h |
Participantsdifferent | 3-8 | 2-6 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Root cause notes, Countermeasures | Family Tree Diagram, Pattern Notes, Systemic Measures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tags1 shared | RiskRoot causeSafety | Root causeIncidentLeanProblem solving | Root causePatternsIncidentSystemic | Root causeSafetyIncident |