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 |  UX Design Customer Journey Canvas |  Agile Sailboat Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
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 a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | 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. | 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 | Medium | Low | Low |
Timedifferent | 45–75 min | 1-3 h | 45-90 min | 45-90 min |
Participantsdifferent | Team members involved | 3-10 | 4-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Customer Journey Canvas, Pain Points, Experience Opportunities | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveLearningReflectionTeam | JourneyCustomerService designCanvas | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |