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 Problem Interview |  UX Research User Interviews |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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 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. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 30-60 min je Interview | 30–60 min per interview | 1-5 Tage |
Participantsdifferent | 10-50 | 5-12 Interviews | 1 participant per interview | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Problem Evidence, Risk Notes, Customer Segments | Interview Notes, Themes, Insight Summary | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | SatisfactionPrioritizationCustomer | DiscoveryInterviewsValidation | QualitativeResearchCustomerDiscovery | ValidationExperimentsDemandDiscovery |