View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile 4Ls Retrospective |  Operations A3 Problem Solving |  Operations Learning Review |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45–75 min | 45-90 min | 1-3 h | 20-45 min |
Participantsdifferent | Team members involved | 2-5 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | A3 Report, Action Plan, Root Cause Analysis | Learning Review Notes, System Factors, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | RetrospectiveLearningReflectionTeam | LeanProblem solvingCoachingOperations | LearningRetrospectiveIncidentOperations | LearningOperationsImprovement |