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 team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Sailboat Retrospective
Agile
Sailboat 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
45–75 min30-60 min1-2 h45-90 min
Participantsdifferent
Team members involved3-124-124-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement ActionsAlignment Map, Open Issues, Decision QuestionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
AlignmentStakeholdersStrategyFacilitation
RetrospectiveTeamImprovement
Add more methods