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
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
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.When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit.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
LowHighMediumLow
Timedifferent
45–75 min0.5-2 Tage1-3 h30-60 min
Participantsdifferent
Team members involved6-123-103-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsService Blueprint, Fail Points, Ownership MapLearning Review Notes, System Factors, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
Service designOperationsJourneyBlueprint
LearningRetrospectiveIncidentOperations
RetrospectiveTeamReflection
Add more methods