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 | ![]() UX Research Customer Journey Mapping | ![]() Agile Start Stop Continue | ![]() Agile 4Ls Retrospective |
|---|---|---|---|---|
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 user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 0.5-2 Tage | 2-4 h | 30-60 min | 45–75 min |
Participantsdifferent | 6-12 | 4-10 | 3-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Journey Map, Pain-point List, Opportunity Backlog | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Service designOperationsJourneyBlueprint | JourneyServiceService design | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |



