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
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
MediumHighLowLow
Timedifferent
2-4 hSeveral meetings plus preparation and analysis; total effort depends on scope1-4 h1-2 Tage
Participantsdifferent
4-10Evaluation team, architects, and relevant stakeholders1-51-4
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Journey 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 investigationsContext Diagram, Container Diagram, Component DiagramArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
JourneyServiceService design
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureCommunicationVisualization
ArchitectureDocumentationCommunication
Add more methods