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 Force Field Analysis |  Knowledge Modeling Competency Questions |  Systems Thinking Leverage Points |
|---|---|---|---|---|
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 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. | 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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | Halber Tag pro Domain Slice | 45-90 min | 2-4 h | Half day |
Participantsdifferent | 1-4 | 3-12 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Force Field Map, Change Levers, Risk Notes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Leverage Map, Action Strategy |
Tagsno overlap | Knowledge graphValidationSemantic | ChangeDecisionStrategy | OntologyKnowledge graphScopeRequirementsSemantic | Systems thinkingChangeStrategy |