View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Growth North Star Metric | ![]() Engineering Goal Question Metric | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 h | 90-180 min | 60–90 min |
Participantsdifferent | 3-8 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | North Star metric, Input metric tree, Measurement cadence | GQM Table, Metric Profiles | Stakeholder Map, Engagement Plan, Risk Notes |
Tags1 shared | GrowthMetricsAlignmentRetention | MetricsMeasurementEngineeringAlignment | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






