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 |  Engineering Kanban |  Product Discovery Pretotyping |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h | Ongoing | Stunden bis wenige Tage | 30-90 min Setup, danach laufend |
Participantsdifferent | 4-10 | 2-12 | 1-4 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | LeanFlowWasteDelivery | FlowVisual managementDelivery | ValidationDemandMVP | ForecastingFlowDelivery |