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 Concierge MVP |  Product Discovery Problem Interview |
|---|---|---|---|
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 an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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 | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 1-4 Wochen | 30-60 min je Interview |
Participantsdifferent | 1-4 | 3-10 Kunden | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Concierge Learnings, Service Blueprint, MVP Risks | Problem Evidence, Risk Notes, Customer Segments |
Tags1 shared | ValidationDemandMVP | MVPValidationServiceDiscovery | DiscoveryInterviewsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
