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 Visual Management |  Agile Sailboat Retrospective |  Operations After-Action Review |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work. | 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. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | Ongoing | 45-90 min | 20-45 min | 45-90 min |
Participantsdifferent | 1-20 | 4-12 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Sailboat Board, Risks, Improvement Actions | Lessons learned, Action items, Event summary | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | SignalsOperationsVisual management | RetrospectiveTeamImprovement | LearningOperationsImprovement | RetrospectiveImprovementExperimentsTeam |