View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Map |  Facilitation Stakeholder Salience Model |  Product Strategy Counter Metrics |  Engineering Goal Question Metric |
|---|---|---|---|---|
Purposedifferent | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | 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. | 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 workshop plus review | 60-90 min | 30-60 min | 90-180 min |
Participantsdifferent | 4-10 | 3-6 | 2-6 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | Salience Diagram, Strategy per Class | Counter Metric List, Guardrail Definitions | GQM Table, Metric Profiles |
Tagsno overlap | AlignmentExecutionGoalsCausality | StakeholdersFacilitationAlignmentGovernance | MetricsMeasurementStrategyExperiments | MetricsMeasurementEngineeringAlignment |