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 Competency Questions | ![]() Systems Thinking Leverage Points | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | 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. | 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 | Low | Medium | High | Low |
Timedifferent | 1-2 h | 2-4 h | Half day | 45-90 min |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | DIBB document, Belief list, Bet list, Learning report | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Leverage Map, Action Strategy | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | StrategyDecisionAssumptionsHypothesis | OntologyKnowledge graphScopeRequirementsSemantic | Systems thinkingChangeStrategy | ChangeDecisionStrategy |



