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 Monte Carlo Forecasting | ![]() Growth Funnel Analysis | ![]() Growth Flywheel | ![]() Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | 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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth. | 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 | High | Medium | Medium | Medium |
Timedifferent | 30-90 min Setup, danach laufend | 1-3 h | 60-120 min | Ongoing |
Participantsdifferent | 1-8 | 1-5 | 3-8 | 2-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Funnel report, Drop-off analysis, Optimization hypotheses | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | ForecastingFlowDelivery | AnalyticsConversionGrowth | GrowthRetentionConversion | FlowVisual managementDelivery |



