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 Shape-First Modeling | ![]() Decision Making OODA Loop | ![]() Knowledge Modeling Competency Questions | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | Halber Tag pro Domain Slice | 15-60 min je Zyklus | 2-4 h | 45-90 min |
Participantsdifferent | 1-4 | 1-8 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Situation Assessment, Decision Loop, Action Updates | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Knowledge graphValidationSemantic | DecisionChangeLearningStrategy | OntologyKnowledge graphScopeRequirementsSemantic | ChangeDecisionStrategy |



