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 |  Decision Making Argument 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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 | 1-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Argument Map, Evidence Gaps, Decision Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Knowledge graphValidationSemantic | SensemakingDecisionRationale | OntologyKnowledge graphScopeRequirementsSemantic |