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 Change Analysis.
Operations
Change Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects 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 deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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
HighMediumHighLow
Timedifferent
0.5-2 Tage45-120 min2-6 h30-60 min
Participantsdifferent
6-122-63-102-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapChange Matrix, Cause Hypotheses, Validation Questions, Action ListFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
Service designOperationsJourneyBlueprint
ChangeRoot causeTroubleshootingComparison
RiskQualityOperationsRoot cause
Root causeQualityOperations
Add more methods