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 |  Engineering Kanban |  Growth Flywheel |
|---|---|---|---|
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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | Ongoing | 60-120 min |
Participantsdifferent | 4-10 | 2-12 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | LeanFlowWasteDelivery | FlowVisual managementDelivery | GrowthRetentionConversion |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
