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 Solution Interview |  Product Discovery Pretotyping |  Product Discovery Outcome-Driven Innovation |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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 | Medium | Low | High | Medium |
Timedifferent | 30-60 min je Interview | Stunden bis wenige Tage | Mehrere Wochen | 1-5 Tage |
Participantsdifferent | 5-10 Interviews | 1-4 | 2-6 researchers plus sample | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationInterviewsPrototype | ValidationDemandMVP | OutcomesInnovationResearchQuantitative | ValidationExperimentsDemandDiscovery |