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 Opportunity Scoring with its method-specific working model.
Product Discovery
Opportunity Scoring
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 opportunities need ranking by their effect, it makes importance and satisfaction directly comparable. It separates problem, assumption, solution, and evidence. The result is captured as an opportunity-score table and top outcomes.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
60-120 min30–60 min per interview30–60 min
Participantsdifferent
3-61 participant per interview4-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Opportunity Score Table, Top OutcomesInterview Notes, Themes, Insight SummaryEmpathy Map, Assumptions List, Research Gaps
Tagsno overlap
PrioritizationDiscoveryOutcomesNeeds
QualitativeResearchCustomerDiscovery
SynthesisQualitativeWorkshop
Add more methods

Often compared together

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

Paper illustration of a JTBD interview notebook with a decision timeline, forces of change and a concise job hypothesis.
Product Discovery
Jobs to Be Done
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