View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Operations Fault Tree Analysis |  Operations 5 Whys |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 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 | Low | High | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 2-6 h | 15-30 min | 2-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-8 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Root cause notes, Countermeasures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskRoot causeSafety | Root causeIncidentLeanProblem solving | Root causeSafetyIncident |