View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Scatter Diagram |  Delivery RAID Log |  Operations 5 Whys |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30-90 min | 30 min Setup, dann laufend | 15-30 min | 1-4 h |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | RAID Log, Status Report Source | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | Root causeQualityVisualization | RiskTrackingStakeholdersGovernance | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |