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
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 paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2-4 h1-3 h1-4 h15-30 min
Participantsdifferent
4-103-103-82-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogCustomer Journey Canvas, Pain Points, Experience OpportunitiesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanRoot cause notes, Countermeasures
Tagsno overlap
JourneyServiceService design
JourneyCustomerService designCanvas
Root causeProblem solvingQualityIncident
Root causeIncidentLeanProblem solving
Add more methods