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 Funnel Analysis |  Operations Waste Analysis |  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. | 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. | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | Ongoing | 1-3 h | 45-120 min | 1-3 h |
Participantsdifferent | 2-12 | 1-5 | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Funnel report, Drop-off analysis, Optimization hypotheses | Waste Map, Prioritized Waste, Improvement Backlog | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | FlowVisual managementDelivery | AnalyticsConversionGrowth | WasteLeanProcess improvement | LeanFlowWasteDelivery |