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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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
MediumLowMediumHigh
Timedifferent
1-3 h1-2 h60-120 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-103-102-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesArchitecture Canvas, Goals, Constraints, Quality AttributesCommunication Canvas, Stakeholder Messages, Architecture Communication PlanPrioritized 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
CanvasArchitectureAlignmentWorkshop
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods