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 ABC Analysis |  Delivery Cost of Delay |
|---|---|---|---|---|
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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | 2-4 h Analyse, laufend | Ongoing | 30-60 min | 90-180 min |
Participantsdifferent | 3-12 | 2-12 | 1-5 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Kanban board, WIP policies, Flow metrics | ABC Classification, Focus Rules, Control List | CoD Table, Prioritization Sequence |
Tagsno overlap | OperationsConstraintsFlowImprovement | FlowVisual managementDelivery | PrioritizationOperationsPortfolio | PrioritizationDeliveryEconomicsDecision |