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 Process Mapping |  Agile Ideal Days |
|---|---|---|---|
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. | 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. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 20-45 min | 1-3 h | 15-60 min |
Participantsdifferent | 3-12 | 3-10 | 2-9 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Process Map, Handoff List, Improvement Backlog | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | LearningOperationsImprovement | ProcessOperationsImprovement | EstimationEffortAgile |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
