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
Affinity Diagramming
UX Research
Affinity Diagramming
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.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
MediumLowLowLow
Timedifferent
2-6 h30–60 min15-45 min45–90 min
Participantsdifferent
2-84-81-33-10
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsEmpathy Map, Assumptions List, Research GapsADR File, Decision Log, RationaleTheme clusters, Insight statements, Opportunity areas
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
SynthesisQualitativeWorkshop
ArchitectureRationaleDocumentationGovernance
SynthesisQualitativeRoot cause
Add more methods