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