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
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
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 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.
Complexitydifferent
HighMediumLow
Timedifferent
0.5-2 Tage1-3 h45–75 min
Participantsdifferent
6-123-10Team members involved
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapLearning Review Notes, System Factors, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
Service designOperationsJourneyBlueprint
LearningRetrospectiveIncidentOperations
RetrospectiveLearningReflectionTeam
Add more methods

Often compared together

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

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem