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
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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
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.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h2-4 h15-30 min2-4 h
Participantsdifferent
3-104-102-62-6
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesJourney Map, Pain-point List, Opportunity BacklogRoot cause notes, CountermeasuresBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
JourneyCustomerService designCanvas
JourneyServiceService design
Root causeIncidentLeanProblem solving
Root causeSafetyIncident
Add more methods