View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  Delivery Value Stream Mapping |  Engineering Kanban |
|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30-60 min | 1-3 h | Ongoing |
Participantsdifferent | 1-5 | 4-10 | 2-12 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | PrioritizationOperationsPortfolio | LeanFlowWasteDelivery | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
