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 Learning Review |  UX Design Service Blueprinting |  Agile Sprint Retrospective |
|---|---|---|---|
Purposedifferent | 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 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 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. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 1-3 h | 0.5-2 Tage | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-10 | 6-12 | Scrum Team |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Learning Review Notes, System Factors, Improvement Actions | Service Blueprint, Fail Points, Ownership Map | Improvement actions, Team agreements |
Tagsno overlap | LearningRetrospectiveIncidentOperations | Service designOperationsJourneyBlueprint | RetrospectiveImprovementLearning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
