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 Wizard of Oz Test |  Product Discovery Solution Interview |  Product Discovery Problem 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. | When a new experience would still be too expensive to automate for real, it simulates the outcome behind the scenes. It checks user reaction and value before the technology disappears. | 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 the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-2 Tage | 2-10 Tage | 30-60 min je Interview | 30-60 min je Interview |
Participantsdifferent | 10-50 | 5-20 Nutzer | 5-10 Interviews | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Prototype Learnings, Manual Effort Notes, Risk List | Solution Feedback, Objection List, Validation Notes | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | SatisfactionPrioritizationCustomer | PrototypeValidationMVP | ValidationInterviewsPrototype | DiscoveryInterviewsValidation |