View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Domain Context Map |  Knowledge Modeling Event Modeling |  UX Research Diary Study |
|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 2-6 h | 1-4 Wochen |
Participantsdifferent | 3-10 | 2-8 | 5-20 |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Event Model, UI Flow, Commands, Read Models | Diary Entries, Longitudinal Patterns, Experience Timeline |
Tagsno overlap | Domain-Driven DesignContextBoundaries | EventsBlueprintDomain-Driven DesignBehavior | UX researchTrackingBehavior |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
