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 | ![]() Product Discovery Outcome-Driven Innovation | ![]() Product Discovery Opportunity Scoring |
|---|---|---|---|---|
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. | 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 opportunities need ranking by their effect, it makes importance and satisfaction directly comparable. It separates problem, assumption, solution, and evidence. The result is captured as an opportunity-score table and top outcomes. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 Tage | 1-2 Tage | Mehrere Wochen | 60-120 min |
Participantsdifferent | Internes Team | 10-50 | 2-6 researchers plus sample | 3-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Kano Matrix, Feature Classes, Priority Themes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Opportunity Score Table, Top Outcomes |
Tagsno overlap | ResearchCustomerSynthesis | SatisfactionPrioritizationCustomer | OutcomesInnovationResearchQuantitative | PrioritizationDiscoveryOutcomesNeeds |



