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 |  Operations Fishbone Diagram |
|---|---|---|---|
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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | Ongoing | 30-60 min |
Participantsdifferent | 4-10 | 2-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | LeanFlowWasteDelivery | FlowVisual managementDelivery | Root causeQualityOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
