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 Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Expectation Mapping.
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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
HighMediumMediumLow
Timedifferent
0.5-2 Tage90-180 min1-2 h45-90 min
Participantsdifferent
6-125-154-123-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapSpotify Model Map, Action ListAlignment Map, Open Issues, Decision QuestionsExpectation Map, Alignment Notes, Agreements
Tagsno overlap
Service designOperationsJourneyBlueprint
TeamOrganizationAlignmentDiagnosis
AlignmentStakeholdersStrategyFacilitation
AlignmentStakeholdersTeam
Add more methods