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 After-Action Review |  Operations Bottleneck Analysis |  Operations Process Mapping |
|---|---|---|---|---|
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. | 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. | 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 a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Ongoing | 20-45 min | 1-3 h | 1-3 h |
Participantsdifferent | 2-12 | 3-12 | 3-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Lessons learned, Action items, Event summary | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | FlowVisual managementDelivery | LearningOperationsImprovement | FlowMeasurementConstraints | ProcessOperationsImprovement |