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 |  Operations A3 Problem Solving |  Engineering Kanban |
|---|---|---|---|
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. | 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 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 | Low | Medium | Medium |
Timedifferent | 1 h bis mehrere Wochen | 45-90 min | Ongoing |
Participantsdifferent | 1-8 | 2-5 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | A3 Report, Action Plan, Root Cause Analysis | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | Continuous improvementLeanExperiments | LeanProblem solvingCoachingOperations | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
