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 two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible.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.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.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
LowMediumHighLow
Timedifferent
30–60 min per interview1-4 hPreparation, scenario analysis, and findings review; effort depends on scope15-30 min
Participantsdifferent
1 participant per interview3-8Architecture experts and stakeholders for scenarios and weighting2-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Interview Notes, Themes, Insight SummaryProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesRoot cause notes, Countermeasures
Tagsno overlap
QualitativeResearchCustomerDiscovery
Root causeProblem solvingQualityIncident
ArchitectureChangeAnalysisComparisonQuality
Root causeIncidentLeanProblem solving
Add more methods