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 North Star Metric |  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 product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible. | 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-2 h | 60-120 min | Ongoing |
Participantsdifferent | 1-8 | 3-8 | 3-8 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | North Star metric, Input metric tree, Measurement cadence | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | ForecastingFlowDelivery | GrowthMetricsAlignmentRetention | GrowthRetentionConversion | FlowVisual managementDelivery |