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 | ![]() Growth North Star Metric | ![]() Facilitation Stakeholder Mapping | ![]() 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 product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Medium | Low | Medium |
Timedifferent | 90-180 min | 1-2 h | 60–90 min | 60-90 min |
Participantsdifferent | 3-6 | 3-8 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | GQM Table, Metric Profiles | North Star metric, Input metric tree, Measurement cadence | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tags1 shared | MetricsMeasurementEngineeringAlignment | GrowthMetricsAlignmentRetention | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |



