North Star Metric: How to Choose Yours in 6 Weeks

8 min read ยท 2026-10-10

A north star metric is the single number that best shows how much real value customers get from your product. To choose yours, write down the value customers come to you for and list 3 to 5 numbers that measure that value. Keep the one that predicts revenue and that your team can move. Then split it into a few input metrics that teams can work on each week.

A team can follow this plan in about 6 weeks. The roadmap below covers each step, from the first workshop to the first quarterly review. It also gives examples by product type and lists the mistakes that make a North Star Metric useless.

The roadmap at a glance

Goal: Choose one North Star Metric, define it precisely, link it to input metrics and make it the number the whole team works on. Duration: 6 weeks, then a review every quarter

  1. Define the value you deliver (Week 1)

    Agree on what "getting value" means for your customers before you talk about numbers.

    • Write the value in one sentence: "Customers use us so that they can X."
    • Interview 5 to 10 active customers, or re-read your notes from past calls, to check that X is what they actually say.
    • Name the moment a customer first gets that value (the first report sent, the first booking made, the first lesson finished).
    • Identify who the customer is: the user, the buyer, or both.

    Milestone: A one sentence value statement signed off by the founder or head of product.

  2. List candidate metrics (Week 2)

    Turn the value statement into 3 to 5 numbers you could track.

    • For each candidate, write the exact event, the unit (users, teams, accounts) and the time window (per week, per month).
    • Include at least one breadth metric (how many customers get value) and one depth metric (how much value each one gets).
    • Check that each event is already tracked, or note what tracking is missing.
    • Remove any candidate that only measures your own activity, such as emails sent or features shipped.

    Milestone: A written shortlist of 3 to 5 candidates, each with a precise definition.

  3. Test the candidates (Week 3)

    Find out which candidate behaves like a real signal of value.

    • Pull at least 6 months of history for each candidate, if you have it.
    • Compare each one with retention and revenue: does it go up before they do?
    • Score each candidate on the five tests listed further down.
    • Ask 3 people from different teams to explain each candidate in one sentence. If they cannot, it is too complex.

    Milestone: A scored comparison with one clear winner, or two finalists.

  4. Lock the definition (Week 4)

    Make the chosen metric impossible to misread.

    • Write the final definition: event, unit, time window and filters (for example, excluding internal accounts and test data).
    • Name one owner who answers for the number and its data quality.
    • Measure today's level as a baseline and set a realistic target for the next quarter.
    • Build one dashboard view that shows the metric and its trend.

    Milestone: A one page metric definition and a live dashboard everyone can open.

  5. Map the input metrics (Week 5)

    Break the North Star into levers that teams can move week by week.

    • List the 3 to 5 factors that drive the metric, usually some mix of breadth, depth, frequency and efficiency.
    • Give each input metric an owner team.
    • Check that each roadmap initiative is linked to at least one input metric.
    • Drop or pause initiatives that move none of them.

    Milestone: A metric tree with the North Star at the top and owned input metrics below it.

  6. Roll out and review (Week 6, then every quarter)

    Make the metric part of how the team works, not a slide that gets forgotten.

    • Present the metric, its definition and its inputs at an all hands meeting.
    • Add it to the weekly team meeting and to every roadmap review.
    • Set a quarterly check: is the metric still tied to value and revenue?
    • Write down what would make you change it, so the decision is not made on a whim.

    Milestone: The North Star Metric is on the agenda of the first weekly review and the first roadmap review.

What a North Star Metric is, and what it is not

A North Star Metric measures the value customers receive. It is a leading indicator: when it grows, retention and revenue should follow later. That is why it works as a guide for product decisions. Revenue tells you what already happened. A good North Star tells you what is about to happen.

It is not a goal, a vanity number or a full dashboard. "Reach X customers by December" is a goal. Total sign ups and page views are vanity numbers, because they can grow while customers get nothing. A dashboard with twenty numbers is not a North Star either, because nobody can focus on twenty things. You keep one number at the top and a few input metrics beneath it.

The five tests a good North Star Metric must pass

Run every candidate through these five questions. A metric that fails one of them is a weak choice.

One more useful check: imagine the metric doubled while revenue stayed flat. If that is easy to picture, the metric probably measures activity, not value.

  • Reflects customer value: does it count what customers get, not what our company does?
  • Predicts revenue: when it rises, do paying customers and renewals rise later?
  • Team can influence it: can product, marketing and support work move it within weeks or months?
  • Easy to explain: can anyone in the company say what it means in one sentence?
  • Measurable and stable: can we track it the same way every week, with data we trust?

North Star Metric examples by product type

The right metric depends on how your product creates value. These patterns are common starting points. Treat them as ideas to test, not answers to copy.

Notice the shape. Each example joins a unit (teams, learners, accounts) with an action that means value (completing, buying, learning) and a time window. If your candidate is missing one of those three parts, make it more precise before you test it.

For full product plans built around metrics like these, see our B2B SaaS product roadmap and these product roadmap examples.

  • Team collaboration tool: weekly active teams that complete a shared task (teams, complete a shared task, per week).
  • Marketplace: completed transactions between buyers and sellers (transactions, completed, per month).
  • Media or content app: time spent consuming content per active user (active users, consume content, per week).
  • Learning app: lessons completed per active learner (learners, complete a lesson, per week).
  • B2B analytics product: accounts that view or share a report (accounts, view or share a report, per week).
  • E-commerce brand: repeat purchases per customer (customers, buy again, within a set period).

How to connect your North Star Metric to your roadmap

A North Star Metric only helps if it shapes what you build. Input metrics make the link. Each one describes a lever, and each roadmap initiative should push at least one lever. For a learning app, the inputs could be new learners who finish a first lesson, learners who come back in their second week, and lessons completed per session.

Once the inputs are clear, review your roadmap with three questions.

This turns roadmap debates into clearer choices. Instead of "this feature feels important", the discussion becomes "this feature should lift second week returns, and here is how we will check". Initiatives that move no input are easier to cut or postpone.

  • Which input metric does this initiative move?
  • How will we know, within a few weeks of release, whether it moved?
  • What would we stop doing to make room for it?

How to roll it out so the team actually uses it

Choosing the metric is the easy part. Keeping it alive is harder. Start by sharing the full definition, not only the name. "Weekly active teams" means nothing until people know what "active" means and which accounts are excluded. Then put the number where decisions happen.

Finally, protect the metric from gaming. If a team can raise the number without helping customers, someone eventually will. Pair the North Star with a guardrail metric, such as churn, refund requests or support tickets, so growth that hurts customers shows up quickly.

  • At the top of the weekly team meeting, with the trend over the last few weeks.
  • In every roadmap or sprint review, next to the input metrics each initiative targets.
  • In onboarding material for new hires, so they learn it in their first week.
  • In the quarterly planning document, with the target for the next quarter.

When to change your North Star Metric

A North Star Metric should stay in place for a long time, but not forever. Changing it every quarter confuses the team and makes trends impossible to read. Changing it too late keeps everyone working on the wrong thing.

Good reasons to revisit it include a change in business model (for example, moving from one time purchases to subscriptions), a new main customer segment, or clear data showing that the metric no longer predicts retention or revenue. When you change it, run the same 6 week process again and keep the old metric visible for a while so you can compare. Our guide on how often to update your roadmap explains how to fit this review into your planning rhythm.

Common mistakes to avoid

  • Choosing revenue as the North Star gives you a lagging result. Pick a value metric that predicts revenue instead.
  • Picking a vanity count like total sign ups hides whether anyone gets value. Measure an action that shows real use.
  • Letting every team invent its own North Star splits the company's focus. Keep one company metric and give teams input metrics.
  • Leaving the definition vague creates arguments over the numbers. Write the event, unit, time window and filters on one page.
  • Tracking the metric without a guardrail invites shortcuts that hurt customers. Pair it with churn or another quality signal.
  • Never revisiting the metric lets it drift away from value. Check it every quarter against retention and revenue.

Frequently asked questions

What is a North Star Metric in simple terms?

It is the one number that best shows customers getting real value from your product. When it grows, retention and revenue should grow later. It guides product and roadmap decisions across the whole team.

Can a company have more than one North Star Metric?

A company should have one North Star Metric. If it has several, teams pull in different directions and the metric loses its purpose. Use 3 to 5 input metrics underneath it to give each team a lever of its own.

What is the difference between a North Star Metric and a KPI?

A KPI is any key number you track, such as revenue, churn or support response time. The North Star Metric is the single KPI chosen to represent customer value and guide product decisions. All other KPIs either feed into it or act as guardrails.

How often should you review your North Star Metric?

Track it every week and review the choice itself every quarter. The quarterly check asks whether the metric still predicts retention and revenue. Change it only for a clear reason, such as a new business model or a new main customer segment.

Generate this roadmap with AI