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 Personas | ![]() Product Discovery Jobs to Be Done |
|---|---|---|---|
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 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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-3 Tage | 1-3 Wochen |
Participantsdifferent | 10-50 | Internes Team | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Persona Profiles, Needs Summary, Scenario Notes | Job Stories, Outcome Statements, Opportunity List |
Tags1 shared | SatisfactionPrioritizationCustomer | ResearchCustomerSynthesis | CustomerOutcomesNeeds |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






