View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Operations Kepner-Tregoe |  Operations Theory of Constraints |
|---|---|---|---|
Purposedifferent | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. |
Complexitydifferent | Medium | High | High |
Timedifferent | Ongoing | 2-8 h | 2-4 h Analyse, laufend |
Participantsdifferent | 2-12 | 2-8 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Problem Analysis, Decision Analysis, Risk Plan | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | FlowVisual managementDelivery | Problem solvingRoot causeDecisionOperations | OperationsConstraintsFlowImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
