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 participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Affinity Diagramming
UX Research
Affinity Diagramming
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.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.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-2 h je Session45–90 min15-30 min2-4 h
Participantsdifferent
Based on research question3-102-62-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Usability Issues, Severity List, RecommendationsTheme clusters, Insight statements, Opportunity areasRoot cause notes, CountermeasuresBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
ValidationUXPrototype
SynthesisQualitativeRoot cause
Root causeIncidentLeanProblem solving
Root causeSafetyIncident
Add more methods