View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Growth Hooked Model |  Growth Flywheel |  Delivery Value Stream Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | Ongoing | Multiple workshops over several weeks | 60-120 min | 1-3 h |
Participantsdifferent | 2-12 | 2-8 | 3-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Hooked loop, Trigger map, Reward design, Ethics check | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | FlowVisual managementDelivery | GrowthBehaviorRetention | GrowthRetentionConversion | LeanFlowWasteDelivery |