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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Empathy Mapping
UX Research
Empathy Mapping
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
Purposedifferent
When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.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 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 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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 h30–60 min45–90 min2-8 h
Participantsdifferent
2-84-83-105-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesEmpathy Map, Assumptions List, Research GapsTheme clusters, Insight statements, Opportunity areasEvent Timeline, Ubiquitous Language, Boundaries, Open Questions
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
SynthesisQualitativeWorkshop
SynthesisQualitativeRoot cause
Domain-Driven DesignEventsDiscoveryWorkshop
Add more methods