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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
30–60 min per interview45-90 min45–90 min15-30 min
Participantsdifferent
1 participant per interview2-53-102-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Interview Notes, Themes, Insight SummaryA3 Report, Action Plan, Root Cause AnalysisTheme clusters, Insight statements, Opportunity areasRoot cause notes, Countermeasures
Tagsno overlap
QualitativeResearchCustomerDiscovery
LeanProblem solvingCoachingOperations
SynthesisQualitativeRoot cause
Root causeIncidentLeanProblem solving
Add more methods