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 |  Product Discovery Outcome-Driven Innovation |  UX Research User Interviews |  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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-2 Tage | Mehrere Wochen | 30–60 min per interview | 1-3 Wochen |
Participantsdifferent | 10-50 | 2-6 researchers plus sample | 1 participant per interview | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Interview Notes, Themes, Insight Summary | Job Stories, Outcome Statements, Opportunity List |
Tagsno overlap | SatisfactionPrioritizationCustomer | OutcomesInnovationResearchQuantitative | QualitativeResearchCustomerDiscovery | CustomerOutcomesNeeds |