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 Fake Door Test | ![]() Product Discovery Pretotyping | ![]() Product Discovery Problem Interview |
|---|---|---|---|
Purposedifferent | 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. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-5 Tage | Stunden bis wenige Tage | 30-60 min je Interview |
Participantsdifferent | Nutzertraffic | 1-4 | 5-12 Interviews |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | Click Data, Interest Signal, Learning Decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Problem Evidence, Risk Notes, Customer Segments |
Tags1 shared | ValidationExperimentsDemandDiscovery | ValidationDemandMVP | DiscoveryInterviewsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






