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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
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.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
2-4 hPreparation, scenario analysis, and findings review; effort depends on scope1-4 h1-3 h
Participantsdifferent
4-10Architecture experts and stakeholders for scenarios and weighting3-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
JourneyServiceService design
ArchitectureChangeAnalysisComparisonQuality
Root causeProblem solvingQualityIncident
Root causeTreeIncidentQuality
Add more methods