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 Solution Interview | ![]() Product Discovery Outcome-Driven Innovation |
|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Medium | High |
Timedifferent | Stunden bis wenige Tage | 30-60 min je Interview | Mehrere Wochen |
Participantsdifferent | 1-4 | 5-10 Interviews | 2-6 researchers plus sample |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Solution Feedback, Objection List, Validation Notes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | ValidationDemandMVP | ValidationInterviewsPrototype | OutcomesInnovationResearchQuantitative |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






