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 |  Agile Starfish Retrospective |  Operations After-Action Review |  Operations Learning 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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45–75 min | 45-90 min | 20-45 min | 1-3 h |
Participantsdifferent | Team members involved | 4-12 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments | Lessons learned, Action items, Event summary | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam | LearningOperationsImprovement | LearningRetrospectiveIncidentOperations |