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 Fake Door Test |  Product Discovery Problem Interview |
|---|---|---|---|---|
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. | 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. | 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 | Medium |
Timedifferent | 30-60 min je Interview | Stunden bis wenige Tage | 1-5 Tage | 30-60 min je Interview |
Participantsdifferent | 5-10 Interviews | 1-4 | Nutzertraffic | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision | Problem Evidence, Risk Notes, Customer Segments |
Tags1 shared | ValidationInterviewsPrototype | ValidationDemandMVP | ValidationExperimentsDemandDiscovery | DiscoveryInterviewsValidation |