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 Research Customer Journey Mapping |  Business Strategy Value Chain Analysis |  Team Design Spotify Model Mapping |  Team Design Team API |
|---|---|---|---|---|
Purposedifferent | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 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 | High | Medium | Low |
Timedifferent | 2-4 h | Half day | 90-180 min | Half day initial, dann laufend |
Participantsdifferent | 4-10 | 3-8 | 5-15 | Ein Team plus Stakeholder |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Value Chain Map, Lever List | Spotify Model Map, Action List | Team API Document |
Tagsno overlap | JourneyServiceService design | StrategyBusiness modelDiagnosisAnalysis | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCommunicationService |