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 | ![]() Product Discovery Kano Model | ![]() Operations A3 Problem Solving |
|---|---|---|---|
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. | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Tage | 1-2 Tage | 45-90 min |
Participantsdifferent | Internes Team | 10-50 | 2-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Kano Matrix, Feature Classes, Priority Themes | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | ResearchCustomerSynthesis | SatisfactionPrioritizationCustomer | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






