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 8D Problem Solving | ![]() Operations 5 Whys |
|---|---|---|---|---|
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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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 | High | Low |
Timedifferent | 30-90 min | 30 min Setup, dann laufend | 1-6 Wochen | 15-30 min |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 4-10 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | RAID Log, Status Report Source | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | Root causeQualityVisualization | RiskTrackingStakeholdersGovernance | QualityProblem solvingRoot cause | Root causeIncidentLeanProblem solving |



