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 Design Thinking |  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 complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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 | High | Medium |
Timedifferent | Stunden bis wenige Tage | 30-60 min je Interview | 1 Tag bis mehrere Wochen | 1-5 Tage |
Participantsdifferent | 1-4 | 5-10 Interviews | 4-10 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Solution Feedback, Objection List, Validation Notes | Problem Statement, Prototype, Test Learnings | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | ValidationInterviewsPrototype | InnovationPrototypeResearch | ValidationExperimentsDemandDiscovery |