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 Concept Mapping |  Knowledge Modeling Shape-First Modeling |  Knowledge Modeling Knowledge Mapping |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 h | Halber Tag pro Domain Slice | 1-3 h | 2-4 h |
Participantsdifferent | 1-8 | 1-4 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Knowledge graphValidationSemantic | KnowledgeMappingRisk | OntologyKnowledge graphScopeRequirementsSemantic |