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 Pretotyping |  Product Discovery Solution Interview |  Innovation Lean Startup |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | 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. | 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 | Stunden bis wenige Tage | 30-60 min je Interview | Wochen bis Monate je Lernzyklus | 1-5 Tage |
Participantsdifferent | 1-4 | 5-10 Interviews | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Solution Feedback, Objection List, Validation Notes | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Click Data, Interest Signal, Learning Decision |
Tags1 shared | ValidationDemandMVP | ValidationInterviewsPrototype | LeanStartupValidationMVP | ValidationExperimentsDemandDiscovery |