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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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 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.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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
HighMediumMediumLow
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope1-3 h1-4 h15-30 min
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting3-103-82-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesCustomer Journey Canvas, Pain Points, Experience OpportunitiesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
JourneyCustomerService designCanvas
Root causeProblem solvingQualityIncident
Root causeIncidentLeanProblem solving
Add more methods