Quick Answer (TL;DR)
A North Star metric is the single metric that best captures the core value your product delivers to users. It aligns every team around one outcome, filters noise from vanity metrics, and serves as a leading indicator of sustainable revenue growth.
Summary: Your North Star metric answers the question: "If this number goes up, does it mean users are getting more value from our product?" Revenue alone does not qualify because it lags behind the user behavior that drives it. A North Star metric sits between product activity and revenue, measuring the moment users receive value.
Key characteristics:
- Measures value delivered to users, not just business output
- Acts as a leading indicator of revenue growth
- The product team can directly influence it through roadmap decisions
Time to implement: 1-2 weeks for selection, ongoing for embedding into team rituals.
Best for: PMs, product leaders, founders, growth teams, anyone responsible for product strategy.
What Is a North Star Metric?
A North Star metric (NSM) is the single measurement that best reflects the value your product creates for its users. It is the one number that, when it grows, signals that your product is healthy and your business will follow.
The concept was popularized by Sean Ellis and the growth hacking community in the mid-2010s, but the idea is older. Product-led companies like Facebook ("daily active users") and Airbnb ("nights booked") had been using this approach for years before it had a name.
The purpose of a North Star metric is alignment. In any product organization with more than a handful of people, teams pull in different directions. Marketing optimizes for signups. Sales pushes for revenue. Engineering prioritizes technical debt. A North Star metric gives everyone a shared answer to the question: "Are we winning?"
This is not the same as picking your most important KPI. A North Star metric has specific properties that distinguish it from general performance tracking. It measures the value exchange between your product and its users, not just the business outcome you hope follows from that exchange.
For a deeper look at how the North Star framework operates in practice, including input metrics and the full metric tree, see the North Star Framework glossary entry.
Why North Star Metrics Work
Aligns teams around a single outcome
Product organizations suffer from a fragmentation problem. Each function has its own dashboards, its own targets, its own definition of success. A North Star metric creates a shared scoreboard. When marketing, product, engineering, and customer success all track the same number, trade-off conversations get simpler. Instead of debating which team's KPI matters more, you ask: "Which option moves the North Star?"
Distinguishes value from vanity
Vanity metrics feel good but do not predict business health. Page views, total registered users, and app downloads all go up and to the right without meaning much. A North Star metric forces you to identify the action that proves users are getting value. This is a harder question to answer, but the answer is far more useful.
If your product is a project management tool, total signups tells you how many people tried it. Weekly active projects tells you how many people found it valuable enough to use for real work. The second metric is a North Star candidate. The first is not.
Leading indicator of revenue
Revenue is a lagging indicator. By the time a subscription renews or churns, the user's experience was shaped weeks or months earlier. A North Star metric captures the behavior that predicts future revenue. If weekly active projects drops this month, you will see churn increase next quarter. Catching the signal early gives you time to intervene.
This is why revenue itself makes a poor North Star metric. It tells you what already happened, not what is about to happen.
The Three Traits of a Good North Star Metric
Not every metric qualifies. A good North Star metric passes three tests.
1. It measures value delivered to users
The metric should reflect a moment when the user receives value, not just when the business captures revenue. For Spotify, that moment is when someone listens to music. For Slack, it is when a team communicates. For Amplitude, it is when a user learns something from their data.
Ask: "If this metric goes up but users are unhappy, is that possible?" If the answer is yes, the metric does not capture value delivery. Total messages sent in Slack could go up because of spam or mandatory compliance notifications. Messages sent per team per week is harder to game because it reflects genuine team communication.
2. It is a leading indicator of revenue
If your North Star metric grows but revenue stays flat for years, you chose the wrong metric. There should be a demonstrable correlation. This does not mean you need a perfect regression model. It means you should be able to explain, in plain language, why more of this metric leads to more revenue.
"More weekly active projects means more teams depend on our tool, which increases expansion revenue and reduces churn." That logic chain works. If you cannot construct one, your metric is too far from the money.
3. The product team can directly influence it
If your North Star metric depends entirely on sales, marketing, or macroeconomic conditions, the product team cannot use it to make roadmap decisions. The metric should respond to product changes: better onboarding, new features, UX improvements, performance gains.
This does not mean the product team is the only team that influences it. Marketing drives awareness that feeds the top of the funnel. Sales closes deals that add users. But the product team should be able to move the number through the choices they make about what to build and how to build it.
Real North Star Metric Examples
Here are NSMs from well-known product-led companies, along with why each metric works.
| Company | North Star Metric | Why It Works |
|---|---|---|
| Spotify | Time spent listening | Directly measures the core value (music enjoyment). Correlates with subscription retention. |
| Airbnb | Nights booked | Captures the complete value exchange between hosts and guests. Revenue follows directly. |
| Slack | Messages sent per team per week | Reflects active team communication. Teams that message more are stickier and expand seats. |
| HubSpot | Weekly active teams using 5+ features | Measures depth of engagement, not just login frequency. Predicts expansion and retention. |
| Amplitude | Weekly learning users | Users who query data weekly are getting analytical value. Correlates with contract renewal. |
| Shopify | Gross merchandise volume (GMV) | When merchants sell more, Shopify's revenue share grows. Merchant success equals platform success. |
Notice the pattern. Each metric captures the moment the user gets what they came for. Spotify does not use "songs added to playlist" because adding songs is preparation, not value delivery. Airbnb does not use "searches" because searching is exploration, not the value exchange.
For more on which metrics actually predict SaaS business health, see The Only Metrics That Matter in B2B SaaS.
How to Choose Your North Star Metric
Choosing a North Star metric is a strategic decision, not a data exercise. Here is a five-step process that works for most product teams.
Step 1: Identify the core value action
Ask your team: "What is the one thing users do in our product that proves they got value?" This is usually not the first thing they do (signup) or the last thing (payment). It is the action in between that makes them stay.
For a design tool, it might be "designs exported." For an analytics platform, it might be "dashboards viewed." For a product-led growth company, it is often the activation event that separates retained users from churned ones.
If you are unsure, look at your retention curves. Segment users by behavior and find the action that best separates users who retain from those who churn. That action is your candidate.
Step 2: Check the three traits
Run your candidate through the three tests above. Does it measure user value? Is it a leading indicator of revenue? Can the product team influence it?
If it fails any test, iterate. "Active users" often fails the value test because it counts logins, not value moments. "Revenue" fails the leading indicator test. "Brand awareness" fails the product influence test.
Step 3: Set input metrics (the levers)
A North Star metric on its own is too high-level to act on. Break it into 3-5 input metrics that the team can move directly. These are the levers.
For example, if your North Star is "weekly active projects":
- Breadth: Number of users creating projects
- Depth: Average actions per project per week
- Frequency: Percentage of users active 3+ days per week
- Activation: Percentage of new users who create a project in the first session
Each input metric can be assigned to a squad or initiative. This is where the North Star framework becomes operational.
Step 4: Validate with historical data
Before committing, backtest your candidate against historical revenue data. If your North Star metric went up last quarter, did revenue follow? If it dropped, did churn increase?
You do not need a perfect R-squared. You need a directional relationship. If the correlation is weak or nonexistent, your metric is too far from the revenue engine.
Use IdeaPlan's North Star Finder tool to evaluate candidate metrics against these criteria and get a structured recommendation.
Step 5: Communicate and embed
A North Star metric only works if everyone knows it. Put it on every dashboard. Mention it in every all-hands. Make it the first question in every product review: "How did our North Star move this week?"
The metric should show up in three places at minimum:
- Executive dashboards and board decks
- Team-level sprint goals and retrospectives
- Individual 1:1s between PMs and their managers
If people have to search for it, it is not embedded enough.
North Star Metrics vs. OKRs vs. KPIs
These three concepts overlap but serve different purposes. Understanding the distinction prevents common misuse.
| North Star Metric | OKRs | KPIs | |
|---|---|---|---|
| Scope | One metric, company-wide | 3-5 objectives per team per cycle | Many metrics per function |
| Time horizon | Stable for 1-3 years | Quarterly or annual | Ongoing |
| Purpose | Align the whole org around user value | Set time-bound goals for specific outcomes | Track operational health |
| Example | Weekly active projects | "Increase activation rate from 40% to 55% by Q2" | Signup conversion rate, page load time, NPS |
Your North Star metric should inform your OKRs. Each quarter, teams set OKRs that target input metrics feeding the North Star. KPIs track the operational details beneath those inputs.
For a deeper comparison of these systems, see North Star Metric vs. OKRs and OKRs vs. KPIs.
The North Star Framework in Practice
Choosing the metric is only the beginning. The North Star framework includes the metric, its input metrics, and a regular review cadence.
The input metrics tree
Visualize your North Star metric at the top, with 3-5 input metrics branching below it. Each input metric can be further decomposed into initiative-level metrics.
Example for a B2B SaaS product (NSM: Weekly Active Teams):
Weekly Active Teams
āāā New team activation rate (% of new teams active in week 1)
āāā Feature adoption breadth (avg features used per team)
āāā Collaboration depth (avg members active per team)
āāā Retention rate (% of teams active this week vs. last week)Each branch is owned by a specific team or squad. The activation team owns new team activation. The core product team owns feature adoption. The growth team owns retention. This structure makes it clear who is responsible for moving each lever.
Weekly review cadence
A North Star metric needs a ritual. Without one, it becomes a poster on the wall that nobody looks at.
Monday: Product leadership reviews the North Star and input metrics. Identify any significant changes from last week. Flag emerging problems.
Wednesday: Individual squads review their input metric. Connect it to the initiatives they shipped or are running. Identify blockers.
Friday: Weekly digest shared org-wide. One paragraph: "Our North Star moved from X to Y this week. Here is what drove the change."
This cadence keeps the metric alive. It turns an abstract concept into a concrete, weekly conversation. For a full breakdown of the metrics that matter most for SaaS products, see The Complete Guide to Product Metrics.
Common North Star Metric Mistakes
Choosing a vanity metric
"Total registered users" is the most common bad North Star metric. It only goes up. It does not reflect whether anyone is getting value. A better alternative is almost always an engagement or activity metric scoped to a meaningful time window (weekly or monthly).
Using revenue as the North Star
Revenue is important, but it is a lagging outcome, not a measure of user value. If you use revenue as your North Star, every team optimizes for extraction (pricing, upsells, fee structures) instead of value creation. The products that grow fastest long-term are the ones that optimize for user value and let revenue follow.
Making it too complex
"Weekly active users who completed onboarding and used at least two core features within a 7-day rolling window, excluding trial accounts." If your North Star metric requires a paragraph to define, nobody will remember it. Simplicity is a feature. The metric should be explainable in one sentence.
Never revisiting it
Your North Star metric should be stable, but not permanent. If your business model changes, your product expands into new markets, or you discover the metric no longer correlates with revenue, it is time to reassess. Schedule an annual review where you validate the metric against current data.
Ignoring feature adoption signals
A North Star metric measures aggregate product value, but it can mask problems at the feature level. If your North Star is growing because of one popular feature while three others sit unused, you have a portfolio problem. Pair your North Star with feature-level adoption tracking to catch these blind spots early.
Key Takeaways
- A North Star metric is the single metric that best reflects the value your product delivers to users. It is not a vanity metric and it is not revenue.
- A good North Star metric passes three tests: it measures user value, it leads revenue, and the product team can influence it.
- Break the North Star into 3-5 input metrics that teams can act on directly. The metric alone is too high-level to drive daily decisions.
- North Star metrics, OKRs, and KPIs serve different purposes. The North Star is the permanent compass. OKRs are quarterly waypoints. KPIs are operational gauges.
- Embed the metric into weekly rituals. A North Star metric that only appears in board decks is a decoration, not a tool.
- Revisit annually but change rarely. If you are swapping North Star metrics every quarter, you have a product strategy problem, not a metrics problem.
Start by identifying the core value action in your product, then validate it against the three traits. Use the North Star Finder to evaluate your candidates, and read the Product Analytics Handbook for the full system of metrics, dashboards, and review processes that make your North Star metric operational.