View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Linked Open Terms | ![]() Decision Making Force Field Analysis | ![]() Product Strategy DIBB | ![]() Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Wochen bis Monate | 45-90 min | 1-2 h | 2-4 h |
Participantsdifferent | 2-8 | 3-12 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Force Field Map, Change Levers, Risk Notes | DIBB document, Belief list, Bet list, Learning report | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | OntologyMethodologyAgileSemantic | ChangeDecisionStrategy | StrategyDecisionAssumptionsHypothesis | OntologyKnowledge graphScopeRequirementsSemantic |



