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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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
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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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.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
MediumHighMediumHigh
Timedifferent
1-3 h2-6 h2-4 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-103-104-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesFMEA Table, Risk Priority, Mitigation ActionsJourney Map, Pain-point List, Opportunity BacklogPrioritized 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
RiskQualityOperationsRoot cause
JourneyServiceService design
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods