Overview
Product teams fail at goal-setting for one predictable reason: they pick the wrong framework for the problem in front of them.
A North Star Metric gives your entire organization a single number that represents customer value. OKRs give individual teams concrete objectives with measurable results, usually on a quarterly cadence. Both frameworks work. Neither works everywhere.
The confusion between them creates two failure modes. Teams that adopt a North Star without OKRs end up with a big number on a dashboard and no plan to move it. Teams that run OKRs without a North Star produce quarterly goals that don't connect to a coherent product strategy.
This comparison will help you decide which to use, when to use both, and how to avoid the mistakes that sink either one. If you want to identify your own North Star Metric, try the North Star Metric Finder for a guided walkthrough. For a broader look at how OKRs compare with other measurement approaches, see OKRs vs KPIs.
Quick Comparison
| Dimension | North Star Metric | OKRs |
|---|---|---|
| What it is | A single metric reflecting core product value | A goal-setting framework: Objectives + Key Results |
| Scope | Company-wide, one metric | Team-level or company-level, multiple objectives |
| Time horizon | Persistent (changes rarely, tracked indefinitely) | Quarterly (reset every 3 months) |
| Number of measures | Exactly one | Typically 3-5 objectives with 2-5 key results each |
| Primary question | "Are we delivering value to customers?" | "What do we need to achieve this quarter?" |
| Best for | Alignment across teams, long-term direction | Execution focus, cross-functional coordination |
| Risk | Too abstract to drive daily decisions | Too granular to maintain strategic coherence |
| Typical adopters | Growth-stage SaaS, product-led companies | Companies of all sizes, especially 50+ employees |
| Review cadence | Weekly tracking, annual reassessment | Quarterly setting, weekly check-ins, quarterly scoring |
| Output | A dashboard with one headline number | A document with scored objectives and results |
North Star Metric: Deep Dive
What It Is
A North Star Metric is the single number that best captures the value your product creates for customers. It is not a revenue metric. It is not a vanity metric. It is the measure that, if it goes up, means customers are getting more value from your product.
The concept gained traction at Facebook (weekly active users), Spotify (time spent listening), and Airbnb (nights booked). Sean Ellis and the growth hacking community formalized the term, but the underlying idea is older: find the one number that matters most, and organize the company around it.
Strengths
Radical alignment. When every team knows the North Star, prioritization disputes resolve faster. A feature request that does not plausibly move the North Star gets deprioritized. A feature that directly moves it gets resources.
Simplicity. One metric is easy to communicate, easy to remember, and easy to track. The CEO, the newest engineer, and the support team can all answer "how are we doing?" by looking at one number.
Customer focus. Because a good North Star reflects customer value (not revenue), it forces the company to think about what customers actually care about. Revenue follows value delivery, not the other way around.
Weaknesses
Too abstract for daily work. Knowing that your North Star is "weekly active projects" does not tell a backend engineer what to build today. Teams need intermediate goals to translate the North Star into action.
Can become a vanity metric. If chosen poorly, the North Star becomes a number everyone watches but nobody influences. "Monthly active users" sounds good until you realize your product has high activation but terrible retention. The number grows from marketing spend, not product quality.
Hard to attribute. When the North Star moves, which team caused it? Attribution is notoriously difficult with a single top-level metric, which can breed resentment or free-riding.
When to Use It
A North Star Metric works best when your product has clear, measurable value delivery and you need to align multiple teams around a shared outcome. Product-led growth companies benefit the most because the metric connects directly to how customers use the product. If you are building a product strategy for a growth-stage SaaS company, the North Star gives your strategy a measurable anchor.
Real Examples
Spotify: Monthly Active Users (MAU). This captures how many people find enough value in the product to keep coming back each month. It is influenced by content quality, discovery algorithms, mobile experience, and pricing.
Airbnb: Nights Booked. A night booked means a guest found a listing they wanted, a host made their space available, and a transaction happened. It captures both sides of the marketplace.
Slack: Daily Active Users Sending Messages. Not just logging in. Sending messages. This is a critical distinction because it measures engagement, not just access. A user who sends messages is getting collaboration value from the product.
HubSpot: Weekly Active Teams. Teams, not individuals. HubSpot recognized that their value compounds when entire teams adopt the platform, so their North Star reflects team-level adoption.
OKRs: Deep Dive
What They Are
OKRs (Objectives and Key Results) are a goal-setting framework popularized by Andy Grove at Intel and later adopted by Google. An Objective is a qualitative statement of what you want to achieve. Key Results are 2-5 measurable outcomes that prove you achieved it.
Example OKR:
- Objective: Make onboarding so good that new users reach value in their first session
- Key Result 1: Increase Day-1 activation rate from 32% to 50%
- Key Result 2: Reduce median time-to-first-value from 14 minutes to 6 minutes
- Key Result 3: Decrease onboarding support tickets by 40%
The Objective describes the intent. The Key Results describe measurable proof.
Strengths
Execution clarity. OKRs tell teams exactly what success looks like this quarter. There is no ambiguity about what they should work toward.
Accountability. Each Key Result has a number, a baseline, and a target. At the end of the quarter, you score it. Did you hit it or not? This creates healthy accountability without micromanaging how teams do the work.
Cross-functional coordination. When a company aligns OKRs across teams, dependencies surface early. If the platform team's OKR depends on the data team shipping an API, that shows up in the OKR document before it becomes a blocking surprise in week 8.
Adaptability. OKRs reset every quarter. If the market shifts, you adjust next quarter's OKRs. The framework accommodates change without abandoning the discipline of goal-setting.
Weaknesses
Overhead. Writing, aligning, scoring, and communicating OKRs takes real time. In companies with hundreds of teams, the OKR cycle itself can consume 2-3 weeks per quarter. Teams start gaming the system, writing easy OKRs they know they can hit.
Disconnection risk. Without a unifying metric above them, team OKRs can pull in different directions. The growth team optimizes acquisition while the product team optimizes retention, and nobody notices they are cannibalizing each other until the end of the quarter.
Scope creep. Teams that set too many OKRs (5+ objectives, 5+ key results each) end up with a planning document, not a focus tool. The framework works when it forces hard prioritization. It breaks when teams use it to justify everything they were already doing.
When to Use Them
OKRs work best when you need structured execution across multiple teams within a defined time period. They are effective at companies that have moved past the "figure out product-market fit" stage and need coordinated delivery. If you are building a product roadmap for the quarter, OKRs give that roadmap measurable outcomes to hit.
How Quarterly OKRs Work in Practice
The OKR cycle typically follows a 3-week cadence at the start of each quarter:
- Week 1: Drafting. Leadership sets 2-3 company-level OKRs. Team leads draft team OKRs that contribute to company goals.
- Week 2: Alignment. Teams share draft OKRs with each other. Dependencies are identified. Conflicts are resolved. Key Results are refined to be measurable and ambitious but achievable.
- Week 3: Commitment. Final OKRs are published. Each team knows their objectives for the quarter.
- Weekly: Check-ins. Teams review Key Result progress in standups or weekly syncs. If a Key Result is off-track, the team adjusts tactics (not the goal).
- End of quarter: Scoring. Each Key Result is scored 0.0 to 1.0. A score of 0.7 is considered good (the target was set ambitiously). Scores feed into the next quarter's planning.
The discipline is in the rhythm, not the document. Teams that skip weekly check-ins or skip scoring at the end of the quarter lose most of the framework's value.
Decision Matrix
Use this matrix to determine which framework fits your situation:
| Your Situation | Best Fit | Why |
|---|---|---|
| Early-stage startup, fewer than 20 people | North Star Metric | You need alignment, not process. One metric keeps everyone pointed the same direction without OKR overhead. |
| Growth-stage company, 50-200 people | Both | The North Star provides strategic coherence. OKRs coordinate execution across teams. |
| Enterprise product org, 200+ people | Both (with discipline) | OKRs are essential for coordination. The North Star prevents OKRs from fragmenting into siloed busywork. |
| Single product team, no cross-functional deps | North Star Metric | OKRs add overhead you do not need. Track your North Star and work backward to decide what to build. |
| Multiple product teams with shared infrastructure | OKRs | You need explicit coordination mechanisms. The North Star alone will not resolve platform vs. feature team trade-offs. |
| Pivoting or exploring product-market fit | North Star Metric | OKRs lock you into quarterly commitments. During exploration, you need the flexibility to change direction weekly. |
| Board or investors want visibility into goals | OKRs | OKRs provide structured reporting. Investors understand the format and can see progress against targets. |
Using Them Together
The most effective product organizations use both. Here is how they fit together:
The North Star is the "why." OKRs are the "how" and "what."
The North Star Metric sits at the top of your goal hierarchy. It answers the question every team should be able to answer: "What outcome are we all working toward?" Company OKRs sit beneath the North Star and describe the 2-3 strategic bets for the quarter. Team OKRs sit beneath company OKRs and describe each team's contribution.
Example hierarchy:
- North Star: Weekly active projects created (measures product value)
- Company OKR: Accelerate time-to-first-project for new users
- Growth Team KR: Increase signup-to-first-project rate from 18% to 30%
- Product Team KR: Reduce steps in project creation flow from 7 to 3
- Platform Team KR: Decrease project creation API latency from 1.2s to 400ms
- Company OKR: Increase multi-user project adoption
- Product Team KR: Launch team workspace sharing by end of Q2
- Growth Team KR: Increase invites-per-project from 0.8 to 2.0
Each team OKR has a clear line back to the North Star. If a proposed OKR does not plausibly contribute to the North Star, it either belongs in a different quarter or should not be an OKR at all.
How to connect them in practice:
- Define your North Star Metric (use the North Star Metric Finder to stress-test your choice).
- Identify the 3-4 input metrics that most directly influence the North Star. For "weekly active projects," inputs might include activation rate, invite-sent rate, and weekly return rate.
- Set company OKRs around the input metrics you want to move this quarter.
- Let teams write OKRs that contribute to the company-level Key Results.
- Review progress against both the North Star (weekly) and OKRs (weekly check-in, quarterly scoring).
This structure gives you strategic coherence from the North Star and execution discipline from OKRs. Neither framework alone provides both.
Common Mistakes
Picking a Vanity North Star
Revenue is not a North Star Metric. Neither is total signups, app downloads, or pageviews. These numbers go up without customers getting more value. A SaaS company that counts "registered accounts" as its North Star will celebrate growth while 80% of those accounts churn in the first month.
The fix: your North Star should only increase when customers are successfully using your product. "Weekly active users completing a workflow" beats "weekly active users" because it captures value delivery, not just logins. Test your candidate metric: if it went up 20% but customers were not happier, it is the wrong metric.
Setting Too Many OKRs
Teams that set 5 objectives with 4 key results each have 20 things they are trying to achieve. That is not focus. That is a to-do list formatted as OKRs. Google's original guidance was 3-5 objectives with 2-3 key results each, and most teams should aim for the lower end.
The fix: if you cannot fit your OKRs on a single slide, you have too many. Force yourself to cut. The OKRs you remove are just as important as the ones you keep, because they represent the conscious decision to not pursue something this quarter.
OKRs That Do Not Ladder Up
When team OKRs exist in isolation, you get a collection of locally optimized goals that may conflict at the company level. The marketing team drives signups while the product team optimizes activation, and nobody notices that the signups are low-intent users who never activate.
The fix: every team OKR should trace back to a company OKR, and every company OKR should trace back to the North Star. If a team cannot explain how their Key Result moves the North Star, they need a different Key Result. Use a prioritization framework like RICE to evaluate which potential OKRs have the highest expected impact on the North Star.
Treating the North Star as Set-and-Forget
A North Star Metric is persistent, but it is not permanent. Companies that picked their North Star three years ago and never revisited it often find that the metric no longer reflects their product's value. This happens when the product expands into new use cases, the customer base shifts, or the business model evolves.
The fix: reassess your North Star annually. Ask three questions: Does this metric still reflect the core value we deliver? Is every team still able to influence it? Would a 20% increase in this metric mean customers are meaningfully better off? If any answer is no, it is time to update the metric. Track your pirate metrics with the AARRR Calculator to identify whether a different stage of the funnel better captures your current value delivery.
Bottom Line
North Star Metrics and OKRs solve different problems. The North Star tells everyone where to point. OKRs tell each team how far to go this quarter and how to measure progress.
If you are a small team searching for product-market fit, start with a North Star. The alignment it provides is worth more than the execution structure of OKRs, and you do not have enough teams to need formal coordination.
If you are past 50 people and have multiple product teams, you need both. The North Star keeps OKRs strategically coherent. OKRs keep the North Star actionable. Without the North Star, OKRs fragment into siloed goals. Without OKRs, the North Star is a number on a wall that nobody knows how to move.
The Product Strategy Handbook covers how to integrate both frameworks into your broader product strategy process. Start there if you want the full picture of how goal-setting fits into strategy, roadmapping, and execution.