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 Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Paper illustration for Learning Review.
Operations
Learning Review
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
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 journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear.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 service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
45–75 min1-3 h1-3 h0.5-2 Tage
Participantsdifferent
Team members involved3-103-106-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsCustomer Journey Canvas, Pain Points, Experience OpportunitiesLearning Review Notes, System Factors, Improvement ActionsService Blueprint, Fail Points, Ownership Map
Tagsno overlap
RetrospectiveLearningReflectionTeam
JourneyCustomerService designCanvas
LearningRetrospectiveIncidentOperations
Service designOperationsJourneyBlueprint
Add more methods