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 a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Affinity Diagramming
UX Research
Affinity Diagramming
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.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
MediumMediumLowHigh
Timedifferent
2-4 h60-120 min45–90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
4-102-83-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogCommunication Canvas, Stakeholder Messages, Architecture Communication PlanTheme clusters, Insight statements, Opportunity areasPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
JourneyServiceService design
ArchitectureCommunicationStakeholdersCanvas
SynthesisQualitativeRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods