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 |  UX Research Card Sorting |  Knowledge Modeling Event Modeling |  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. | When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | 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 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 | Low | Medium | Medium |
Timedifferent | 1-4 Wochen | 20-45 min | 2-6 h | 2-8 h |
Participantsdifferent | 5-20 | Based on research question | 2-8 | 5-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Content groups, Label set, IA hypotheses | Event Model, UI Flow, Commands, Read Models | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | UX researchTrackingBehavior | Information architectureNavigationStructure | EventsBlueprintDomain-Driven DesignBehavior | Domain-Driven DesignEventsDiscoveryWorkshop |