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 | ![]() Knowledge Modeling Event Modeling | ![]() Knowledge Modeling Ontology Design Patterns | ![]() Knowledge Modeling Competency Questions |
|---|---|---|---|---|
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. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen | 2-6 h | 1-3 h pro Pattern | 2-4 h |
Participantsdifferent | 5-20 | 2-8 | 1-6 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Event Model, UI Flow, Commands, Read Models | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | UX researchTrackingBehavior | EventsBlueprintDomain-Driven DesignBehavior | OntologyPatternsReuseSemanticModeling | OntologyKnowledge graphScopeRequirementsSemantic |



