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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
A paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.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 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.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
LowMediumMediumHigh
Timedifferent
15-45 min60-120 min1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-32-83-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleCommunication Canvas, Stakeholder Messages, Architecture Communication PlanCustomer Journey Canvas, Pain Points, Experience OpportunitiesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ArchitectureCommunicationStakeholdersCanvas
JourneyCustomerService designCanvas
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods