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 |  UX Research User Interviews |  Product Discovery Fake Door Test |  Product Discovery MVP Test Matrix |
|---|---|---|---|---|
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 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. | When several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 Tage | 30–60 min per interview | 1-5 Tage | 45-75 min |
Participantsdifferent | 10-50 | 1 participant per interview | Nutzertraffic | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Interview Notes, Themes, Insight Summary | Click Data, Interest Signal, Learning Decision | Test Matrix, Test Plan |
Tagsno overlap | SatisfactionPrioritizationCustomer | QualitativeResearchCustomerDiscovery | ValidationExperimentsDemandDiscovery | ExperimentsValidationDiscoveryOptions |