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 |  Architecture Risk Storming |  Knowledge Modeling Shape-First Modeling |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-4 h | 60-90 min | Halber Tag pro Domain Slice | 45-60 min |
Participantsdifferent | 2-8 | 4-12 | 1-4 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Annotated Diagram, Prioritized Risk List, Action Backlog | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | RiskArchitectureWorkshopValidation | Knowledge graphValidationSemantic | AssumptionsRiskExperimentsValidation |