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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Empathy Mapping
UX Research
Empathy Mapping
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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 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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
MediumLowLow
Timedifferent
2-6 h30–60 min15-45 min
Participantsdifferent
2-84-81-3
Formatdifferent
Workshop + asyncWorkshopAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsEmpathy Map, Assumptions List, Research GapsADR File, Decision Log, Rationale
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
SynthesisQualitativeWorkshop
ArchitectureRationaleDocumentationGovernance
Add more methods

Often compared together

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

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
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop