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 |  Product Discovery Fake Door Test |  Innovation Lean Startup |  Product Discovery Pretotyping |
|---|---|---|---|---|
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 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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-60 min je Interview | 1-5 Tage | Wochen bis Monate je Lernzyklus | Stunden bis wenige Tage |
Participantsdifferent | 5-12 Interviews | Nutzertraffic | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Click Data, Interest Signal, Learning Decision | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tags1 shared | DiscoveryInterviewsValidation | ValidationExperimentsDemandDiscovery | LeanStartupValidationMVP | ValidationDemandMVP |