View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Discovery Kano Model | ![]() UX Research Usability Testing | ![]() UX Research Personas |
|---|---|---|---|
Purposedifferent | 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. | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-2 h je Session | 1-3 Tage |
Participantsdifferent | 10-50 | Based on research question | Internes Team |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Usability Issues, Severity List, Recommendations | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | ValidationUXPrototype | ResearchCustomerSynthesis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






