Definition
The North Star Framework is a strategic alignment tool in which a team identifies a single "North Star Metric" (NSM) that captures the core value the product delivers to customers, supported by 3-5 input metrics that teams can directly influence. The NSM serves as a shared focus for the entire organization: every team's work should ultimately contribute to moving this metric.
The concept builds on Sean Ellis's growth thinking and was formalized by Amplitude in their North Star Playbook. The key insight is that a well-chosen North Star Metric is a leading indicator of long-term business success. If the metric goes up sustainably, revenue follows. If it stagnates, no amount of sales effort can compensate.
The Product Analytics Handbook covers how to define and track a North Star Metric alongside supporting input metrics. The metrics guide provides practical guidance on choosing the right metric. The North Star Finder is an interactive tool that helps teams identify their NSM through a guided assessment.
Why It Matters for Product Managers
The North Star Framework solves the most common alignment failure in product organizations: different teams optimizing for different metrics that may conflict. When marketing optimizes for signups, product optimizes for engagement, and sales optimizes for deal size, the organization pulls in three directions. A shared North Star Metric creates a single point of alignment.
For PMs, the North Star matters in three ways. First, it clarifies prioritization. When deciding between two features, the PM can ask "which one moves the North Star Metric more?" This cuts through opinion-based debates and gives teams a shared decision-making criterion. The RICE Calculator can factor NSM impact into scoring.
Second, the North Star connects product work to business outcomes. Revenue is a lagging indicator that takes quarters to respond to product changes. The North Star Metric is a leading indicator that responds within weeks. This gives PMs faster feedback on whether their decisions are working. If the NSM is "weekly active projects" and it is flat after a major release, the team knows immediately that the release did not deliver expected value.
Third, the framework creates cross-functional alignment without top-down mandates. When the CEO, the engineering VP, and the marketing lead all watch the same number, they naturally coordinate. Conflicting initiatives surface quickly because someone asks "how does this help our NSM?" The framework aligns through shared visibility, not hierarchical control.
How It Works in Practice
Implementing the North Star Framework involves seven steps:
- Define the core value exchange. Ask: what is the one thing that, when a user experiences it, predicts they will stay and grow? For Spotify, it is listening to music. For Airbnb, it is booking a stay. For Slack, it is communicating with teammates. The answer reveals the product's fundamental value proposition. If you cannot articulate this clearly, product strategy work is needed before choosing a North Star.
- Identify a single metric that captures that value. The North Star Metric should measure value delivered, not revenue extracted. It should pass four tests: (1) reflects value delivered to customers, (2) is a leading indicator of revenue, (3) is measurable with current analytics, and (4) teams can influence it through product decisions. Common patterns by business type:
- Marketplace: transactions completed (Airbnb: nights booked)
- SaaS: engagement depth (Slack: messages sent in teams)
- Media/Content: consumption time (Spotify: time spent listening)
- E-commerce: purchase frequency or repeat rate
- Freemium: adoption of collaborative features (Dropbox: files in shared folders)
- Map 3-5 input metrics. Decompose the NSM into the factors that drive it. If the NSM is "weekly active projects," inputs might be: new user activation rate (do users create their first project?), collaborator invite rate (do users bring in teammates?), feature adoption breadth (are users finding value across features?), and D14 retention rate (do users come back?). Each input metric should be actionable by a specific team.
- Assign owners. Each input metric needs a team or individual responsible for moving it. The growth team owns activation. The core product team owns feature adoption. The platform team owns performance and reliability (which affects retention). Shared ownership means no ownership.
- Set targets. Define quarterly targets for each input metric. Use historical data, growth models, and OKRs to set targets that, if hit collectively, would move the NSM by the desired amount. The Product Analytics Handbook covers how to model these relationships.
- Review cadence. The North Star Metric is reviewed weekly in leadership meetings. Input metrics are monitored daily by owning teams via dashboards. If an input metric trends off-target, the team adjusts approach without waiting for the weekly review. Monthly deep-dives examine the relationship between inputs and the NSM.
- Revisit annually or at major pivots. The NSM should be stable for 1-3 years. Change it only when the product strategy shifts fundamentally. Input metrics and targets change quarterly. The stability of the NSM is what makes it useful: teams build deep intuition around a metric they track for years, not weeks.
North Star Metrics by Business Model
Choosing the right NSM depends on how the product creates value. Here are patterns that work for different business models:
| Business Model | Example Company | North Star Metric | Why It Works |
|---|---|---|---|
| SaaS (collaboration) | Slack | Messages sent in teams | Measures daily value delivery to teams |
| SaaS (productivity) | Notion | Weekly active editors | Captures ongoing engagement with the core value |
| Marketplace | Airbnb | Nights booked | Represents completed value exchange between both sides |
| Media/Content | Spotify | Time spent listening | Measures ongoing content consumption |
| E-commerce | Amazon | Purchase frequency | Captures repeat value extraction |
| Freemium | Dropbox | Files in shared folders | Measures collaborative usage that drives viral growth |
| Developer tools | GitHub | Commits pushed | Captures core developer workflow integration |
The pattern across all of these: the metric captures the moment when a user receives the product's core value, not the moment when the company extracts revenue. Revenue follows value delivery, not the other way around.
Implementation Checklist
- ☐ Articulate the core value your product delivers to customers in one sentence
- ☐ Identify 3-5 candidate North Star Metrics and evaluate each against the four tests
- ☐ Select one NSM and get leadership alignment (the CEO must agree)
- ☐ Map 3-5 input metrics that decompose the NSM into actionable levers
- ☐ Assign each input metric to a specific team or individual
- ☐ Set quarterly targets for each input metric based on historical data
- ☐ Build a dashboard that shows the NSM and all input metrics with trends
- ☐ Establish a weekly NSM review in the leadership meeting
- ☐ Define a guardrail metric (the number that must not decrease while the NSM increases)
- ☐ Communicate the NSM and input metrics to every team in the organization
- ☐ Run a quarterly retrospective on framework effectiveness
- ☐ Do not change the NSM for at least 4 quarters unless the business model pivots
Common Mistakes
1. Choosing revenue as the North Star
Revenue measures value extracted from customers, not value delivered to them. It is a lagging indicator that takes quarters to respond to product changes. Worse, optimizing directly for revenue can lead to anti-user decisions (dark patterns, price increases, feature gating) that hurt long-term growth. Revenue is the output. The NSM should be the input that predicts it.
2. Picking a vanity metric
Total signups, page views, or app downloads grow over time by default. They do not indicate whether users are getting value. A good NSM reflects ongoing value delivery, not cumulative activity. "Weekly active users" is better than "total registered users" because it measures current engagement, not historical accumulation.
3. Too many input metrics
More than 5 input metrics diffuse focus. Teams cannot track and improve 10 metrics simultaneously. Each additional input metric reduces the attention given to every other one. Start with 3-4 inputs and add only if a clear gap in the model emerges.
4. No team ownership of input metrics
If every input metric belongs to "the product team," nobody is accountable for moving any specific one. Each input metric needs a named owner who is responsible for understanding it, monitoring it, and running experiments to improve it.
5. Changing the NSM too frequently
Changing the North Star every quarter destroys its alignment value. Teams never build deep intuition around a metric they just started tracking. The NSM should be stable for 1-3 years. Input metrics and targets can change quarterly. Reserve NSM changes for genuine strategic pivots.
6. Ignoring guardrail metrics
Optimizing a North Star Metric without guardrails can lead to gaming. If the NSM is "messages sent," a team could boost it by sending automated notifications that annoy users. A guardrail metric like "NPS must stay above 40" prevents optimization that harms user experience.
Measuring Success
Track these signals to evaluate whether the North Star Framework is working for your organization:
- NSM trend. Is the North Star Metric trending upward over quarters? This is the ultimate test. If the NSM is flat or declining despite the team's efforts, either the wrong metric was chosen or the wrong inputs are being optimized.
- Input-to-NSM correlation. When input metrics improve, does the NSM also improve? If there is no correlation, the input metrics are wrong. Run correlation analysis quarterly.
- Team alignment survey. Ask every team member: "What is our North Star Metric and how does your work contribute to it?" Target: 90%+ can answer correctly. Below 70% means the framework is not operationalized.
- Decision-making speed. Track how long it takes to resolve feature prioritization debates. The NSM should shorten these by providing a shared criterion.
- Revenue correlation (lagging). Over 2+ quarters, does NSM growth predict revenue growth? This validates the choice of metric. If the NSM grows but revenue does not follow, re-evaluate the NSM.
Use the AARRR Calculator to model the funnel that connects input metrics to the North Star, and the metrics guide for selecting the right measurements.
Related Concepts
OKRs are quarterly goals that move specific input metrics contributing to the North Star. The relationship is hierarchical: NSM defines what matters long-term, OKRs define what to improve this quarter. HEART Framework is a complementary UX metrics framework (Happiness, Engagement, Adoption, Retention, Task Success) that provides a structured way to define input metrics for user-facing products. AARRR Pirate Metrics (Acquisition, Activation, Retention, Revenue, Referral) provide another decomposition model that maps naturally to input metrics. Product Strategy defines the strategic context that determines which NSM is correct. Retention Rate is one of the most common input metrics in the North Star Framework because retention is the strongest signal of ongoing value delivery.