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 | ![]() Product Discovery Assumption Mapping | ![]() Agile Specification by Example | ![]() Product Discovery Riskiest Assumption 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-4 h | 45-60 min | 60-90 min pro Feature | 1-2 Wochen pro Iteration |
Participantsdifferent | 2-8 | 2-8 | 3-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Assumption map, Test backlog, Risk ranking | Example Table, Acceptance Tests | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | AssumptionsRiskExperimentsValidation | AgileRequirementsExamplesBehavior-Driven Development | ExperimentsValidationDiscoveryAssumptions |



