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 Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Contextual Inquiry.
UX Research
Contextual Inquiry
Paper illustration for Diary Study.
UX Research
Diary Study
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise.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.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h1-3 Wochen1-4 Wochen2-6 h
Participantsdifferent
3-84-12 Beobachtungen5-202-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesField Notes, Workflow Insights, Pain PointsDiary Entries, Longitudinal Patterns, Experience TimelineEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
Domain-Driven DesignBoundariesModeling
UX researchObservationContext
UX researchTrackingBehavior
EventsBlueprintDomain-Driven DesignBehavior
Add more methods