View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Engineering Goal Question Metric | ![]() Product Strategy Counter Metrics | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 90-180 min | 30-60 min | 60-90 min |
Participantsdifferent | 3-6 | 2-6 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | GQM Table, Metric Profiles | Counter Metric List, Guardrail Definitions | Salience Diagram, Strategy per Class |
Tagsno overlap | MetricsMeasurementEngineeringAlignment | MetricsMeasurementStrategyExperiments | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






