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 Waste Analysis |  Operations Bottleneck Analysis |  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 process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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 | Low | Medium | High |
Timedifferent | Ongoing | 45-120 min | 1-3 h | 2-4 h Analyse, laufend |
Participantsdifferent | 2-12 | 2-8 | 3-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Waste Map, Prioritized Waste, Improvement Backlog | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | FlowVisual managementDelivery | WasteLeanProcess improvement | FlowMeasurementConstraints | OperationsConstraintsFlowImprovement |