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 Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
Paper illustration for Learning Review.
Operations
Learning Review
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
A paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Purposedifferent
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 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.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.
Complexitydifferent
HighMediumLowMedium
Timedifferent
0.5-2 Tage1-3 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-3 h
Participantsdifferent
6-123-10Scrum Team3-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapLearning Review Notes, System Factors, Improvement ActionsImprovement actions, Team agreementsCustomer Journey Canvas, Pain Points, Experience Opportunities
Tagsno overlap
Service designOperationsJourneyBlueprint
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementLearning
JourneyCustomerService designCanvas
Add more methods