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 Flywheel |  Agile NoEstimates |  Growth Hooked Model |
|---|---|---|---|---|
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. | 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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 60-120 min | laufend | Multiple workshops over several weeks |
Participantsdifferent | 4-10 | 3-8 | 2-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Throughput Data, Flow Forecast, Slicing Rules | Hooked loop, Trigger map, Reward design, Ethics check |
Tagsno overlap | LeanFlowWasteDelivery | GrowthRetentionConversion | EstimationForecastingFlow | GrowthBehaviorRetention |