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 Theory of Constraints |  Engineering Kanban |  Operations A3 Problem Solving |
|---|---|---|---|
Purposedifferent | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | 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 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 | High | Medium | Medium |
Timedifferent | 2-4 h Analyse, laufend | Ongoing | 45-90 min |
Participantsdifferent | 3-12 | 2-12 | 2-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Kanban board, WIP policies, Flow metrics | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | OperationsConstraintsFlowImprovement | FlowVisual managementDelivery | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
