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 Context Map | ![]() Decision Making Delphi Method | ![]() 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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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 | High | Medium |
Timedifferent | 1-4 Wochen | 1-3 h | 1-4 Wochen | 2-6 h |
Participantsdifferent | 5-20 | 2-8 | 6-30 Experten | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Context Map, Integration Patterns, Boundary Notes | Expert Forecast, Consensus Range, Assumption Notes | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | UX researchTrackingBehavior | Domain-Driven DesignBoundariesStrategy | ForecastingExpertsDecisionStrategy | EventsBlueprintDomain-Driven DesignBehavior |



