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 After-Action Review |
|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | Ongoing | 1-3 h | 20-45 min |
Participantsdifferent | 2-12 | 3-8 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Lessons learned, Action items, Event summary |
Tagsno overlap | FlowVisual managementDelivery | FlowMeasurementConstraints | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
