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
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.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.
Complexitydifferent
LowMediumHighMedium
Timedifferent
30–60 min2-8 hPreparation, scenario analysis, and findings review; effort depends on scope2-6 h
Participantsdifferent
4-85-12Architecture experts and stakeholders for scenarios and weighting2-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Empathy Map, Assumptions List, Research GapsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
SynthesisQualitativeWorkshop
Domain-Driven DesignEventsDiscoveryWorkshop
ArchitectureChangeAnalysisComparisonQuality
EventsBlueprintDomain-Driven DesignBehavior
Add more methods