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 Problem Interview | ![]() Product Discovery MVP Test Matrix |
|---|---|---|---|
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 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 several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 30-60 min je Interview | 45-75 min |
Participantsdifferent | 1-4 | 5-12 Interviews | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Problem Evidence, Risk Notes, Customer Segments | Test Matrix, Test Plan |
Tags1 shared | ValidationDemandMVP | DiscoveryInterviewsValidation | ExperimentsValidationDiscoveryOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






