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 | ![]() Knowledge Modeling Shape-First Modeling | ![]() Decision Making Assumption Surfacing | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | Halber Tag pro Domain Slice | 45-90 min | 45-60 min |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Assumption List, Critical Assumptions, Learning Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphValidationSemantic | AssumptionsRiskDecisionDiscovery | AssumptionsRiskExperimentsValidation |



