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 |  Knowledge Modeling Property Graph Schema Design |  Knowledge Modeling Shape-First Modeling |
|---|---|---|---|---|
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. | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-4 h | 45-60 min | 4-8 h initial, dann iterativ | Halber Tag pro Domain Slice |
Participantsdifferent | 2-8 | 2-8 | 1-6 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Assumption map, Test backlog, Risk ranking | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | AssumptionsRiskExperimentsValidation | Knowledge graphModelingSemantic | Knowledge graphValidationSemantic |