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 PDCA Cycle |  Engineering Kanban |  Delivery Value Stream Mapping |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 1 h bis mehrere Wochen | Ongoing | 1-3 h | 15-30 min |
Participantsdifferent | 1-8 | 2-12 | 4-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Root cause notes, Countermeasures |
Tagsno overlap | Continuous improvementLeanExperiments | FlowVisual managementDelivery | LeanFlowWasteDelivery | Root causeIncidentLeanProblem solving |