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 | ![]() Domain Modeling Domain Context Map | ![]() UX Research Card Sorting | ![]() Knowledge Modeling Event Modeling |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-4 Wochen | 1-3 h | 20-45 min | 2-6 h |
Participantsdifferent | 5-20 | 3-10 | Based on research question | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Domain Context Map, Boundary Notes, Ownership Map | Content groups, Label set, IA hypotheses | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | UX researchTrackingBehavior | Domain-Driven DesignContextBoundaries | Information architectureNavigationStructure | EventsBlueprintDomain-Driven DesignBehavior |



