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 |  Innovation Design Thinking |  UX Research Personas |
|---|---|---|---|---|
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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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. |
Complexitydifferent | Medium | High | High | Medium |
Timedifferent | 1-2 Tage | Mehrere Wochen | 1 Tag bis mehrere Wochen | 1-3 Tage |
Participantsdifferent | 10-50 | 2-6 researchers plus sample | 4-10 | Internes Team |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Prototype, Test Learnings | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | OutcomesInnovationResearchQuantitative | InnovationPrototypeResearch | ResearchCustomerSynthesis |