View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  UX Design Service Blueprinting |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 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 | Medium | High | Medium | Low |
Timedifferent | 2-4 h | 0.5-2 Tage | 90-180 min | 45-90 min |
Participantsdifferent | 3-12 | 6-12 | 5-15 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Service Blueprint, Fail Points, Ownership Map | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | TeamAlignmentCollaboration | Service designOperationsJourneyBlueprint | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |