View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations After-Action Review |  Agile Sprint Retrospective |  UX Design Service Blueprinting |
|---|---|---|---|
Purposedifferent | 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 is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. |
Complexitydifferent | Low | Low | High |
Timedifferent | 20-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 0.5-2 Tage |
Participantsdifferent | 3-12 | Scrum Team | 6-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Improvement actions, Team agreements | Service Blueprint, Fail Points, Ownership Map |
Tagsno overlap | LearningOperationsImprovement | RetrospectiveImprovementLearning | Service designOperationsJourneyBlueprint |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
