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 |  UX Research HEART Framework |  Product Strategy Counter Metrics |  Engineering Goal Question Metric |
|---|---|---|---|---|
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 observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 120 min initial, dann laufend | 30-60 min | 90-180 min |
Participantsdifferent | 2-8 | 3-6 | 2-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | HEART-GSM Table, Dashboard | Counter Metric List, Guardrail Definitions | GQM Table, Metric Profiles |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | MetricsUX researchMeasurementSatisfaction | MetricsMeasurementStrategyExperiments | MetricsMeasurementEngineeringAlignment |