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 |  Operations ABC Analysis |  UX Research Personas |  UX Research User Interviews |
|---|---|---|---|---|
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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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 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 | Low | Medium | Low |
Timedifferent | 1-2 Tage | 30-60 min | 1-3 Tage | 30–60 min per interview |
Participantsdifferent | 10-50 | 1-5 | Internes Team | 1 participant per interview |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ABC Classification, Focus Rules, Control List | Persona Profiles, Needs Summary, Scenario Notes | Interview Notes, Themes, Insight Summary |
Tagsno overlap | SatisfactionPrioritizationCustomer | PrioritizationOperationsPortfolio | ResearchCustomerSynthesis | QualitativeResearchCustomerDiscovery |