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 Bottleneck Analysis |  Operations ALPEN Method |  Decision Making Constraint Analysis |
|---|---|---|---|---|
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 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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | Ongoing | 1-3 h | 10-20 min daily | 30-90 min |
Participantsdifferent | 2-12 | 3-8 | 1 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Daily Plan, Time Estimates, Review Notes | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | FlowVisual managementDelivery | FlowMeasurementConstraints | PlanningTime managementProductivityOperations | ConstraintsDecisionPlanningOptions |