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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.
Complexitydifferent
HighLowMediumHigh
Timedifferent
0.5-2 Tage30 min Setup, dann laufend2-4 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
6-121-3 maintaining, briefing for everyone4-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Service Blueprint, Fail Points, Ownership MapRAID Log, Status Report SourceJourney Map, Pain-point List, Opportunity BacklogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Service designOperationsJourneyBlueprint
RiskTrackingStakeholdersGovernance
JourneyServiceService design
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods