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 8D Problem Solving |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | Ongoing | 1-6 Wochen | 45-90 min |
Participantsdifferent | 4-10 | 2-12 | 4-10 | 2-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | LeanFlowWasteDelivery | FlowVisual managementDelivery | QualityProblem solvingRoot cause | LeanProblem solvingCoachingOperations |