methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 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 a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.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
LowMediumLowLow
Timedifferent
45–75 min2-4 h30-60 min30-60 min
Participantsdifferent
Team members involved4-103-103-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsJourney Map, Pain-point List, Opportunity BacklogEmotion Board, Themes, Action ItemsStart Stop Continue Board, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
JourneyServiceService design
RetrospectiveTeamReflection
RetrospectiveImprovementTeamReflection
Add more methods