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 Learning Review |  Agile Starfish Retrospective |  Operations After-Action Review |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 45-90 min | 20-45 min | 45-90 min |
Participantsdifferent | 3-10 | 4-12 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | Starfish Board, Practice Changes, Experiments | Lessons learned, Action items, Event summary | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementExperimentsTeam | LearningOperationsImprovement | RetrospectiveTeamImprovement |