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 |  Product Discovery Assumption Mapping |  Engineering Goal Question Metric |  Growth Pirate Metrics AARRR |
|---|---|---|---|---|
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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 h | 45-60 min | 90-180 min | 1-2 h Setup, laufend |
Participantsdifferent | 3-8 | 2-8 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | North Star metric, Input metric tree, Measurement cadence | Assumption map, Test backlog, Risk ranking | GQM Table, Metric Profiles | AARRR funnel, Metric baseline, Experiment backlog |
Tagsno overlap | GrowthMetricsAlignmentRetention | AssumptionsRiskExperimentsValidation | MetricsMeasurementEngineeringAlignment | GrowthMetricsExperiments |