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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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 Tage1-3 Tage2-6 h30-60 min
Participantsdifferent
6-121-43-102-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapArchitecture Views, Cross-view Notes, RationaleFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
Service designOperationsJourneyBlueprint
DocumentationStakeholdersArchitecture
RiskQualityOperationsRoot cause
Root causeQualityOperations
Add more methods