View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Cost of Delay | ![]() Engineering Kanban | ![]() Operations A3 Problem Solving | ![]() Operations Kepner-Tregoe |
|---|---|---|---|---|
Purposedifferent | 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. | 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 complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | High | Medium | Medium | High |
Timedifferent | 90-180 min | Ongoing | 45-90 min | 2-8 h |
Participantsdifferent | 3-8 | 2-12 | 2-5 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | CoD Table, Prioritization Sequence | Kanban board, WIP policies, Flow metrics | A3 Report, Action Plan, Root Cause Analysis | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | FlowVisual managementDelivery | LeanProblem solvingCoachingOperations | Problem solvingRoot causeDecisionOperations |



