View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Service BlueprintingCustomer Journey MappingSpotify Model MappingTeam Topologies Interaction Modes
| Criterion | ![]() UX Design Service Blueprinting | ![]() UX Research Customer Journey Mapping | ![]() Team Design Spotify Model Mapping | ![]() Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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 landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | 0.5-2 Tage | 2-4 h | 90-180 min | Half day |
Participantsdifferent | 6-12 | 4-10 | 5-15 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Journey Map, Pain-point List, Opportunity Backlog | Spotify Model Map, Action List | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | Service designOperationsJourneyBlueprint | JourneyServiceService design | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaborationOrganization |



