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 Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration of a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey 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 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.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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.
Complexitydifferent
HighMediumHighMedium
Timedifferent
0.5-2 Tage1-3 hHalf day2-4 h
Participantsdifferent
6-122-83-124-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapContext Map, Integration Patterns, Boundary NotesLeverage Map, Action StrategyJourney Map, Pain-point List, Opportunity Backlog
Tagsno overlap
Service designOperationsJourneyBlueprint
Domain-Driven DesignBoundariesStrategy
Systems thinkingChangeStrategy
JourneyServiceService design
Add more methods