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 review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Learning Review.
Operations
Learning Review
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 missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.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.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
LowLowMediumLow
Timedifferent
45–75 min20-45 min1-3 h30-60 min
Participantsdifferent
Team members involved3-123-103-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsLessons learned, Action items, Event summaryLearning Review Notes, System Factors, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
LearningOperationsImprovement
LearningRetrospectiveIncidentOperations
RetrospectiveTeamReflection
Add more methods