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 |  Growth A/B Testing |  Architecture Risk Storming |  Knowledge Modeling Shape-First Modeling |
|---|---|---|---|---|
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. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 2-4 h | 1-4 Wochen | 60-90 min | Halber Tag pro Domain Slice |
Participantsdifferent | 2-8 | 1-6 | 4-12 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Experiment results, Decision log, Learning summary | Annotated Diagram, Prioritized Risk List, Action Backlog | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ExperimentsGrowthAnalyticsValidation | RiskArchitectureWorkshopValidation | Knowledge graphValidationSemantic |