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 Shape-First Modeling |  Delivery RAID Log |  Decision Making Assumption Surfacing |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Halber Tag pro Domain Slice | 30 min Setup, dann laufend | 45-90 min | 2-4 h |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphValidationSemantic | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery | OntologyKnowledge graphScopeRequirementsSemantic |