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 |  Decision Making Assumption Surfacing |  Agile Specification by Example |  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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 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 | 45-90 min | 60-90 min pro Feature | 45-60 min |
Participantsdifferent | 2-8 | 2-8 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Assumption List, Critical Assumptions, Learning Plan | Example Table, Acceptance Tests | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | AssumptionsRiskDecisionDiscovery | AgileRequirementsExamplesBehavior-Driven Development | AssumptionsRiskExperimentsValidation |