View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Diary Study |  Knowledge Modeling Event Modeling |  Delivery RAID Log |  Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-4 Wochen | 2-6 h | 30 min Setup, dann laufend | 2-8 h |
Participantsdifferent | 5-20 | 2-8 | 1-3 maintaining, briefing for everyone | 5-12 |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Event Model, UI Flow, Commands, Read Models | RAID Log, Status Report Source | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | UX researchTrackingBehavior | EventsBlueprintDomain-Driven DesignBehavior | RiskTrackingStakeholdersGovernance | Domain-Driven DesignEventsDiscoveryWorkshop |