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
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.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.
Complexitydifferent
MediumLowHighLow
Timedifferent
1-3 h45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope1-2 h
Participantsdifferent
3-103-12Evaluation team, architects, and relevant stakeholders3-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesExpectation Map, Alignment Notes, AgreementsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
JourneyCustomerService designCanvas
AlignmentStakeholdersTeam
ArchitectureQualityRiskTradeoffsStakeholders
CanvasArchitectureAlignmentWorkshop
Add more methods