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 |  Business Strategy Value Chain Analysis |  Engineering Kanban |
|---|---|---|---|
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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 | Medium | High | Medium |
Timedifferent | 1-3 h | Half day | Ongoing |
Participantsdifferent | 4-10 | 3-8 | 2-12 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Value Chain Map, Lever List | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | StrategyBusiness modelDiagnosisAnalysis | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
