View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research User Interviews | ![]() Product Discovery Kano Model | ![]() Product Discovery Concierge MVP | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 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 an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 30–60 min per interview | 1-2 Tage | 1-4 Wochen | 1-5 Tage |
Participantsdifferent | 1 participant per interview | 10-50 | 3-10 Kunden | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Kano Matrix, Feature Classes, Priority Themes | Concierge Learnings, Service Blueprint, MVP Risks | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | QualitativeResearchCustomerDiscovery | SatisfactionPrioritizationCustomer | MVPValidationServiceDiscovery | ValidationExperimentsDemandDiscovery |



