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 Surveys |  Product Discovery Smoke Test |  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 a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 | 3-14 Tage | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 10-50 | 50+ | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Survey Results, Charts, Segment Insights | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | SatisfactionPrioritizationCustomer | QuantitativeResearchValidation | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |