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 |  Knowledge Modeling Shape-First Modeling |  Decision Making Assumption Surfacing |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 60-120 min | Halber Tag pro Domain Slice | 45-90 min | 2-4 h |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Assumption List, Critical Assumptions, Learning Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Knowledge graphValidationSemantic | AssumptionsRiskDecisionDiscovery | OntologyKnowledge graphScopeRequirementsSemantic |