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 for Starfish Retrospective
Agile
Starfish 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 Mad Sad Glad
Agile
Mad Sad Glad
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 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.
Complexitysame
LowLowLowLow
Timedifferent
45–75 min45-90 min30-60 min30-60 min
Participantsdifferent
Team members involved4-123-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsStarfish Board, Practice Changes, ExperimentsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tags2 shared
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementExperimentsTeam
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods