View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Service Blueprinting |  Operations After-Action Review |  Agile 4Ls Retrospective |  Agile Mad Sad Glad |
|---|---|---|---|---|
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 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. | 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. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 0.5-2 Tage | 20-45 min | 45–75 min | 30-60 min |
Participantsdifferent | 6-12 | 3-12 | Team members involved | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Lessons learned, Action items, Event summary | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | Service designOperationsJourneyBlueprint | LearningOperationsImprovement | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection |