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 |  Decision Making Assumption Surfacing |  Operations Root Cause 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 1-4 h | 15-30 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |