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 Starfish Retrospective |  Agile Sprint Retrospective |  Agile 4Ls 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 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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | Ongoing | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min |
Participantsdifferent | 1-20 | 4-12 | Scrum Team | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Starfish Board, Practice Changes, Experiments | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | SignalsOperationsVisual management | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam |