North Star Metrics
A north star metric is the single number that best captures the core value your product delivers to users. Spotify's is time spent listening. Airbnb's is nights booked. Slack's is messages sent. Facebook's was daily active users. Each of these metrics reflects the moment when a user gets real value from the product — and when that number goes up, the business grows.
Why One Metric Matters
Companies drown in data. Dashboards show dozens of charts. Every team tracks different KPIs. Leadership reviews a spreadsheet with forty metrics, and nobody can agree on what matters most. The result is diffusion of effort: teams optimize for their local metric while the overall product stagnates.
A north star metric solves three problems:
1. Focus: Everyone knows what we're optimizing for.
Debates about priorities become simpler:
"Does this move the north star?"
2. Alignment: Cross-functional teams share a common goal.
Engineering, design, marketing, and support
all understand what success looks like.
3. Clarity: New hires, board members, and investors can
understand the company's health from one number.
"Nights booked is up 15% quarter over quarter"
tells a clear story.
One metric does not mean you ignore everything else. It means you have a hierarchy. The north star sits at the top, and everything else is evaluated by whether it contributes to that number.
Characteristics of a Good North Star Metric
Not every metric qualifies. A good north star metric has specific properties:
It Reflects Value Delivered to Users
Revenue is not a north star metric. Revenue reflects value captured by the company, not value delivered to users. A product can increase revenue by raising prices, adding fees, or making cancellation harder — none of which deliver more value. The north star should measure the thing users actually care about.
Revenue-focused (not north star):
- Monthly recurring revenue
- Average revenue per user
- Gross merchandise value
Value-focused (candidate north stars):
- Spotify: Time spent listening (users came for music; listening = value)
- Airbnb: Nights booked (travelers came for accommodation; booking = value)
- Slack: Messages sent (teams came for communication; messaging = value)
- Uber: Rides completed (riders came for transportation; rides = value)
It Correlates with Business Growth
While the north star measures user value, it must also correlate with revenue and growth. If the metric goes up and revenue does not follow, it is the wrong metric. The relationship does not need to be immediate — Slack does not charge per message — but over time, more messages means more engaged teams, which means more paid seats.
It Is Measurable & Actionable
The metric must be something you can track reliably and influence through product decisions. "Customer happiness" is too vague. "Percentage of users who complete a core workflow at least once per week" is measurable and actionable.
It Has a Leading Indicator Quality
A good north star moves before revenue does. If users start listening to less music on Spotify, revenue will eventually drop — but the listening metric drops first, giving the team time to react. This early-warning property is critical.
Lagging indicators (too late): Revenue, churn rate, NPS
Leading indicators (early): Active usage, feature adoption, engagement depth
How to Choose Your North Star
Step 1: Identify Your Product's Core Value
Ask: "What is the one thing users come to our product to do?" Strip away features and focus on the job-to-be-done.
Product type Core value Candidate metric
---------------------------------------------------------------------------
E-commerce Buy things they want Purchases completed
Social network Connect with people Meaningful interactions
Project management Complete work efficiently Tasks completed
Analytics tool Make data-driven decisions Reports generated & viewed
Learning platform Acquire new skills Lessons completed
Step 2: Test Against the Three Criteria
For each candidate, ask:
1. Does it reflect user value? If this goes up, are users getting
more of what they came for?
2. Does it correlate with growth? If this goes up sustainably,
will the business grow?
3. Can we influence it? Can product, engineering, and design
make decisions that move this number?
If a candidate fails any of these, it is not your north star.
Step 3: Validate with Data
Look at your existing data. Do users who score high on the candidate metric retain better? Convert to paid more often? Refer others? If the data shows a strong correlation between the candidate metric and retention/revenue, you have a strong north star.
Validation example:
Candidate north star: "Weekly active projects" (project management tool)
Analysis:
- Users with 3+ active projects: 92% monthly retention
- Users with 1-2 active projects: 71% monthly retention
- Users with 0 active projects: 23% monthly retention
Correlation with revenue:
- Users with 3+ active projects: 4.2x more likely to upgrade to paid
Verdict: Strong candidate. Weekly active projects correlates
with both retention and revenue.
Step 4: Get Buy-In
A north star metric only works if the whole organization adopts it. Present the metric, the reasoning, and the data to leadership. Get agreement that this is the number the company is optimizing for. If different executives are optimizing for different metrics, the north star has no power.
Input Metrics That Drive the North Star
The north star is a lagging indicator of user behavior. To move it, you need to identify and optimize the input metrics — the upstream actions that drive the north star.
North star: Nights booked (Airbnb)
Input metrics:
Supply side:
- Number of active listings
- Average listing quality score
- Host response rate
- Host response time
Demand side:
- Search-to-view rate (do users find relevant listings?)
- View-to-booking rate (do users convert after viewing?)
- First booking time (how quickly do new users book?)
- Repeat booking rate
Each input metric is owned by a team. The supply team works on listing quality and host responsiveness. The demand team works on search relevance and conversion. Everyone contributes to the north star, but each team has a specific lever to pull.
Building an Input Metric Tree
Map the relationship between the north star and its drivers:
North star: Weekly active users who complete a core action
Level 1 (direct drivers):
- New user activation rate (what % of signups become active?)
- Existing user retention rate (what % of active users stay active?)
- Resurrected user rate (what % of lapsed users come back?)
Level 2 (drivers of drivers):
New user activation:
- Signup completion rate
- Onboarding completion rate
- Time to first core action
- First-week engagement
Existing user retention:
- Feature adoption breadth
- Workflow completion rate
- Collaboration activity
- Integration usage
User resurrection:
- Win-back email open rate
- Re-engagement notification click rate
- Product improvement awareness
Each leaf in this tree is something a team can directly influence. The tree makes the connection between daily work and the north star visible.
Real-World Examples in Depth
Spotify: Time Spent Listening
Spotify chose time spent listening because it directly reflects whether users are getting value. A user who listens for two hours a day is getting enormous value from the product. The input metrics include playlist quality, recommendation relevance, content library breadth, and playback reliability. Every team can trace their work back to listening time.
Facebook: Daily Active Users (DAU)
In its growth phase, Facebook's north star was DAU. This worked because daily usage correlated with engagement, ad revenue, and network effects. The famous "7 friends in 10 days" insight was an input metric — users who added 7 friends within their first 10 days were dramatically more likely to become daily active users.
HubSpot: Weekly Active Teams
HubSpot shifted from tracking individual users to tracking teams because their value proposition is team collaboration on customer relationships. A team using HubSpot weekly is deeply embedded in their workflow and unlikely to churn. Input metrics include team invitation rate, shared workflow creation, and cross-functional usage.
When the North Star Needs to Change
North star metrics are not permanent. They should change when:
- The product strategy fundamentally shifts
(e.g., moving from consumer to enterprise)
- The metric has been maximized and no longer differentiates
(e.g., DAU at 99% of addressable market)
- You discover the metric does not actually correlate with
sustainable growth (vanity metric in disguise)
- The market changes and the old metric no longer reflects
the value users seek
Changing the north star is a big deal. It reshapes team goals, dashboards, and incentives. Do it deliberately, not casually. Announce it, explain why, and give teams time to adjust.
North Star Anti-Patterns
Vanity Metrics as North Stars
Bad north stars:
- Total registered users (includes dead accounts)
- Page views (can be inflated by clickbait)
- App downloads (most are never opened again)
- Total revenue (can grow while value shrinks)
These feel good in board decks but do not reflect
whether users are actually getting value.
Multiple North Stars
If you have three north star metrics, you have zero. The whole point is singular focus. Teams will optimize for whichever one is easiest, and the others will be ignored. If you genuinely cannot pick one, your product strategy is not clear enough.
Metrics That Teams Cannot Influence
If the north star is driven primarily by external factors (market size, seasonality, macroeconomic trends), product teams cannot move it. Choose something closer to the product experience.
Common Pitfalls
- Confusing north star with revenue — revenue is a business outcome, not a product metric. The north star should measure user value that eventually drives revenue, not revenue itself.
- Picking a metric that is too broad — "monthly active users" is so broad that it does not guide decisions. What counts as active? A login? A core action? Define it precisely.
- Picking a metric that is too narrow — "daily reports exported" might be too specific if your product delivers value in multiple ways. The north star should capture the breadth of your value proposition.
- Not connecting input metrics to the north star — the north star is useless if teams do not know which levers move it. Build the input metric tree and make it visible.
- Gaming the metric — if the north star is "messages sent" and you add auto-generated messages, the number goes up but user value does not. Guard against optimizations that inflate the metric without improving the experience.
- Setting the north star and forgetting it — track it weekly. Review it in leadership meetings. Reference it in planning. If it only appears in a quarterly deck, it is not functioning as a north star.
Key Takeaways
- A north star metric is the single number that captures the core value your product delivers to users. It drives focus, alignment, and clarity across the organization.
- The metric must reflect user value, correlate with business growth, and be something the team can influence through product decisions.
- Input metrics are the levers that drive the north star. Map the tree from north star to input metrics, and assign each input metric to a team.
- Revenue is not a north star. It is an outcome of delivering value. Measure the value, and revenue follows.
- The north star should be referenced constantly — in planning, in reviews, in daily decisions. If it does not shape behavior, it is just a number on a dashboard.