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 Competency Questions | ![]() Product Strategy Impact Mapping | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
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. | 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. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-4 Wochen | 2-4 h | 45-90 min | Mehrere Wochen bis Monate |
Participantsdifferent | 5-20 | 2-8 | 3-8 | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Impact Map, Outcome Hypotheses, Delivery Options | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | UX researchTrackingBehavior | OntologyKnowledge graphScopeRequirementsSemantic | OutcomesStrategyBehaviorPlanning | OntologyMethodologyReuseSemanticEngineering |



