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 |  Delivery Cost of Delay |  Operations After-Action Review |  Operations Kepner-Tregoe |
|---|---|---|---|---|
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. | 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. | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | Ongoing | 90-180 min | 20-45 min | 2-8 h |
Participantsdifferent | 2-12 | 3-8 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | CoD Table, Prioritization Sequence | Lessons learned, Action items, Event summary | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | FlowVisual managementDelivery | PrioritizationDeliveryEconomicsDecision | LearningOperationsImprovement | Problem solvingRoot causeDecisionOperations |