View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Theory of Constraints |  Operations After-Action Review |  Operations Kepner-Tregoe |  Operations Bottleneck Analysis |
|---|---|---|---|---|
Purposedifferent | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits 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. | 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. | 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. |
Complexitydifferent | High | Low | High | Medium |
Timedifferent | 2-4 h Analyse, laufend | 20-45 min | 2-8 h | 1-3 h |
Participantsdifferent | 3-12 | 3-12 | 2-8 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Constraint Map, Improvement Plan, Flow Metrics | Lessons learned, Action items, Event summary | Problem Analysis, Decision Analysis, Risk Plan | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures |
Tagsno overlap | OperationsConstraintsFlowImprovement | LearningOperationsImprovement | Problem solvingRoot causeDecisionOperations | FlowMeasurementConstraints |