North Star Framework: How Every Product Manager Aligns Teams Around One Metric
The North Star Framework is a product management model where teams align around a single North Star Metric (NSM) that captures the core value customers receive from a product. A product manager identifies this metric, maps the input metrics that influence it, and uses both to guide prioritization, roadmap decisions, and cross-functional alignment. Developed by Sean Ellis, the framework prevents teams from optimizing vanity metrics and instead focuses effort on sustainable, value-driven growth.
Overview
The North Star Framework was developed by Sean Ellis, the growth marketer who coined the term "growth hacking" and led early growth at Dropbox and LogMeIn. Ellis observed that the highest-performing product teams shared a common trait: they rallied around a single metric that captured the moment customers received genuine value. He formalized this observation into the North Star Framework, first popularizing it through GrowthHackers.com and later co-authoring the definitive guide with the Amplitude product analytics team. The framework emerged from a practical frustration—teams were drowning in dashboards full of metrics that pulled people in conflicting directions, and leadership needed a shared language for what "winning" actually meant.
The problem the North Star Framework solves is deceptively simple but devastatingly common: misalignment. Engineering optimizes for shipping velocity. Marketing optimizes for signups. Sales optimizes for closed deals. Finance optimizes for revenue. Without a unifying metric, each function can hit its targets while the product stagnates or even declines. The North Star Metric acts as a single source of truth—a leading indicator that, when it grows, reliably predicts long-term business success because it measures real customer value delivered. For Airbnb, that metric is nights booked. For Spotify, it's time spent listening. For Slack, it's messages sent within organizations. Each metric captures the atomic unit of value the product delivers.
The framework is more than just picking a metric, though. A product manager using the North Star Framework also identifies 3–5 input metrics—the levers the team can directly influence to move the North Star. These inputs create a causal model of the business. If your North Star is weekly active subscribers, your inputs might be new signups, activation rate, content engagement depth, and churn rate. The product manager's job becomes orchestrating work across these inputs, making trade-off decisions visible, and ensuring every team understands how their work connects to the metric that matters most.
The North Star Framework has become a staple in product management because it scales across company sizes—from a five-person startup trying to find product-market fit to a thousand-person enterprise trying to prevent organizational drift. It's especially powerful for any product manager navigating the tension between short-term revenue pressure and long-term product health, because a well-chosen North Star Metric inherently balances customer value with business outcomes.
How It Works
Step 1: Articulate Your Product's Core Value Proposition
Before choosing any metric, the product manager must clearly articulate what value customers receive from the product. This is not your tagline or marketing positioning—it's the fundamental reason customers keep coming back. Interview 10–15 of your most engaged users and ask them what they would miss most if your product disappeared. Look for patterns in their answers. The most common mistake at this step is confusing what your product does (features) with what value it delivers (outcomes). A project management tool's features include task creation and Gantt charts, but the value it delivers is 'projects completed on time.' Get to the outcome, not the mechanism.
Step 2: Identify Your North Star Metric Candidates
Generate 3–5 candidate metrics that could serve as your North Star by asking: which metric, when it increases, most reliably indicates that more customers are getting more value from our product? Common archetypes include attention metrics (time spent), transaction metrics (actions completed), and productivity metrics (tasks accomplished). Test each candidate against four criteria: Does it measure customer value delivered? Can we measure it reliably? Can our team influence it? Does growth in this metric lead to growth in revenue over time? A strong candidate passes all four. Be wary of vanity metrics like total registered users or page views—they can grow while the product deteriorates.
Step 3: Select and Validate Your North Star Metric
Narrow your candidates to one metric through a combination of data analysis and stakeholder alignment. Run a historical correlation analysis: does past growth in this metric correlate with subsequent revenue growth, retention improvement, and customer satisfaction? Present the top 2–3 candidates to your leadership team with the data, and drive consensus on one. The validation step is critical—if you skip it, you risk choosing a metric that leadership doesn't believe in, which will undermine the entire framework. Document the rationale for your choice so new team members understand why this metric was selected over alternatives.
Step 4: Map the Input Metrics That Drive Your North Star
Decompose your North Star Metric into 3–5 input metrics that represent the controllable levers your team can pull. Think of this as building a simple equation: NSM = f(Input 1, Input 2, Input 3, ...). For example, if your NSM is 'weekly active subscribers watching content,' your inputs might be new subscriber activations, content catalog freshness, recommendation accuracy, and stream completion rate. Each input should be ownable by a specific team or squad. The most common failure here is choosing too many inputs (which dilutes focus) or choosing inputs that are correlated with each other rather than independently contributing to the NSM.
Step 5: Assign Input Ownership and Set Targets
Assign each input metric to a specific team or individual who has the authority and capability to move it. The product manager coordinates this assignment, ensuring there are no gaps and no overlaps. For each input, set a current baseline, a 90-day target, and a stretch goal. Be explicit about the expected relationship: 'If we improve activation rate from 32% to 40%, we expect our NSM to increase by approximately X based on our model.' This makes the framework testable—if you improve the input and the NSM doesn't move, either your input mapping is wrong or there's an external factor you haven't accounted for.
Step 6: Build Dashboards and Reporting Cadences
Create a shared dashboard that displays the North Star Metric and all input metrics with trend lines, targets, and current values. This dashboard should be visible to the entire company, not just the product team. Establish a weekly review cadence where the product manager walks through each input's progress, highlights anomalies, and surfaces trade-off decisions. The dashboard is not a vanity display—it's the operating system for your prioritization conversations. If a team proposes a new initiative, the first question should be 'which input does this move, and by how much?'
Step 7: Use the Framework for Prioritization and Trade-offs
With your NSM and inputs established, every product decision should be evaluated through this lens. When comparing two feature proposals, estimate their expected impact on the relevant input metrics and, by extension, the North Star. This doesn't mean you only work on things that directly move an input—some work is infrastructure, some is debt reduction, some is compliance. But the framework makes the cost of non-NSM work visible: 'We're choosing to invest in this compliance project, which means we're accepting slower growth in Input 2 this quarter.' Transparency about trade-offs is the framework's greatest practical benefit.
Step 8: Review, Learn, and Iterate
Conduct a quarterly North Star review where the product manager presents: Did the NSM move as expected? Did the inputs move? Where did our causal model break down? Are there new inputs we should add or existing ones we should retire? This review is also the appropriate time to ask whether the North Star Metric itself still captures your product's core value, especially if you've launched new product lines, entered new markets, or observed shifts in customer behavior. Treat the framework as a living system, not a set-it-and-forget-it exercise.
When to Use
- When your product team has grown past 10 people and different functions are optimizing for conflicting metrics—engineering ships features, marketing drives signups, and no one agrees on whether the product is actually getting better for customers.
- When your company has achieved initial product-market fit and you need to shift from chaotic experimentation to disciplined, scalable growth. The North Star Framework provides the operational structure to focus experimentation on what matters without killing the growth mindset.
- When your product manager is struggling to prioritize a backlog of 30+ feature requests because there's no shared language for evaluating impact. The NSM and its input metrics give you a quantitative basis for saying 'this initiative moves our North Star more than that one.'
- When leadership keeps asking 'are we winning?' and every team gives a different answer based on their own dashboards. A single North Star Metric with transparent input metrics creates one shared answer and one shared reality.
- When you're preparing for a board meeting or annual planning cycle and need a concise way to communicate product strategy and progress. The North Star and its inputs compress your product narrative into a model that non-product stakeholders can understand and hold you accountable to.
When Not to Use
- When you're a pre-product-market-fit startup still searching for what value you actually deliver. Choosing a North Star Metric before you understand your core value proposition will lock you into optimizing for the wrong thing. Focus on discovery and qualitative learning first, and adopt the framework once you have confidence in your value hypothesis.
- When your product serves fundamentally different user segments with incompatible definitions of value—for example, a marketplace where buyer value and seller value are measured in completely different units. In these cases, a single NSM can obscure important segment-level dynamics. Consider separate North Stars per segment or a composite metric approach.
- When your organization's leadership is not willing to commit to a single metric and will continue demanding that every team hit their own siloed KPIs regardless. Without executive buy-in, the North Star becomes another metric on the dashboard rather than the unifying force it's designed to be—and the product manager ends up fighting political battles instead of building products.
- When your product is in sunset or maintenance mode with no active investment in growth. The framework is designed to focus growth efforts; if there's no growth investment, it adds process overhead without corresponding benefit.
- When your team lacks the analytics infrastructure to reliably measure the North Star and its inputs at least weekly. Adopting the framework without trustworthy data leads to debates about measurement accuracy rather than strategic decisions, and can erode team trust in data-driven approaches entirely.
Examples
Example: B2B Project Management SaaS Adopts the North Star Framework
A 50-person B2B SaaS company building project management software was struggling with cross-team alignment. Engineering measured sprint velocity, marketing tracked MQLs, and sales focused on closed-won revenue—but customer churn was creeping up to 8% monthly. The product manager facilitated a North Star workshop and the team selected 'weekly active teams completing projects' as their NSM, with four inputs: new team activation rate, template adoption rate, weekly collaboration events per team, and project completion rate. Within two quarters, the product team shifted 40% of their roadmap from new feature development to improving the activation and collaboration inputs. Template adoption rose from 23% to 51%, project completion rate increased by 18%, and monthly churn dropped to 4.2%—because the framework redirected the entire organization's attention from vanity growth metrics to the moments where customers actually received value.
Example: Consumer Fitness App Selects 'Weekly Workouts Completed' as NSM
A consumer fitness app with 2 million registered users but declining engagement hired a new product manager who implemented the North Star Framework. After analyzing user behavior data and conducting 20 user interviews, the team chose 'weekly workouts completed' as their NSM over alternatives like DAU and session length. The input metrics were: new user first-workout rate (activation), workout plan personalization score, social challenge participation rate, and streak maintenance rate. The critical insight came from mapping inputs: the team discovered that social challenge participation had a 3.2x multiplier effect on streak maintenance, which was the strongest driver of weekly workouts. They shifted their Q3 roadmap to double down on social features, resulting in a 34% increase in weekly workouts completed and a 22% improvement in 90-day retention—metrics the team would never have prioritized if they were still optimizing for raw DAU.
Example: E-Commerce Marketplace Resolves Buyer-Seller Tension
A two-sided marketplace for handmade goods faced a classic tension: the buyer team wanted to optimize for 'items purchased' while the seller team optimized for 'items listed.' Neither metric captured the full picture, and the teams frequently clashed over homepage real estate and search algorithm priorities. The senior product manager proposed 'weekly transactions where buyers leave positive reviews' as the North Star Metric, arguing it only grows when both sides of the marketplace are healthy—sellers deliver quality goods and buyers find what they want. Inputs included new seller 30-day activation rate, search relevance score, average delivery time, and buyer return visit rate. The shared metric transformed prioritization conversations: a proposal to increase listing volume was evaluated not by raw listing count but by its expected impact on positively-reviewed transactions. Over six months, the NSM grew 27% while average seller rating improved from 4.1 to 4.4 stars, demonstrating that marketplace quality and growth weren't in conflict when measured correctly.
Skills in This Method
Identifying Your Product's North Star Metric
How to discover and define the single metric that best captures the core value your product delivers to customers.
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.