View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Design Customer Journey Canvas | ![]() Agile Sailboat Retrospective | ![]() Agile Starfish Retrospective |
|---|---|---|---|
Purposedifferent | 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 | Medium | Low | Low |
Timedifferent | 1-3 h | 45-90 min | 45-90 min |
Participantsdifferent | 3-10 | 4-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | JourneyCustomerService designCanvas | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






