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 Power Interest Grid | ![]() Facilitation Expectation 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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 0.5-2 Tage | 90-180 min | 30-60 min | 45-90 min |
Participantsdifferent | 6-12 | 5-15 | 2-8 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Spotify Model Map, Action List | Power Interest Grid, Strategy per Stakeholder | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | Service designOperationsJourneyBlueprint | TeamOrganizationAlignmentDiagnosis | StakeholdersFacilitationAlignmentPlanning | AlignmentStakeholdersTeam |



