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 |  Innovation Design Thinking |  Product Discovery Solution Interview |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
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. | 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 a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-2 Tage | 1 Tag bis mehrere Wochen | 30-60 min je Interview | 30-60 min je Interview |
Participantsdifferent | 10-50 | 4-10 | 5-10 Interviews | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Problem Statement, Prototype, Test Learnings | Solution Feedback, Objection List, Validation Notes | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | SatisfactionPrioritizationCustomer | InnovationPrototypeResearch | ValidationInterviewsPrototype | DiscoveryInterviewsOpportunityCustomer |