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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
LowMediumLow
Timedifferent
30–60 min2-6 h1-2 Tage
Participantsdifferent
4-82-81-4
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Empathy Map, Assumptions List, Research GapsEvent Model, UI Flow, Commands, Read ModelsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
SynthesisQualitativeWorkshop
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureDocumentationCommunication
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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record