methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
A paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
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 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.When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear.
Complexitydifferent
HighMediumLowMedium
Timedifferent
0.5-2 Tage90-180 min45-90 min1-3 h
Participantsdifferent
6-125-153-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapSpotify Model Map, Action ListExpectation Map, Alignment Notes, AgreementsCustomer Journey Canvas, Pain Points, Experience Opportunities
Tagsno overlap
Service designOperationsJourneyBlueprint
TeamOrganizationAlignmentDiagnosis
AlignmentStakeholdersTeam
JourneyCustomerService designCanvas
Add more methods