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 |  Product Discovery Assumption Mapping |  Decision Making Force Field Analysis |  Product Strategy DIBB |
|---|---|---|---|---|
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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-4 h | 45-60 min | 45-90 min | 1-2 h |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Assumption map, Test backlog, Risk ranking | Force Field Map, Change Levers, Risk Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | AssumptionsRiskExperimentsValidation | ChangeDecisionStrategy | StrategyDecisionAssumptionsHypothesis |