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 Problem Interview |  UX Research Usability Testing |  Product Discovery Riskiest Assumption Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 1-2 h je Session | 1-2 Wochen pro Iteration | 1-5 Tage |
Participantsdifferent | 5-12 Interviews | Based on research question | 2-6 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Usability Issues, Severity List, Recommendations | Prioritized Assumption List, Test Plan, Results Report | Click Data, Interest Signal, Learning Decision |
Tags1 shared | DiscoveryInterviewsValidation | ValidationUXPrototype | ExperimentsValidationDiscoveryAssumptions | ValidationExperimentsDemandDiscovery |