Overview
OKRs and North Star Metrics are two of the most widely adopted goal-setting tools in product organizations. They get mentioned in the same conversations, appear on the same strategy slides, and often confuse teams who are not sure how they relate.
Here is the short version: they are not competing frameworks. A North Star Metric tells you where to point the ship. OKRs tell you how fast to row and in which direction this quarter. Used together, they create a goal system that is both stable and actionable.
What Is a North Star Metric?
A North Star Metric is a single metric that captures the core value your product delivers to users. It serves as the primary measure of long-term product health and guides strategic decisions across the entire organization.
Characteristics
- Single metric: One number, not a dashboard of ten
- User-value focused: Reflects value delivered, not revenue extracted
- Leading indicator: Predicts long-term business outcomes (revenue, retention)
- Stable: Changes rarely, typically persists for years
- Company-wide: Every team can influence it
Examples by Company Type
| Company Type | North Star Metric |
|---|---|
| Social network | Daily Active Users |
| SaaS tool | Weekly Active Teams |
| Marketplace | Transactions per week |
| Media platform | Total watch hours |
| E-commerce | Purchase frequency |
The best North Star Metrics are correlated with revenue but are not revenue itself. Revenue is a trailing indicator that reflects past value delivery. The North Star captures current value delivery that will produce future revenue.
What Are OKRs?
OKRs (Objectives and Key Results) are a quarterly goal-setting framework where teams define ambitious Objectives and measurable Key Results that indicate progress toward those Objectives.
Structure
- Objective: Qualitative, inspiring goal that describes where you want to go
- Key Results (2 to 4 per Objective): Quantitative measures that indicate whether you reached the Objective
- Time-bound: Typically set and evaluated quarterly
- Cascading: Company OKRs inform team OKRs, which inform individual OKRs
Example
Objective: Make onboarding effortless for new users
- KR1: Increase 7-day activation rate from 35% to 50%
- KR2: Reduce median time-to-first-value from 8 minutes to 3 minutes
- KR3: Decrease support tickets from new users by 40%
OKRs are intentionally set at 60 to 70% expected achievement. If you hit 100% of every Key Result, your targets were too conservative. This differs from traditional KPIs, which are typically set at achievable levels.
How They Differ
| Dimension | North Star Metric | OKRs |
|---|---|---|
| Scope | One metric, whole company | Multiple objectives, multiple teams |
| Time horizon | Years | Quarters |
| Stability | Rarely changes | Refreshed every quarter |
| Specificity | Single measure of value | Specific targets with deadlines |
| Who sets it | CEO/CPO with leadership team | Each team, aligned to company direction |
| Achievement target | Continuous improvement | 60 to 70% stretch targets |
| Function | Strategic compass | Tactical execution framework |
How They Work Together
The North Star Metric and OKRs form two layers of the same goal system.
Layer 1: North Star Metric (strategic). This is the constant. It defines what "winning" looks like for the product. Every team should be able to explain how their work connects to the North Star. If they cannot, the work is either misaligned or the connection needs to be made explicit.
Layer 2: OKRs (tactical). Each quarter, teams set OKRs that target the input metrics driving the North Star. These input metrics are the levers your team can pull to move the single number that matters most.
The Input Metric Tree
A North Star Metric decomposes into input metrics, and those input metrics become Key Results in your OKRs.
For example, if your North Star is Weekly Active Teams:
- Acquisition: New team signups per week (Growth team OKR)
- Activation: Percentage of new teams that complete setup (Onboarding team OKR)
- Retention: Percentage of teams active after 90 days (Core product team OKR)
- Expansion: Average team size growth (Platform team OKR)
Each team owns a different input metric. Each team's OKRs target improvement on their input metric. The sum of all team efforts moves the North Star. This structure prevents teams from working in isolation while giving each team clear ownership over their piece of the puzzle.
Aligning OKRs to Your North Star
Step 1: Define the North Star
Choose a metric that reflects the core value exchange between your product and your users. Validate that it correlates with revenue over historical data. Get executive alignment that this is the single metric the company will rally around. See our product metrics guide for more on choosing the right measures.
Step 2: Decompose Into Input Metrics
Map the 3 to 5 input metrics that drive the North Star. Use your product strategy to identify which inputs have the most room for improvement this quarter.
Step 3: Assign Input Metrics to Teams
Each team should own one primary input metric. Some teams may share an input metric (e.g., both growth marketing and product growth work on acquisition), but ownership should be clear.
Step 4: Set Quarterly OKRs Against Input Metrics
Each team writes OKRs that target their input metric. The Objective states the qualitative aspiration. The Key Results quantify the target improvement for the quarter.
Step 5: Review the Chain Monthly
Check whether team OKR progress is translating into North Star movement. If teams are hitting their Key Results but the North Star is flat, the input metric model needs revision.
Common Mistakes
Treating the North Star as an OKR. The North Star is not a quarterly target. It is a long-term compass. Setting a quarterly target against it is fine (as a top-level KR), but the North Star itself should persist beyond any single quarter.
Setting OKRs that do not connect to the North Star. If a team's OKRs cannot be traced back to an input metric that drives the North Star, either the OKRs are misaligned or the input metric model is incomplete. Every OKR should have a clear causal path to the North Star.
Picking a North Star that is too lagging. Revenue, NPS, and annual contract value are important metrics, but they move too slowly to guide quarterly decisions. Choose a metric that responds to product changes within weeks, not months.
Cascading OKRs too rigidly. OKR alignment should be directional, not mechanical. Teams need autonomy to define how they will move their input metric. Top-down cascading where leadership dictates every team's Key Results kills ownership and creativity.
Ignoring counter-metrics. A team focused on increasing activation rate might do so by lowering the bar for what counts as "activated." Pair each input metric with a counter-metric (e.g., 30-day retention) to ensure quality is not sacrificed for quantity. The RICE framework can help evaluate whether specific initiatives genuinely improve the metric or just game it.
When You Only Need One
Not every organization needs both systems simultaneously.
Early-stage startups (pre-product-market fit): Use the North Star Metric only. Your entire team of 5 to 10 people can rally around a single number without formal OKR processes. Hold weekly standups focused on what moved the North Star this week and what will move it next week.
Growth-stage companies (20 to 200 people): Use both. The North Star provides strategic coherence across teams. OKRs provide tactical focus and accountability within teams.
Enterprise organizations (200+ people): Use both, with additional governance. At this scale, you likely need an OKR coordination process (quarterly planning, cross-team dependency mapping) to prevent misalignment between dozens of teams all trying to move different input metrics.
Making Them Stick
The biggest risk with both frameworks is that they become paperwork rather than decision-making tools. To keep them alive:
- Reference the North Star in every product review. Start meetings with the North Star trend line.
- Grade OKRs publicly every quarter. Share results across the company, including misses.
- Use OKRs to say no. When a request comes in that does not connect to a current OKR or the North Star, that is a signal to deprioritize it.
- Update input metric models. The relationship between input metrics and the North Star is a hypothesis. Test it with data and revise quarterly.
The best product teams treat their North Star as a fixed point and their OKRs as the evolving plan for reaching it. The North Star keeps everyone pointed in the same direction. OKRs keep everyone moving.