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
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck Analysis
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
HighMediumMediumLow
Timedifferent
0.5-2 Tage1-3 h1-4 h30-60 min
Participantsdifferent
6-123-83-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapBottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
Service designOperationsJourneyBlueprint
FlowMeasurementConstraints
Root causeProblem solvingQualityIncident
Root causeQualityOperations
Add more methods