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 Assumption Mapping |  Knowledge Modeling Linked Open Terms |  Agile Example Mapping |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 45-60 min | Wochen bis Monate | 30-60 min | 2-4 h |
Participantsdifferent | 2-8 | 2-8 | 3-7 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Assumption map, Test backlog, Risk ranking | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Example Map, Acceptance Criteria, Open Questions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | AssumptionsRiskExperimentsValidation | OntologyMethodologyAgileSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyKnowledge graphScopeRequirementsSemantic |