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 Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.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
MediumMediumHighHigh
Timedifferent
1-3 h60-120 min0.5-2 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-102-86-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesCommunication Canvas, Stakeholder Messages, Architecture Communication PlanService Blueprint, Fail Points, Ownership MapPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
JourneyCustomerService designCanvas
ArchitectureCommunicationStakeholdersCanvas
Service designOperationsJourneyBlueprint
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods