View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Spotify Model Mapping |  UX Research Customer Journey Mapping |  Team Design Team Topologies Interaction Modes |  Team Design Team API |
|---|---|---|---|---|
Purposedifferent | 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. | 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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 90-180 min | 2-4 h | Half day | Half day initial, dann laufend |
Participantsdifferent | 5-15 | 4-10 | Team-Leads plus Architecture | Ein Team plus Stakeholder |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Spotify Model Map, Action List | Journey Map, Pain-point List, Opportunity Backlog | Interaction Heat Map, Agreements per Pair | Team API Document |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | JourneyServiceService design | TeamAlignmentCollaborationOrganization | TeamAlignmentCommunicationService |