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 | ![]() Engineering Goal Question Metric | ![]() Product Strategy Counter Metrics |
|---|---|---|---|
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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 2-4 h | 90-180 min | 30-60 min |
Participantsdifferent | 2-8 | 3-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | GQM Table, Metric Profiles | Counter Metric List, Guardrail Definitions |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | MetricsMeasurementEngineeringAlignment | MetricsMeasurementStrategyExperiments |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






