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 |  Engineering Fault Isolation |  Operations Barrier Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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 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 | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 30-180 min | 2-4 h | 15-30 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-6 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Root cause notes, Countermeasures |
Tagsno overlap | RiskTrackingStakeholdersGovernance | TroubleshootingDiagnosisEngineering | Root causeSafetyIncident | Root causeIncidentLeanProblem solving |