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 EventStorming |  Decision Making Force Field Analysis |  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 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | 2-8 h | 45-90 min | 2-6 h |
Participantsdifferent | 5-20 | 5-12 | 3-12 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Force Field Map, Change Levers, Risk Notes | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | UX researchTrackingBehavior | Domain-Driven DesignEventsDiscoveryWorkshop | ChangeDecisionStrategy | EventsBlueprintDomain-Driven DesignBehavior |