Identifying Your Product's North Star Metric
This skill teaches you how to discover and define the single metric that best captures the core value your product delivers to customers, forming the foundation of the North Star Framework.
To identify your North Star Metric, start by articulating the core value your product delivers to customers—the moment they experience real benefit. Then find the metric that best quantifies how many customers are receiving that value, how frequently, and how deeply. A strong North Star Metric correlates with both customer satisfaction and long-term revenue growth, making it the single measure your entire product team can rally around.
Outcome: You produce a clearly defined, validated North Star Metric that the entire product organization can use to align decisions, prioritize work, and measure whether your product is delivering increasing value to customers over time.
Prerequisites
- Basic understanding of product analytics and how your product is instrumented
- Familiarity with your product's business model and revenue drivers
- Access to user behavior data or analytics tools (e.g., Amplitude, Mixpanel, or even spreadsheets)
- Understanding of what is a product manager's role in defining strategy and success metrics
Overview
Every product team faces a common challenge: dozens of metrics are moving in different directions, stakeholders disagree on what matters most, and teams optimize for local metrics that don't compound into real business outcomes. Identifying your North Star Metric solves this by forcing you to answer a deceptively hard question: what single measurement best represents the value customers get from your product? This is the foundational skill within the North Star Framework, and everything else—mapping input metrics, aligning teams, building dashboards—depends on getting this right.
The North Star Metric (NSM) is not a vanity metric like page views, nor is it a pure business metric like revenue. It sits at the intersection of customer value and business value. For Spotify, it's time spent listening. For Airbnb, it's nights booked. For Slack, it's messages sent within organizations. Each of these metrics captures the core exchange of value: when the number goes up, customers are getting more value, and the business grows sustainably. Understanding what is a product manager's core responsibility helps clarify why this skill matters—product managers are uniquely positioned to bridge customer needs with business outcomes, and the North Star Metric is the instrument that makes that bridge measurable.
This skill matters because choosing the wrong metric can be worse than having no metric at all. A poorly chosen NSM can misalign incentives, encourage short-term gaming, or focus teams on activity rather than outcomes. The process of identification is as valuable as the result—it forces deep thinking about your product's value proposition, your customers' jobs-to-be-done, and the relationship between customer success and business growth.
How It Works
The core mental model behind identifying a North Star Metric is the value exchange loop: your product delivers value to customers, customers signal that value through their behavior, and that behavior drives sustainable business growth. Your NSM should sit at the heart of this loop—it should go up when customers get more value and, as a consequence, when your business becomes healthier.
Think of it as a funnel with three filters. First, the metric must reflect customer value received, not just customer activity. There's a critical difference between 'users who logged in' (activity) and 'users who completed a project' (value received). Second, the metric must be leading, not lagging—it should predict future revenue and retention, not just report on the past. Third, the metric must be influenceable by the product team. If your team can't move it through product decisions, it's not a useful North Star.
The reason this is an intermediate skill rather than a beginner one is that it requires judgment, not just analysis. You'll find that multiple candidate metrics seem reasonable, and the data alone won't tell you which is right. You need to combine quantitative analysis (which metrics correlate with retention and revenue?) with qualitative understanding (what moment represents real value for your customer?). The best North Star Metrics often feel obvious in hindsight but require significant exploration to surface. They emerge from a deep understanding of your product's value proposition—the kind of understanding that what is a product manager fundamentally responsible for cultivating through continuous customer discovery and strategic thinking.
One important nuance: a North Star Metric is not permanent. Products evolve, markets shift, and your understanding deepens. But you need to commit to one for long enough to align your team and learn from it—typically 6-12 months minimum. The iterating and evolving your North Star Metric skill covers when and how to revisit it.
Step-by-Step
Step 1: Articulate Your Product's Core Value Proposition
Before looking at any data, write down in one or two sentences what value your product delivers to customers. Focus on the outcome they achieve, not the features you provide. For a project management tool, the value isn't 'task lists and Gantt charts'—it's 'teams ship projects on time with less coordination overhead.' Interview 5-10 customers and ask them to describe the moment they first felt your product was worth paying for. Look for patterns in their language.
Tip: Use the 'jobs-to-be-done' framing: 'When [situation], customers hire our product to [outcome], so they can [benefit].' This structure forces you past feature-level thinking.
Step 2: Identify the 'Value Moment' in Your Product
Map the customer journey and pinpoint the specific action or event that represents value being received. This isn't the signup or first login—it's the moment the customer's problem is actually being solved. For a collaboration tool, it might be 'a team member responds to a shared document.' For an e-commerce platform, it might be 'a buyer receives their order and doesn't return it.' List 3-5 candidate value moments, then rank them by how directly they represent the core value you articulated in Step 1.
Tip: If you're unsure, look at what churned users did NOT do. The actions that separate retained users from churned users often point directly to your value moment.
Step 3: Generate Candidate North Star Metrics
For each value moment, brainstorm metrics that quantify it. A good NSM typically combines three dimensions: breadth (how many customers), depth (how much value per customer), and frequency (how often). For Spotify, 'total hours listened per week' combines all three. For each candidate, write it out as a specific, measurable statement: 'Weekly active teams that complete at least one project milestone.' Aim for 3-6 strong candidates. Don't filter too aggressively at this stage—you want options to compare.
Tip: Test each candidate against this template: 'If [metric] goes up, we are confident that customers are getting more value AND the business will grow.' If either clause fails, refine the metric.
Step 4: Validate Candidates Against Historical Data
Pull your analytics data and test each candidate metric's correlation with two outcomes: customer retention (do customers who score high on this metric stick around?) and revenue growth (does this metric's movement predict future revenue?). You don't need sophisticated statistical analysis—even plotting the metric against 90-day retention in a spreadsheet will reveal patterns. If a candidate metric has no meaningful correlation with retention or revenue, it's measuring activity, not value. Eliminate those candidates.
Tip: Look at cohort data, not just aggregate numbers. A metric might look good in aggregate but fail for specific customer segments. Your NSM should work across your most important segments.
Step 5: Apply the Six Criteria Test
Score each remaining candidate against six criteria: (1) It expresses value—when it moves, customers are getting more value. (2) It represents vision—it points toward where your product is heading. (3) It's a leading indicator—it predicts future success, not just reports on the past. (4) It's actionable—your product team can influence it directly. (5) It's understandable—you can explain it to any team member in one sentence. (6) It's measurable—you can track it reliably with your current instrumentation. Score each criterion 1-5 and compare totals. The highest-scoring candidate is your frontrunner.
Tip: The 'understandable' criterion is more important than it seems. If people can't remember the metric or explain it to a new hire, it won't drive alignment—which defeats the entire purpose of having a North Star.
Step 6: Stress-Test with Thought Experiments
Take your top candidate and deliberately try to break it. Ask: 'Could we game this metric in a way that hurts customers?' (If yes, refine it.) 'Would this metric still be relevant if we doubled our user base?' (If no, it may be a growth-stage metric, not a true North Star.) 'If this metric plateaued, would we be worried even if revenue kept growing?' (If no, it might not be fundamental enough.) Run these scenarios with your team—different perspectives will surface blind spots you missed alone.
Tip: The most common failure mode is choosing a metric that can be inflated through low-quality activity. If your metric is 'messages sent,' teams might optimize for notification spam. Consider adding a quality qualifier, like 'messages sent that receive a reply within 24 hours.'
Step 7: Define the Metric Precisely
Once you've selected your NSM, write a precise definition document. Include: the exact formula for calculating it, the data sources used, how frequently it's measured (daily, weekly, monthly), any segments or filters applied, and boundary conditions (e.g., 'we count a project as completed only if at least two team members contributed'). This definition prevents future debates about whether the metric went up or down. Circulate it to engineering, data, and product teams for feedback on feasibility.
Tip: Include specific examples of what counts and what doesn't count. 'A weekly active project is one where at least one task was completed or one comment was added by a human user (automated actions excluded).' Edge cases will arise—define them upfront.
Step 8: Validate with Stakeholders and Commit
Present your recommended NSM to key stakeholders—executive team, product leads, engineering leaders—along with the evidence from your analysis. Explain why alternatives were rejected. The goal is not unanimous enthusiasm; it's informed commitment. Leadership needs to understand that the NSM is a strategic choice, not a perfect truth. Agree on a review period (typically 6-12 months) where the team commits to this metric before revisiting. This step connects directly to the aligning teams around a North Star Metric skill.
Tip: Anticipate the 'but what about revenue?' objection. Show the correlation between your NSM and revenue. Make it clear: you're not ignoring revenue, you're identifying the leading indicator that drives it.
Examples
Example: B2B Project Management SaaS
A 50-person SaaS company builds project management software for mid-market teams. They've been tracking MAU, NPS, and MRR, but teams are pulling in different directions—marketing optimizes for signups, product optimizes for feature adoption, and customer success optimizes for NPS. The CEO asks the product team to implement the North Star Framework to create alignment. The product manager needs to figure out what is a product manager's most important contribution here: identifying the metric that unites all these efforts.
The PM interviews 12 customers and discovers the consistent 'aha moment' is when a team completes their first project on time using the tool. She generates five candidate metrics: MAU, weekly active projects, projects completed, teams with 3+ active members, and weekly projects completed on time by teams with 3+ members. She pulls 12 months of cohort data and finds that 'teams that complete at least one project per month' has a 0.78 correlation with 12-month retention and a 0.65 correlation with expansion revenue. She applies the six criteria test: it expresses value (projects completed = work delivered), represents vision (more teams succeeding), is leading (predicts retention 3 months out), is actionable (product improvements in templates, collaboration, and reminders can all move it), is understandable ('monthly active teams completing projects'), and is measurable (they already track project status). The final NSM becomes: 'Number of teams that complete at least one project per month.' She presents it with the data and gets leadership buy-in for a 9-month commitment.
Example: Consumer Fitness App
A consumer fitness app has 2 million downloads but struggles with retention—only 15% of users are active after 30 days. The product team suspects they're measuring the wrong things. Currently they track daily active users (DAU) and workouts started, but these metrics haven't helped them improve retention. The head of product asks a senior PM to identify a proper North Star Metric.
The PM starts by analyzing the behavioral difference between users who retain past 30 days and those who don't. The data reveals that users who complete 3+ workouts per week in their first two weeks have a 72% chance of being active at 90 days, versus 11% for users who complete fewer. He generates candidates: workouts started, workouts completed, weekly active users completing 3+ workouts, and total workout minutes. He eliminates 'workouts started' because users often start and quit mid-workout (activity without value). 'Total workout minutes' fails the gaming test—the team could just make workouts longer. 'Weekly active users completing 3+ workouts' scores highest across all criteria, but after stress-testing, the team adds a quality qualifier: workouts of at least 15 minutes that reach the cool-down phase. The final NSM is: 'Weekly users completing 3+ full workouts (15+ minutes reaching cool-down).' This metric immediately reframes product priorities—instead of adding more workout types, the team focuses on reducing mid-workout dropout and building habit-formation features like scheduling and streak tracking.
Example: Two-Sided Marketplace for Freelancers
A freelance marketplace connects designers with small businesses. They have 20,000 freelancers and 8,000 clients on the platform. The company has been measuring GMV (gross merchandise value) as their primary metric, but the product team feels this overweights a small number of high-value contracts and doesn't capture the health of the marketplace for the average user.
The PM maps both sides of the marketplace. For clients, the value moment is receiving deliverables they're satisfied with. For freelancers, it's getting paid for work that matches their skills. She realizes the metric must capture both sides. Candidates include: monthly transactions completed, projects with 4+ star ratings, freelancers earning $500+/month, and repeat client engagements. She tests correlations and finds that 'projects completed with both parties rating 4+ stars' is the strongest predictor of both freelancer retention (they stay on the platform) and client repeat purchase behavior. The stress test reveals a risk: teams might optimize for easy, low-value projects that are easy to rate well. She refines to 'monthly projects completed with mutual 4+ star ratings and minimum $200 project value.' This captures quality, satisfaction, and meaningful economic exchange. The metric is 3,400 currently, and she works with the data team to build a daily tracking dashboard—which feeds directly into the building North Star Metric dashboards skill.
Best Practices
Choose a metric that a customer would recognize as valuable—if you told a customer 'we're trying to increase X,' they should nod and say 'yes, that would make the product better for me.' This customer-resonance test eliminates most vanity metrics immediately.
Prefer rate or ratio metrics over raw counts for your NSM when possible. 'Weekly active teams completing milestones' is better than 'total milestones completed' because it's harder to game and more reflective of broad-based value delivery rather than power-user activity.
Score your candidate metrics independently before discussing them as a group to avoid anchoring bias. Have each team member rank the candidates privately, then reveal and discuss the differences—disagreements often surface the most important insights.
Document the 'why not' for rejected candidates as carefully as the 'why' for your chosen NSM. When someone proposes switching to a different metric six months later (and they will), you'll have your reasoning ready.
Your North Star Metric should be stable enough to measure over quarters but sensitive enough to respond to product changes within weeks. If it takes six months to move, your team will lose faith. If it fluctuates wildly day-to-day, you'll over-react to noise.
Explicitly separate your North Star Metric from your company-level financial KPIs. Your NSM feeds into revenue, but it is not revenue. This distinction is what makes the North Star Framework powerful—it keeps your team focused on the value creation that drives financial outcomes rather than optimizing for short-term extraction.
Common Mistakes
Choosing revenue or a revenue-adjacent metric as your North Star Metric
Correction
Revenue is a trailing indicator—it tells you what already happened, not whether you're creating the value that will sustain growth. Teams that use revenue as their NSM tend to optimize for short-term monetization tactics (more aggressive upsells, paywalls) at the expense of long-term customer value. Instead, find the metric that predicts revenue. If your NSM goes up and revenue eventually follows, you've found the right leading indicator.
Picking a metric the product team cannot influence through product decisions
Correction
This typically happens when teams choose metrics driven primarily by marketing spend or sales activity, like 'new signups' or 'total registered users.' If your product team ships a great feature and the NSM doesn't move, the metric isn't reflecting product value. Your NSM should be something a product engineer can connect to their sprint work. Test this by asking: 'If we improve onboarding, would this metric go up?' If the answer is unclear, your metric is too far from the product experience.
Selecting a composite index or overly complex formula as the NSM
Correction
Some teams create weighted indices combining multiple metrics into a single score. While intellectually appealing, these metrics fail the understandability test. When you say 'our Health Score is 73,' nobody in the room intuitively knows whether that's good, bad, or what caused it to change. The cognitive overhead kills adoption. Your NSM should be explainable in one sentence to a new team member on their first day. If it requires a footnote or a spreadsheet to understand, simplify it.
Treating the NSM identification process as a one-person exercise
Correction
When a single product manager identifies the NSM in isolation, even if the analysis is excellent, the rest of the organization feels no ownership over it. The NSM becomes 'that metric the PM chose' rather than 'our North Star.' The identification process should involve input from at least 3-5 people across product, engineering, data, and customer-facing teams. Different perspectives catch blind spots: engineers know what's measurable, customer success knows what drives satisfaction, and data teams know what the numbers actually show.
Changing the North Star Metric too frequently based on short-term results
Correction
When the NSM doesn't show immediate improvement after a product change, some teams panic and switch metrics. But value creation is often non-linear—you might need to ship three improvements before the metric meaningfully moves. Commit to your NSM for at least 6 months. If after that period, with genuine effort, the metric doesn't correlate with customer outcomes, revisit it using the iterating and evolving your North Star Metric process. Premature switching destroys the alignment benefits the framework is designed to create.
Other Skills in This Method
Mapping Input Metrics That Drive Your North Star
How to identify, define, and connect the 3-5 key input metrics that directly influence your North Star Metric.
Building Dashboards to Track Your North Star and Inputs
How to set up real-time dashboards and reporting structures that visualize your North Star Metric and its supporting input metrics.
Running a North Star Framework Workshop with Stakeholders
A step-by-step guide to facilitating a collaborative workshop where teams define or refine their North Star Metric and input metrics.
Using the North Star Metric to Prioritize Your Product Roadmap
How to evaluate and rank roadmap initiatives based on their expected impact on the North Star Metric and its input metrics.
Iterating and Evolving Your North Star Metric Over Time
When and how to revisit, validate, or change your North Star Metric as your product matures and strategy shifts.
Aligning Cross-Functional Teams Around a North Star Metric
Techniques for communicating, cascading, and embedding the North Star Metric across product, engineering, marketing, and leadership teams.
Related Skills from Other Methods
Frequently Asked Questions
How is a North Star Metric different from a KPI or OKR?
KPIs are any key performance indicators—you might have dozens across the company. OKRs are time-bound objectives with measurable key results, typically set quarterly. Your North Star Metric is a single, enduring metric that represents the core value your product delivers. It sits above KPIs and OKRs in the hierarchy: your OKRs might define quarterly targets for improving the NSM, and your KPIs are the input metrics that drive it. Think of it this way: OKRs change every quarter, KPIs vary by team, but your North Star Metric stays constant for 6-12+ months and applies to the entire product organization.
Can a company have more than one North Star Metric?
The short answer is no—the entire value of the framework comes from forcing alignment around a single metric. If you have two, you effectively have zero because teams will optimize for whichever is more convenient. The exception is companies with genuinely distinct product lines serving different customers (e.g., a company running both a consumer app and a B2B API). Each product can have its own NSM, but each product team should have exactly one. If you're struggling to choose between two candidates, it usually means one is actually an input metric that drives the other—use the [mapping input metrics](/skills/mapping-input-metrics-to-north-star) skill to determine the hierarchy.
What is a product manager's role in identifying the North Star Metric versus leadership's role?
The product manager typically drives the identification process—conducting customer research, analyzing data, generating candidates, and making a recommendation. Leadership's role is to provide strategic context (where is the company headed in 2-3 years?), validate that the proposed NSM aligns with the business model, and commit to the metric organizationally. Think of it as: the PM does the analytical work and proposes, leadership challenges and ratifies. The worst pattern is when a CEO announces the NSM top-down without the analytical process—it rarely reflects genuine customer value and teams won't feel ownership.
How do I identify a North Star Metric when my product is pre-product-market fit?
Before product-market fit, your understanding of customer value is still forming, so your NSM will be more of a hypothesis than a validated metric. That's okay—pick the best candidate you can based on early customer interviews and usage data, and expect to revise it. Focus on the value moment: what action indicates a user got real value? Even with 50 users, you can often identify the behavioral difference between users who come back and those who don't. Use that as your starting NSM, commit for 3-4 months instead of the usual 6-12, and iterate. Having an imperfect NSM is still better than having no alignment metric at all.
What if our North Star Metric conflicts with short-term revenue goals?
This tension is common and actually healthy—it surfaces strategic misalignment that was always there but hidden. If your NSM is 'weekly active teams completing projects' but leadership wants to maximize this quarter's upsell revenue, the conflict isn't between metrics, it's between short-term extraction and long-term value creation. Present the correlation data showing your NSM predicts future revenue. Then negotiate: perhaps the team allocates 80% of effort to NSM-driving work and 20% to immediate revenue needs. If leadership consistently overrides the NSM for short-term revenue, the framework won't work—and that's valuable information about whether the organization is truly ready for it.
How do I know if I've chosen the wrong North Star Metric?
Three warning signs: (1) The metric is going up but customer satisfaction or retention is flat or declining—this means your metric doesn't actually capture value. (2) Teams are gaming it in ways that don't help customers—for example, inflating 'active users' through aggressive notification spam. (3) After 3-6 months, product teams can't articulate how their current work connects to the NSM—this means it's too abstract or disconnected from daily product decisions. If you see any of these, don't panic-switch. Instead, revisit the process described here and use the [iterating and evolving your North Star Metric](/skills/iterating-and-evolving-north-star-metric) skill to systematically reassess.