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 Strategy Lean Canvas |  Delivery Value Stream Mapping |
|---|---|---|---|
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 an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 45-90 min | 1-3 h |
Participantsdifferent | 1-4 | 1-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Lean Canvas, Core Assumptions, Experiment Backlog | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | ValidationDemandMVP | StartupLeanAssumptionsBusiness model | LeanFlowWasteDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
