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 |  Innovation Design Thinking |  Product Discovery Concierge MVP |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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. | 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. | 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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 1 Tag bis mehrere Wochen | 1-4 Wochen | 30-60 min |
Participantsdifferent | 1-4 | 4-10 | 3-10 Kunden | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Problem Statement, Prototype, Test Learnings | Concierge Learnings, Service Blueprint, MVP Risks | Completed Experiment Canvas, Success Metric |
Tagsno overlap | ValidationDemandMVP | InnovationPrototypeResearch | MVPValidationServiceDiscovery | ExperimentsValidationDiscoveryHypothesis |