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 Concierge MVP |  Product Discovery Wizard of Oz 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. | 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 a new experience would still be too expensive to automate for real, it simulates the outcome behind the scenes. It checks user reaction and value before the technology disappears. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 30-60 min je Interview | Stunden bis wenige Tage | 1-4 Wochen | 2-10 Tage |
Participantsdifferent | 5-10 Interviews | 1-4 | 3-10 Kunden | 5-20 Nutzer |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Concierge Learnings, Service Blueprint, MVP Risks | Prototype Learnings, Manual Effort Notes, Risk List |
Tags1 shared | ValidationInterviewsPrototype | ValidationDemandMVP | MVPValidationServiceDiscovery | PrototypeValidationMVP |