North star metric consultant

Most companies don't lack metrics — they lack a hierarchy. Twenty dashboards, each department steering by its favorite number, and executive meetings that relitigate which chart matters. A north star metric exists to end that argument: one measure of delivered value that the whole company agrees predicts long-term revenue, with every team's work laddering into it visibly.

The test of a good north star

It has to be a proxy for value received, not activity generated. At WisOwl AI, signups were the flattering number — 5,000+ of them, acquired organically. But the honest north star is successful matches: a recruiter and a candidate connected in a way that progresses a real hire. Signups can grow while the product fails; matches can't. At CaaStle-style subscription businesses the equivalent is active engaged subscribers, not gross adds — because retention, not acquisition, is where subscription economics live or die. I watched a $30M–$50M ARR portfolio managed with exactly that discipline, and the $2.1M in savings our experimentation program found came from optimizing against retention truth rather than acquisition vanity.

What the engagement produces

• The metric itself, chosen through a structured evaluation: does it capture value delivery, is it measurable weekly, can teams actually influence it, and does it correlate with revenue on your own historical data — not in someone else's blog post.
• A driver tree, decomposing the north star into the three-to-five input metrics each team owns. This is where the framework becomes operational instead of decorative.
• Guardrails, because every north star can be gamed. Optimizing matches shouldn't degrade match quality; optimizing engagement shouldn't manufacture addiction. Guardrail metrics get defined the same day, not after the first incident.
• A review cadence that keeps the metric in charge — and a scheduled reassessment, because north stars have lifespans and outgrow themselves as strategy shifts.

Two to three weeks, leadership workshop included. The deliverable is less the number than the alignment: the moment every team can say how their quarter moves the same metric, most prioritization arguments dissolve on their own.

Frequently asked questions

Can a company have more than one north star metric?

One per product line at most, or the alignment benefit evaporates. What looks like a need for two north stars is usually one value metric plus an unacknowledged guardrail — revenue quality versus growth, for instance — and naming that structure resolves it.

Is revenue a valid north star?

Revenue is the outcome, not the star — it lags value by months and no single team can act on it directly. The north star should be the leading indicator that predicts revenue; put revenue at the top of the driver tree, then steer by the level below it.

How do we know if we picked the wrong one?

Backtest it: if the metric had been rising over the past year, would retention and revenue have followed? Run that correlation on your own cohort data before committing. Post-adoption, the tell is teams hitting the metric while customers get no happier — that's a gamed or hollow star.

How does the north star relate to OKRs?

Cleanly: the north star is stable across quarters; OKRs are the quarterly bets on which driver to push next. Teams that skip the driver tree end up with OKRs disconnected from the star, which recreates the original chaos with more paperwork.

Related pages