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 5 Whys |  Operations Root Cause Tree 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 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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 15-30 min | 1-3 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-6 | 2-8 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Root cause notes, Countermeasures | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Root causeIncidentLeanProblem solving | Root causeTreeIncidentQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
