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 Learning Review.
Operations
Learning Review
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
45–75 min1-3 h15-30 min30-60 min
Participantsdifferent
Team members involved3-102-63-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsLearning Review Notes, System Factors, Improvement ActionsRoot cause notes, CountermeasuresEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
LearningRetrospectiveIncidentOperations
Root causeIncidentLeanProblem solving
RetrospectiveTeamReflection
Add more methods