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 for Change Analysis.
Operations
Change Analysis
Paper illustration of a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
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.When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down.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.
Complexitysame
MediumMediumMedium
Timedifferent
45-120 min1-2 h je Session1-4 h
Participantsdifferent
2-6Based on research question3-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Change Matrix, Cause Hypotheses, Validation Questions, Action ListUsability Issues, Severity List, RecommendationsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ChangeRoot causeTroubleshootingComparison
ValidationUXPrototype
Root causeProblem solvingQualityIncident
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)