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 | ![]() Agile 4Ls Retrospective | ![]() Agile Start Stop Continue | ![]() Operations Learning Review |
|---|---|---|---|---|
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. | 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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 0.5-2 Tage | 45–75 min | 30-60 min | 1-3 h |
Participantsdifferent | 6-12 | Team members involved | 3-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | Service designOperationsJourneyBlueprint | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection | LearningRetrospectiveIncidentOperations |



