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 |  Agile Specification by Example |
|---|---|---|---|
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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen | 2-8 h | 60-90 min pro Feature |
Participantsdifferent | 5-20 | 5-12 | 3-6 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | UX researchTrackingBehavior | Domain-Driven DesignEventsDiscoveryWorkshop | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
