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 Research Customer Journey Mapping |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 4-10 | 4-12 | 4-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | JourneyServiceService design | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection |