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 |  Agile Example Mapping |  Product Discovery Test Card |  Product Discovery Fake Door Test |
|---|---|---|---|---|
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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2-4 h | 30-60 min | 20-35 min | 1-5 Tage |
Participantsdifferent | 2-8 | 3-7 | 1-5 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Map, Acceptance Criteria, Open Questions | Test Card with a pre-set threshold | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ExperimentsValidationDiscoveryHypothesis | ValidationExperimentsDemandDiscovery |