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
Paper illustration of a horizontal story map with an activity backbone, task cards below it and a cross-map release line.
Product Discovery
User Story Mapping
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
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 user goals and delivery scope could drift apart, it orders the journey from goal to slice. It makes visible where an MVP can genuinely be cut.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 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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-4 h2-4 h1-4 h2-4 h
Participantsdifferent
4-104-103-82-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogStory Map, Release Slices, Backlog CandidatesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
JourneyServiceService design
BacklogJourneyPlanningMVP
Root causeProblem solvingQualityIncident
Root causeSafetyIncident
Add more methods