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 paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
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.When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.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.
Complexitydifferent
MediumLowMedium
Timedifferent
1-3 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-3 h
Participantsdifferent
3-10Scrum Team3-10
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesImprovement actions, Team agreementsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
JourneyCustomerService designCanvas
RetrospectiveImprovementLearning
LearningRetrospectiveIncidentOperations
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem