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 5 Whys | ![]() Operations Kepner-Tregoe | ![]() UX Research Affinity Diagramming | ![]() Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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 | High | Low | Medium |
Timedifferent | 15-30 min | 2-8 h | 45–90 min | 1-4 h |
Participantsdifferent | 2-6 | 2-8 | 3-10 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Problem Analysis, Decision Analysis, Risk Plan | Theme clusters, Insight statements, Opportunity areas | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tags1 shared | Root causeIncidentLeanProblem solving | Problem solvingRoot causeDecisionOperations | SynthesisQualitativeRoot cause | Root causeProblem solvingQualityIncident |



