View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Leverage Points | ![]() Knowledge Modeling Shape-First Modeling | ![]() Knowledge Modeling Competency Questions | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | High | Medium | Medium | Low |
Timedifferent | Half day | Halber Tag pro Domain Slice | 2-4 h | 45-90 min |
Participantsdifferent | 3-12 | 1-4 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Leverage Map, Action Strategy | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Systems thinkingChangeStrategy | Knowledge graphValidationSemantic | OntologyKnowledge graphScopeRequirementsSemantic | ChangeDecisionStrategy |



