View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Argument Mapping |  Knowledge Modeling Property Graph Schema Design |  Knowledge Modeling Concept Mapping |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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-3 h | 4-8 h initial, dann iterativ | 1-2 h | 2-4 h |
Participantsdifferent | 1-8 | 1-6 | 1-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Concept Map, Relationship Labels, Knowledge Gaps | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | SensemakingDecisionRationale | Knowledge graphModelingSemantic | KnowledgeConceptsMappingSensemaking | OntologyKnowledge graphScopeRequirementsSemantic |