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 A3 Problem Solving |  Delivery Value Stream Mapping |  Operations Kaizen Event |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 45-90 min | 1-3 h | 0.5-5 Tage | Ongoing |
Participantsdifferent | 2-5 | 4-10 | 4-10 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Current-state map, Future-state map, Bottleneck list | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanProblem solvingCoachingOperations | LeanFlowWasteDelivery | LeanContinuous improvementOperations | FlowVisual managementDelivery |