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 ABC Analysis
Operations
ABC Analysis
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.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 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.
Complexitysame
LowLowLowLow
Timedifferent
45–75 min30-60 min30-60 min45-90 min
Participantsdifferent
Team members involved1-53-104-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsABC Classification, Focus Rules, Control ListEmotion Board, Themes, Action ItemsSailboat Board, Risks, Improvement Actions
Tagsno overlap
RetrospectiveLearningReflectionTeam
PrioritizationOperationsPortfolio
RetrospectiveTeamReflection
RetrospectiveTeamImprovement
Add more methods