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 |  Agile Sprint Retrospective |  Operations A3 Problem Solving |
|---|---|---|---|
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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 20-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min |
Participantsdifferent | 3-12 | Scrum Team | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Improvement actions, Team agreements | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | LearningOperationsImprovement | RetrospectiveImprovementLearning | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
