View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Affinity Diagramming | ![]() Operations Kepner-Tregoe | ![]() UX Design Service Blueprinting | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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 | High | High | Low |
Timedifferent | 45–90 min | 2-8 h | 0.5-2 Tage | 15-30 min |
Participantsdifferent | 3-10 | 2-8 | 6-12 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Problem Analysis, Decision Analysis, Risk Plan | Service Blueprint, Fail Points, Ownership Map | Root cause notes, Countermeasures |
Tagsno overlap | SynthesisQualitativeRoot cause | Problem solvingRoot causeDecisionOperations | Service designOperationsJourneyBlueprint | Root causeIncidentLeanProblem solving |



