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 |  Delivery RAID Log |  Operations Family Tree Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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. | 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 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 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 | Low | Medium | Low |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 2-4 h | 15-30 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 2-6 | 2-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | RAID Log, Status Report Source | Family Tree Diagram, Pattern Notes, Systemic Measures | Root cause notes, Countermeasures |
Tagsno overlap | FailureResilienceRisk | RiskTrackingStakeholdersGovernance | Root causePatternsIncidentSystemic | Root causeIncidentLeanProblem solving |