North Star Metric

In Kyle’s notes the North Star Metric surfaces as part of the Product Led Growth — The End User Era vocabulary (alongside PQLs, viral coefficient, and land-and-expand), but the book’s most pointed lesson is a cautionary one about how a North Star can backfire. The case study: a Customer Success department chose Net Revenue Retention as its North Star Metric. It was “very motivating for my team,” but “ultimately did more harm than good” — because other departments assumed Customer Success “had retention covered” and dropped it from their own quarterly goals. The typical refusal was, “Improving net retention isn’t part of my OKRs, so I can’t prioritize this project.” Naming one team the owner of a cross-functional metric let everyone else off the hook.

The resolution Kyle preserves is a reframe rather than an abandonment: the team kept net retention as its North Star but “shifted from being the ‘owner’ of net retention to becoming the ‘champions.’” The takeaway in the wiki’s reading is that a North Star Metric is only healthy when the whole org shares accountability for it — better to champion a number across teams than to own it alone.

Context: A “North Star Metric” is a product-management term for the single measure that best captures the core value a product delivers to customers; teams rally around it to align prioritization. The framing was popularized in the growth/SaaS community.

Where this appears

• Product Led Growth — The End User Era — used as a PLG vocabulary term, and the source of the “owner vs. champion” org lesson, where making Net Revenue Retention one team’s North Star let other teams off the hook.