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 | ![]() UX Design Customer Journey Canvas | ![]() UX Research User Interviews |
|---|---|---|---|---|
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. | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Tage | 1-2 Tage | 1-3 h | 30–60 min per interview |
Participantsdifferent | Internes Team | 10-50 | 3-10 | 1 participant per interview |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Kano Matrix, Feature Classes, Priority Themes | Customer Journey Canvas, Pain Points, Experience Opportunities | Interview Notes, Themes, Insight Summary |
Tags1 shared | ResearchCustomerSynthesis | SatisfactionPrioritizationCustomer | JourneyCustomerService designCanvas | QualitativeResearchCustomerDiscovery |



