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 Outcome-Driven Innovation |  Innovation Design Thinking |
|---|---|---|---|
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. | 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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. |
Complexitydifferent | Low | High | High |
Timedifferent | Stunden bis wenige Tage | Mehrere Wochen | 1 Tag bis mehrere Wochen |
Participantsdifferent | 1-4 | 2-6 researchers plus sample | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | ValidationDemandMVP | OutcomesInnovationResearchQuantitative | InnovationPrototypeResearch |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
