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 Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
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.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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 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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 h1-3 hHalf day1-3 h
Participantsdifferent
3-103-123-122-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesSystem Map, Dependencies, Leverage PointsLeverage Map, Action StrategyContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
JourneyCustomerService designCanvas
Systems thinkingMappingBoundariesChange
Systems thinkingChangeStrategy
Domain-Driven DesignBoundariesStrategy
Add more methods