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 Monte Carlo Forecasting |  Delivery Value Stream 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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. | 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 | High | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 30-90 min Setup, danach laufend | 1-3 h | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-4 | 1-8 | 4-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | ValidationDemandMVP | ForecastingFlowDelivery | LeanFlowWasteDelivery | LeanStartupValidationMVP |