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 |  UX Research Affinity Diagramming |  Operations Root Cause 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. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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 min Setup, dann laufend | 15-30 min | 45–90 min | 1-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-6 | 3-10 | 3-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Root cause notes, Countermeasures | Theme clusters, Insight statements, Opportunity areas | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Root causeIncidentLeanProblem solving | SynthesisQualitativeRoot cause | Root causeProblem solvingQualityIncident |