North Star Metric and OKRs

A single number aligning teams toward shared outcome. North Star definition, examples, picking yours, metric trees, OKR cascade, and the anti-patterns to avoid.

Why North Star matters

Without a North Star metric, growth teams pull in different directions. Marketing optimizes for leads; sales for deals; product for engagement; support for resolution. Each can hit their target while the business stalls.

The North Star metric is a single number that represents the value your customer realizes from your product. It aligns teams toward a shared outcome. The discipline of picking it well is harder than it looks.

North Star definition

The North Star metric is:

• Customer value-aligned. Captures the real value customers get from your product.
• Predictive of revenue. Higher North Star = higher long-term revenue.
• Actionable. Teams can influence it through their work.
• Understandable. Anyone in the company can explain it.
• Singular. One metric; not a portfolio.

Examples

Company	North Star (public examples)
Airbnb	Nights booked
Spotify	Time spent listening
Slack	Daily active teams (or messages sent in qualifying teams)
Amazon	Customers' share of wallet / number of repeat purchases
Netflix	Hours streamed
HubSpot	Weekly active customer base
Notion	Weekly active teams with X workspace activity

How to pick a North Star

1. Identify what value your customer gets from your product.
2. Find a measurable proxy for that value.
3. Test correlation with revenue: do customers with high values of this metric have higher LTV?
4. Test influence: can teams improve this metric through their work?
5. Test understandability: can sales, support, product all explain it?
6. Test stability: is this still the right metric in 12 months?

Common North Star anti-patterns

• Vanity metric (downloads, signups) without value-aligned outcome.
• Revenue itself (what people do to hit revenue isn't always good).
• Composite metric (north stars need to be one thing, not five).
• Metrics teams can't influence (e.g., macroeconomic indicators).

Input metrics and the metric tree

The North Star at the top; input metrics below; leading indicators at the bottom.

• North Star: Nights booked (Airbnb example).
• Input metrics: New guest signups, listing inventory, search-to-book conversion, repeat-booking rate.
• Leading indicators: Visit-to-signup conversion, listing photo quality, search query volume.
• Each level is actionable. Teams own input metrics; their work cascades up to North Star.

OKRs and how they connect

OKRs (Objectives and Key Results) translate North Star into quarterly priorities.

• Objective: Qualitative goal aligned to North Star direction.
• Key Results: 3–5 quantitative outcomes that, if achieved, mean the objective was achieved.
• Time-bound: Quarterly (most common) or annual.
• Stretch goals: Targets that require real effort; 70% achievement is success.

Example

• Objective: Increase activation rate for new users in onboarding.
• KR1: Activation rate from 28% to 40% by Q3.
• KR2: Reduce time-to-activation from 4.2 days to 2.5 days.
• KR3: Increase 30-day retention from 45% to 55%.

Anti-patterns

• Sandbagging. Setting easy KRs to hit 100%; defeats the stretch-goal purpose.
• Activity OKRs. "Ship 5 features" instead of "achieve X outcome."
• Too many OKRs. 10 objectives per team = no priority.
• OKRs disconnected from North Star. Each team picks their own; misaligned across org.
• Penalty for missing. Defeats stretch-goal culture.
• Annual without checkpoints. No mid-cycle review; teams drift.

Cadence

• Annual North Star review. Is this still the right metric? Refresh as business changes.
• Quarterly OKR setting. 2–4 weeks before quarter; aligns to North Star.
• Monthly check-ins. Are we on track? What's blocked?
• Weekly metric review. Leading indicators tracked weekly; surface issues fast.
• End-of-quarter retrospective. What hit? What missed? What did we learn?

Advanced playbook

• Metric tree visualization. Tool or doc showing North Star → inputs → leading indicators. Reference for all teams.
• Team-level OKRs aligned vertically. Each team's KRs cascade up to company OKRs.
• Cross-team dependencies surfaced. If marketing's KR depends on product's output, document the dependency.
• Confidence scoring. Teams self-assess confidence in hitting KRs weekly; surfaces risk early.
• North Star sub-metrics by segment. Track North Star by customer cohort to identify what's growing/declining.
• Annual North Star pressure test. Is the metric still the right one as the business evolves?
• OKR scoring discipline. 0.7 is success; calibrate stretch over time.
• Public OKRs. Visible across organization; transparency drives alignment.
• OKR fatigue management. If teams cynical about OKRs, fix the process; don't blame the teams.
• Quarterly business review tied to North Star. Standing meeting; same metrics every time.

Common mistakes

• No North Star; teams pursue their own metrics.
• Multiple North Stars; defeats the point.
• Vanity North Star (downloads, signups) not tied to value.
• North Star not understood across teams.
• OKRs not connected to North Star.
• Activity OKRs instead of outcome OKRs.
• Too many OKRs per team.
• OKR penalty culture; sandbagging follows.
• Annual OKRs without quarterly check-ins.
• No metric tree; cascade from North Star unclear.
• OKRs treated as performance review; gaming follows.
• North Star never refreshed.

Operating checklist

• Single North Star metric documented
• Metric tree from North Star to leading indicators
• Quarterly OKR cadence
• Team OKRs cascade to company OKRs
• 3–5 KRs per objective; not more
• Stretch culture (0.7 = success)
• Weekly leading indicator review
• Monthly OKR check-ins
• Quarterly retrospective
• Annual North Star refresh
• Public OKR visibility
• Cross-team dependencies documented

---

Part of the Growth Marketing Foundations series.