The Metric That Defines Your Product Strategy
By Dennis Chow · 7 min read
I've watched product teams argue for weeks about roadmap priorities while their CEO quietly wonders if the PM org understands the business at all. The problem usually isn't the roadmap. It's that the team is optimizing for seven different things, none of which the exec team cares about.
A north star metric fixes this. Not by making everyone agree, but by making disagreement productive. When you pick the right one, every roadmap debate becomes simpler: does this move the metric or not?
What Is a North Star Metric and Why It Matters
Your north star metric is the single product metric that best captures the core value your product delivers to customers. It's not revenue. It's not Monthly Active Users. It's the thing that, if it goes up consistently, means customers are getting real value — and revenue follows.
Spotify's north star is "time spent listening." Not signups, not app opens. Listening time. When that number grows, everything else — retention, premium conversions, artist satisfaction — tends to follow.
The reason this matters isn't philosophical. It's practical. Product teams at scale face hundreds of competing priorities. Sales wants enterprise features. Support wants bug fixes. Marketing wants viral mechanics. Your CEO wants "growth" but won't tell you what kind.
A north star metric doesn't eliminate these tensions. It gives you a tiebreaker. When a feature request doesn't clearly move the metric, you have language to explain why it's not the priority. When two equally expensive projects compete for engineering time, the metric tells you which one matters more.
How the Right Metric Aligns Your Entire Product Team
Here's what changes when a product org actually commits to a north star:
Design reviews get faster. Instead of debating aesthetics, you're asking whether the proposed experience increases the likelihood that users complete the core value action. The metric becomes the design brief.
Engineering understands priority. Your backend team stops treating all requests as equally urgent because they know which systems directly support the metric and which are two degrees removed.
The executive team stops asking for random features. Not because they care about your metric framework, but because you're speaking their language now. "This feature won't move weekly active creators" is more convincing than "this wasn't on the roadmap."
I worked with a B2B SaaS team whose north star was "teams using the product together three times per week." That framing transformed how they thought about onboarding. The old goal was "get users to complete setup." The new goal was "get the second and third team member active within 72 hours." Completely different product strategy, same company.
The Framework: Choosing Your Product's North Star Metric
Most product teams pick a vanity metric and call it north star. Daily Active Users sounds good until you realize half your DAUs are checking something once and bouncing. Total revenue feels strategic until you realize you're growing top-line while customer satisfaction craters.
A real north star metric passes three tests:
It captures delivered value, not promised value. Signups don't count. Completed onboarding barely counts. You want the moment when the customer actually got what they came for. For Airbnb, it's "nights booked" — not searches, not wishlists, not profile completions.
It predicts retention and revenue. Your north star should be a leading indicator. If it goes up this month, revenue should follow in the next 2-3 months. If the correlation is weak, you picked the wrong metric.
The product team can directly influence it. If your north star requires the sales team to close bigger deals or marketing to change their messaging, it's not a product north star. Your team needs to be able to move this metric through product decisions alone.
The formula I use: "Number of [active user segment] who [complete core value action] per [time period]."
For Slack, it's something like "teams who exchange 2,000+ messages per month." For Amazon, it's closer to "customers who complete 3+ purchases per quarter." The specifics matter less than the structure.
Common North Star Metrics by Product Type (with Examples)
Marketplaces: Transaction volume or gross merchandise value. Etsy optimizes for "active sellers making sales monthly" because supply-side health predicts long-term marketplace dynamics.
Social/UGC platforms: Content creation by engaged users. YouTube's metric is closer to "hours uploaded by creators with 100+ subscribers" than total video uploads. Quality supply matters more than volume.
SaaS tools: Weekly active teams or collaboration events. Figma's north star is probably "files with 3+ editors per week" — capturing both adoption and the collaboration value that makes them sticky.
Subscription content: Consumption frequency among paying users. The New York Times likely tracks "paid subscribers who read 4+ articles per week" because that behavior pattern predicts long-term retention.
Fintech/transactional: Transaction frequency among verified users. PayPal's north star might be "active users making 3+ transactions per month" — proving the product has become a habit.
Notice the pattern. It's never just volume. It's always volume of a quality behavior, from a qualified user segment, happening with meaningful frequency.
When Your North Star Metric Should Change
Your north star metric shouldn't change quarterly. But it should change as your product matures.
Early-stage products often focus on activation: "users who complete their first [core action] within 7 days." You're proving the value proposition works. Once activation is reliably above 40-50%, shift to a retention-focused metric: "users who complete [core action] weekly for a month."
When Dropbox was young, their north star was probably "users who save their first file." As they scaled, it became "users storing 1GB+ of files" and later "teams with 3+ members actively sharing folders." Same product category, different maturity stage.
The trigger for changing your north star: when optimizing for the current metric stops predicting business outcomes. If you're hitting your metric targets but churn is climbing, the metric is lying to you.
I've seen two common failure modes. The first is changing the metric because you're not hitting it. Don't. If the metric is right and you're not moving it, that's information — your product strategy isn't working. The second is adding multiple north stars. Also don't. The entire point is singular focus.
Tracking and Communicating Your North Star Effectively
The metric is worthless if nobody looks at it. I've reviewed dozens of product strategies where the "north star" appears on slide 12 of a deck the team presents once a quarter. That's not a north star. That's a KPI you mention to sound strategic.
Real north star tracking means the metric is visible everywhere. Literally. It's in your weekly team sync. It's on a dashboard the design team checks daily. Your CEO knows the number without having to ask.
When you present roadmap priorities, you show how each initiative is expected to impact the metric. Not might impact. Not could impact. Expected impact, with a hypothesis you can test. "We believe adding collaborative editing will increase weekly active teams by 15% because 60% of our activated users report wanting to work together in real-time."
The communication format that works: current metric value, trend over the last 8 weeks, and one sentence about what moved it. That's the update. Keep it short. Make it regular. Stop making people dig through dashboard hell to understand if the product is working.
Your product strategy should connect directly to the metric. When stakeholders understand that relationship — when they see your team consistently moving the number that predicts business outcomes — you stop getting random feature requests. Not because stakeholders changed, but because you gave them a better way to understand what the product team actually does.