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 Competency Questions |  Knowledge Modeling Property Graph Schema Design |  Systems Thinking Leverage Points |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. | 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. | 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 | High | Low |
Timedifferent | 2-4 h | 4-8 h initial, dann iterativ | Half day | 45-90 min |
Participantsdifferent | 2-8 | 1-6 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Leverage Map, Action Strategy | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphModelingSemantic | Systems thinkingChangeStrategy | ChangeDecisionStrategy |