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 for Change Analysis.
Operations
Change Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture 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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
2-4 h45-120 min1-2 TagePreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
4-102-61-4Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogChange Matrix, Cause Hypotheses, Validation Questions, Action ListArchitecture Document, Context View, Runtime View, Deployment ViewDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
JourneyServiceService design
ChangeRoot causeTroubleshootingComparison
ArchitectureDocumentationCommunication
ArchitectureChangeAnalysisComparisonQuality
Add more methods