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
Empathy Mapping
UX Research
Empathy Mapping
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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Affinity Diagramming
UX Research
Affinity Diagramming
Purposedifferent
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.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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30–60 min2-8 h2-6 h45–90 min
Participantsdifferent
4-85-122-83-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Empathy Map, Assumptions List, Research GapsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsEvent Model, UI Flow, Commands, Read ModelsTheme clusters, Insight statements, Opportunity areas
Tagsno overlap
SynthesisQualitativeWorkshop
Domain-Driven DesignEventsDiscoveryWorkshop
EventsBlueprintDomain-Driven DesignBehavior
SynthesisQualitativeRoot cause
Add more methods