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 Personas | ![]() Operations 5 Whys | ![]() Operations Kepner-Tregoe | ![]() UX Research Affinity Diagramming |
|---|---|---|---|---|
Purposedifferent | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 Tage | 15-30 min | 2-8 h | 45–90 min |
Participantsdifferent | Internes Team | 2-6 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Root cause notes, Countermeasures | Problem Analysis, Decision Analysis, Risk Plan | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | ResearchCustomerSynthesis | Root causeIncidentLeanProblem solving | Problem solvingRoot causeDecisionOperations | SynthesisQualitativeRoot cause |



