View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Smoke Test |  Knowledge Modeling Shape-First Modeling |  Knowledge Modeling Competency Questions |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 1-5 Tage | Halber Tag pro Domain Slice | 2-4 h | 1-4 Wochen |
Participantsdifferent | Nutzertraffic | 1-4 | 2-8 | 1-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationExperimentsDemandGrowth | Knowledge graphValidationSemantic | OntologyKnowledge graphScopeRequirementsSemantic | ExperimentsGrowthAnalyticsValidation |