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 Process Mapping |
|---|---|---|---|
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. | 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 | Low | High | Medium |
Timedifferent | 20-45 min | 2-8 h | 1-3 h |
Participantsdifferent | 3-12 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Problem Analysis, Decision Analysis, Risk Plan | Process Map, Handoff List, Improvement Backlog |
Tags1 shared | LearningOperationsImprovement | Problem solvingRoot causeDecisionOperations | ProcessOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






