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 Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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
Purposedifferent
When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit.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.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.
Complexitydifferent
HighLowMediumMedium
Timedifferent
0.5-2 Tage15-30 min1-3 h1-4 h
Participantsdifferent
6-122-63-103-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Service Blueprint, Fail Points, Ownership MapRoot cause notes, CountermeasuresCustomer Journey Canvas, Pain Points, Experience OpportunitiesProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Service designOperationsJourneyBlueprint
Root causeIncidentLeanProblem solving
JourneyCustomerService designCanvas
Root causeProblem solvingQualityIncident
Add more methods