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 Start Stop Continue |  Agile Sailboat Retrospective |  UX Design Customer Journey Canvas |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 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 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 | 30-60 min | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 3-12 | 4-12 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions | Customer Journey Canvas, Pain Points, Experience Opportunities | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement | JourneyCustomerService designCanvas | RetrospectiveImprovementExperimentsTeam |