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
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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
Purposedifferent
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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 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.
Complexitydifferent
LowMediumLowLow
Timedifferent
30-60 min45-90 min30-60 min45–75 min
Participantsdifferent
3-122-53-10Team members involved
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsA3 Report, Action Plan, Root Cause AnalysisEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
LeanProblem solvingCoachingOperations
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods