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 |  Delivery Value Stream Mapping |  Product Discovery Assumption Mapping |  Innovation Lean Startup |
|---|---|---|---|---|
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 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 1-3 h | 45-60 min | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-4 | 4-10 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Current-state map, Future-state map, Bottleneck list | Assumption map, Test backlog, Risk ranking | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | ValidationDemandMVP | LeanFlowWasteDelivery | AssumptionsRiskExperimentsValidation | LeanStartupValidationMVP |