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 |  Team Design Spotify Model Mapping |  Facilitation Stakeholder 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 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | High | Medium | Low |
Timedifferent | 0.5-2 Tage | 90-180 min | 60–90 min |
Participantsdifferent | 6-12 | 5-15 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Spotify Model Map, Action List | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Service designOperationsJourneyBlueprint | TeamOrganizationAlignmentDiagnosis | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
