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 Problem Interview
Product Discovery
Problem Interview
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
Affinity Diagramming
UX Research
Affinity Diagramming
Empathy Mapping
UX Research
Empathy Mapping
Purposedifferent
When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.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.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
MediumMediumLowLow
Timedifferent
30-60 min je Interview2-8 h45–90 min30–60 min
Participantsdifferent
5-12 Interviews5-123-104-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Problem Evidence, Risk Notes, Customer SegmentsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsTheme clusters, Insight statements, Opportunity areasEmpathy Map, Assumptions List, Research Gaps
Tagsno overlap
DiscoveryInterviewsValidation
Domain-Driven DesignEventsDiscoveryWorkshop
SynthesisQualitativeRoot cause
SynthesisQualitativeWorkshop
Add more methods