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
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 Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Learning Review.
Operations
Learning Review
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.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 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.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
HighLowLowMedium
Timedifferent
0.5-2 TageUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter30-60 min1-3 h
Participantsdifferent
6-12Scrum Team3-103-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapImprovement actions, Team agreementsEmotion Board, Themes, Action ItemsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
Service designOperationsJourneyBlueprint
RetrospectiveImprovementLearning
RetrospectiveTeamReflection
LearningRetrospectiveIncidentOperations
Add more methods