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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
HighLowLow
Timedifferent
0.5-2 Tage30-60 min15-45 min
Participantsdifferent
6-122-81-3
Formatdifferent
WorkshopWorkshopAsync
Outputdifferent
Service Blueprint, Fail Points, Ownership MapFishbone Diagram, Cause Categories, Investigation BacklogADR File, Decision Log, Rationale
Tagsno overlap
Service designOperationsJourneyBlueprint
Root causeQualityOperations
ArchitectureRationaleDocumentationGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)