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 Evaporating Cloud |  Product Strategy DIBB |  Knowledge Modeling Competency Questions |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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 | Low | Medium | Low |
Timedifferent | 60-120 min | 1-2 h | 2-4 h | 45-90 min |
Participantsdifferent | 2-8 | 2-8 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | DIBB document, Belief list, Bet list, Learning report | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | StrategyDecisionAssumptionsHypothesis | OntologyKnowledge graphScopeRequirementsSemantic | ChangeDecisionStrategy |