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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.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 Tage1-3 h45-90 min1-3 h
Participantsdifferent
6-122-83-123-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapContext Map, Integration Patterns, Boundary NotesForce Field Map, Change Levers, Risk NotesCustomer Journey Canvas, Pain Points, Experience Opportunities
Tagsno overlap
Service designOperationsJourneyBlueprint
Domain-Driven DesignBoundariesStrategy
ChangeDecisionStrategy
JourneyCustomerService designCanvas
Add more methods