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 |  Team Design Spotify Model Mapping |  Facilitation Team Charter |  Facilitation Expectation Mapping |
|---|---|---|---|---|
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. | 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 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 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 | Medium | Medium | Low |
Timedifferent | 2-4 h | 90-180 min | 2-4 h | 45-90 min |
Participantsdifferent | 4-10 | 5-15 | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Spotify Model Map, Action List | Team Charter, Working Norms, Role Notes | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | JourneyServiceService design | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaboration | AlignmentStakeholdersTeam |