View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy DIBB |  Knowledge Modeling Property Graph Schema Design |  Decision Making Force Field Analysis |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 1-2 h | 4-8 h initial, dann iterativ | 45-90 min | 2-4 h |
Participantsdifferent | 2-8 | 1-6 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | DIBB document, Belief list, Bet list, Learning report | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Force Field Map, Change Levers, Risk Notes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | StrategyDecisionAssumptionsHypothesis | Knowledge graphModelingSemantic | ChangeDecisionStrategy | OntologyKnowledge graphScopeRequirementsSemantic |