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 |  Operations After-Action Review |  Agile Sailboat Retrospective |
|---|---|---|---|---|
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. | 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 team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 45–75 min | 0.5-2 Tage | 20-45 min | 45-90 min |
Participantsdifferent | Team members involved | 6-12 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Service Blueprint, Fail Points, Ownership Map | Lessons learned, Action items, Event summary | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | Service designOperationsJourneyBlueprint | LearningOperationsImprovement | RetrospectiveTeamImprovement |