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 |  Growth A/B Testing |  Delivery Monte Carlo Forecasting |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | High | High | Medium |
Timedifferent | 1-3 h | 1-4 Wochen | 30-90 min Setup, danach laufend | 45-60 min |
Participantsdifferent | 4-10 | 1-6 | 1-8 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Experiment results, Decision log, Learning summary | Forecast Percentiles, Throughput Dataset, Risk Communication | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | LeanFlowWasteDelivery | ExperimentsGrowthAnalyticsValidation | ForecastingFlowDelivery | AssumptionsRiskExperimentsValidation |