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 BlueprintingTeam Topologies Interaction ModesSpotify Model MappingCustomer Journey Mapping
| Criterion | ![]() UX Design Service Blueprinting | ![]() Team Design Team Topologies Interaction Modes | ![]() Team Design Spotify Model Mapping | ![]() UX Research Customer Journey Mapping |
|---|---|---|---|---|
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 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. | 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 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. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | 0.5-2 Tage | Half day | 90-180 min | 2-4 h |
Participantsdifferent | 6-12 | Team-Leads plus Architecture | 5-15 | 4-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | Service designOperationsJourneyBlueprint | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis | JourneyServiceService design |



