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 branching tree with an outcome at its root, customer opportunities, solution options and small experiment cards.
Product Discovery
Opportunity Solution Tree
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Empathy Mapping
UX Research
Empathy Mapping
Purposedifferent
When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure.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 lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.
Complexitydifferent
MediumLowLow
Timedifferent
1-2 h Setup, laufend30–60 min per interview30–60 min
Participantsdifferent
2-61 participant per interview4-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Opportunity Solution Tree, Experiment Backlog, Learning LogInterview Notes, Themes, Insight SummaryEmpathy Map, Assumptions List, Research Gaps
Tagsno overlap
DiscoveryOutcomesExperimentsOpportunity
QualitativeResearchCustomerDiscovery
SynthesisQualitativeWorkshop
Add more methods

Often compared together

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

Paper illustration for Opportunity Interview
Product Discovery
Opportunity Interview
Affinity Diagramming
UX Research
Affinity Diagramming
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming