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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Diary Study.
UX Research
Diary Study
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.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 experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory.
Complexitydifferent
MediumLowMedium
Timedifferent
2-6 h15-45 min1-4 Wochen
Participantsdifferent
2-81-35-20
Formatdifferent
Workshop + asyncAsyncAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsADR File, Decision Log, RationaleDiary Entries, Longitudinal Patterns, Experience Timeline
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureRationaleDocumentationGovernance
UX researchTrackingBehavior
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
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments