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 Learning 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 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | Ongoing | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 1-20 | 4-12 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Sailboat Board, Risks, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | SignalsOperationsVisual management | RetrospectiveTeamImprovement | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementExperimentsTeam |