View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Stakeholder Salience Model | ![]() Growth Pirate Metrics AARRR | ![]() Engineering Goal Question Metric | ![]() Growth North Star Metric |
|---|---|---|---|---|
Purposedifferent | 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. | For products with complex usage paths, overall growth alone is too coarse to reveal bottlenecks. Pirate Metrics breaks the relationship with the product into consecutive stages and shows where the funnel actually leaks. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 60-90 min | 1-2 h Setup, laufend | 90-180 min | 1-2 h |
Participantsdifferent | 3-6 | 2-8 | 3-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Salience Diagram, Strategy per Class | AARRR funnel, Metric baseline, Experiment backlog | GQM Table, Metric Profiles | North Star metric, Input metric tree, Measurement cadence |
Tagsno overlap | StakeholdersFacilitationAlignmentGovernance | GrowthMetricsExperiments | MetricsMeasurementEngineeringAlignment | GrowthMetricsAlignmentRetention |



