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 Mad Sad Glad
Agile
Mad Sad Glad
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
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action 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 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.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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.
Complexitydifferent
HighLowLowLow
Timedifferent
0.5-2 Tage30-60 min45–75 min20-45 min
Participantsdifferent
6-123-10Team members involved3-12
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Service Blueprint, Fail Points, Ownership MapEmotion Board, Themes, Action Items4Ls Board, Learning Themes, Improvement ActionsLessons learned, Action items, Event summary
Tagsno overlap
Service designOperationsJourneyBlueprint
RetrospectiveTeamReflection
RetrospectiveLearningReflectionTeam
LearningOperationsImprovement
Add more methods