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 |  Systems Thinking Evaporating Cloud |  Domain Modeling EventStorming |  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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen | 60-120 min | 2-8 h | 2-6 h |
Participantsdifferent | 5-20 | 2-8 | 5-12 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | UX researchTrackingBehavior | Theory of ConstraintsAssumptionsSystems thinking | Domain-Driven DesignEventsDiscoveryWorkshop | EventsBlueprintDomain-Driven DesignBehavior |