North Star Metric

A North Star Metric is the single metric a team agrees best captures the value customers get from a product, used to align every team around one measure of progress instead of a scoreboard of disconnected KPIs. It is the anchor a prioritization framework hangs off, the number every roadmap debate eventually has to answer to.

Nobody can point to a single moment where the North Star Metric was invented, and the growth community has never settled the question cleanly. Ellis has written that Ed Baker, who had led Facebook's international growth team before becoming Uber's first VP of Growth, described his own deep appreciation for the concept when Ellis interviewed him at the 2017 GrowthHackers Conference. That interview helped popularize the term inside the growth community, but it was not the term's origin: Baker was already applying the idea at Facebook and Uber well before that conversation. Amplitude later took the concept and built it into a full framework in its North Star Playbook, adding structure around how a North Star connects the value customers get to the business outcomes it drives. Produck uses Ellis's framing as the definition and Amplitude's structure as the practical model, rather than claiming a tidy origin story neither source actually tells.

A good North Star Metric represents real customer value, not activity. Facebook's early North Star was daily active users tied to its mission. Airbnb tracks nights booked. Spotify tracks time spent listening. Amazon tracks purchases per month. Each of these is a leading indicator of revenue that the team can influence through its work, not a lagging number like MRR that only tells you what already happened.

Why it matters for product-market fit

A North Star Metric only earns its name once it is wired into how a team actually decides what to build. That is where Produck's loop comes in. Listen collects the raw signal, what users are saying and doing. Diagnose sorts that signal into patterns worth acting on. Decide is where the North Star Metric does its job, giving the team a single yardstick to weigh competing feature requests against. Ship closes the loop by putting the change back in front of users and watching whether the metric actually moved.

Without a North Star, Decide becomes a vote based on whoever argued loudest in the last meeting. With one, the question changes from "do we like this idea" to "will this move the number that reflects customer value." That is also why a North Star Metric has to be chosen carefully. Pick the wrong one, chase activation numbers when your real problem is retention, and you can hit your target while the business quietly stalls. Our full breakdown of why this discipline matters for early-stage teams is in what PMF actually means and why it matters so much for startups.

When it works, and when it doesn't

It works when

1. The metric moves because of genuine product usage, not a marketing push or a one-time promotion.
2. The whole team, not just the data analyst, can say the number out loud and explain why it matters.

It falls short when

1. The team can move the metric directly with a single lever, like a discount or a notification blast, instead of it responding to real behavior change.
2. The company swaps its North Star every quarter chasing whatever number looks best, so nobody trusts it enough to plan around it.
3. The metric rewards volume over depth, counting logins or opens instead of the moment a user actually gets value.
4. Multiple teams optimize for different, conflicting North Stars because nobody forced a single company-wide choice.

How to apply it

1. Write down what "value delivered" means for your product in one sentence, in the customer's words, not yours.
2. List three or four candidate metrics that could represent that sentence numerically, and rule out anything that is really just an activity count.
3. Test each candidate against Amplitude's leading-indicator check: does it predict revenue and retention weeks out, or does it only report what already happened.
4. Pick one metric and give it an owner. A North Star with no owner drifts back into a dashboard nobody opens.
5. Wire the metric into your Decide stage so every roadmap item gets scored against whether it plausibly moves that number.
6. Revisit the choice every two quarters, not every sprint. A North Star that changes too often stops functioning as a north star at all.