View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Product Discovery Assumption Mapping | ![]() Delivery Monte Carlo Forecasting | ![]() Product Discovery Experiment Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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 | Medium | Medium | High | Low |
Timedifferent | 1-3 h | 45-60 min | 30-90 min Setup, danach laufend | 30-60 min |
Participantsdifferent | 4-10 | 2-8 | 1-8 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Assumption map, Test backlog, Risk ranking | Forecast Percentiles, Throughput Dataset, Risk Communication | Completed Experiment Canvas, Success Metric |
Tagsno overlap | LeanFlowWasteDelivery | AssumptionsRiskExperimentsValidation | ForecastingFlowDelivery | ExperimentsValidationDiscoveryHypothesis |



