View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Design Thinking |  Product Discovery Pretotyping |  Product Discovery Outcome-Driven Innovation |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | High | Low | High |
Timedifferent | 1 Tag bis mehrere Wochen | Stunden bis wenige Tage | Mehrere Wochen |
Participantsdifferent | 4-10 | 1-4 | 2-6 researchers plus sample |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | InnovationPrototypeResearch | ValidationDemandMVP | OutcomesInnovationResearchQuantitative |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
