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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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.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 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
MediumMediumLowMedium
Timedifferent
1-3 h1-3 h45-90 min1-3 h
Participantsdifferent
3-103-123-122-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesSystem Map, Dependencies, Leverage PointsForce Field Map, Change Levers, Risk NotesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
JourneyCustomerService designCanvas
Systems thinkingMappingBoundariesChange
ChangeDecisionStrategy
Domain-Driven DesignBoundariesStrategy
Add more methods