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 Kano Model |  Delivery Value Stream Mapping |  Delivery Monte Carlo Forecasting |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | 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. | 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 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. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-2 Tage | 1-3 h | 30-90 min Setup, danach laufend | Ongoing |
Participantsdifferent | 10-50 | 4-10 | 1-8 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Current-state map, Future-state map, Bottleneck list | Forecast Percentiles, Throughput Dataset, Risk Communication | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | SatisfactionPrioritizationCustomer | LeanFlowWasteDelivery | ForecastingFlowDelivery | FlowVisual managementDelivery |