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 After-Action Review |  Operations Kepner-Tregoe |  Operations Theory of Constraints |
|---|---|---|---|
Purposedifferent | 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 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. |
Complexitydifferent | Low | High | High |
Timedifferent | 20-45 min | 2-8 h | 2-4 h Analyse, laufend |
Participantsdifferent | 3-12 | 2-8 | 3-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Problem Analysis, Decision Analysis, Risk Plan | Constraint Map, Improvement Plan, Flow Metrics |
Tags1 shared | LearningOperationsImprovement | Problem solvingRoot causeDecisionOperations | OperationsConstraintsFlowImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
