OKR vs KPI vs North Star Metric: How They Fit Together

What is the difference between an OKR and a KPI?

A KPI measures health continuously; an OKR commits a team to changing something within one cycle. KPI.org defines the first: "Key Performance Indicators (KPIs) are the critical, quantifiable measures of progress toward a desired result." A KPI has no end date. You watch churn, uptime or activation rate every week for as long as the product exists.

An OKR is different in kind. Google's re:Work guide describes objectives that "are ambitious and may feel somewhat uncomfortable" and key results that "are measurable and should be easy to grade with a number," and it notes that Google likes to set OKRs so that success means achieving 70 percent of the objectives. That 70 percent figure is Google's own grading convention, not a law of goal-setting, but it shows the intent: a KPI tells you whether things are fine, an OKR is a stretch you expect to only partly reach.

The two meet at the key result. A KPI you have decided to move this quarter becomes a key result; once the quarter is over, it goes back to the watchlist.

How do goal, objective, metric, KPI, OKR and North Star relate?

Six terms get mixed up in most planning meetings. Each one answers a different question.

Term	What it is	Question it answers	Cadence
Goal	A broad, long-term, often qualitative aim	Where do we want to be in a few years?	Set yearly or less often
Objective	A specific, short-to-mid-term direction for a team	What are we trying to change now?	Per quarter or per initiative
Metric	Any number you can measure	What happened?	Whenever you look
KPI	A metric you have chosen to watch against a target	Is this healthy?	Continuous, reviewed weekly
OKR	An objective plus a few measurable key results (Google often uses about three per objective)	Did we move what we said we would this cycle?	Usually quarterly, graded at the end
North Star Metric	The single metric that best captures the value customers get	Is the product delivering more value over time?	Continuous, reviewed weekly

The relationship is a hierarchy of attention. Be guided by the North Star, which rarely changes. Focus on a few OKRs, which change every cycle. Keep a KPI watchlist, which stays mostly stable and exists so that focusing on the OKRs does not quietly break something else.

What is the North Star Metric, and where does it sit?

The North Star Metric is the one KPI the whole product organization agrees on as the measure of delivered value. Julia Sholtz, writing for Amplitude, describes it as the metric "that best captures the value customers derive from your product." It sits above OKRs: a good quarterly objective should be explainable as a bet on moving the North Star, directly or through one of its inputs. For worked examples from real companies, see North Star Metric examples; for how inputs roll up to it, see metrics tree.

What does this look like for one product?

Take a fictional expense-management app for small businesses. The numbers below are illustrative, not benchmarks.

North Star Metric: expense reports approved each month without manual correction, across all active companies. It goes up only when companies actually use the product to close their expenses, not when they merely sign up or scan a receipt.

OKR for this quarter:

• Objective: New companies get their first clean expense report approved in their first week.
• Key result 1: Share of new companies with an approved report within 7 days rises from 22 percent to 35 percent.
• Key result 2: Median time from signup to first approved report falls from 9 days to 4.
• Key result 3: Share of first reports needing manual correction falls from 30 percent to 15 percent.

KPI watchlist (reviewed weekly, not targets this quarter): monthly company churn, receipt-scan error rate, support tickets per 100 active companies, and payment failures.

The OKR is a bet that faster first value raises the North Star over the following months. The watchlist is there because pushing new companies through setup faster could, for example, raise the scan error rate or the support load, and you want to see that the week it happens, not at the end of the quarter. For how to judge which of these measures move early and which confirm results later, see leading vs lagging indicators.

What is the difference between goals and objectives?

A goal is where the company wants to end up, stated broadly and over a long horizon: "become the default expense tool for European small businesses." An objective is the specific direction one team commits to for a cycle, with a way to tell how far it got: "new companies get their first clean report approved in their first week." Goals rarely change; objectives change every quarter or every initiative.

The practical test is whether a team can act on it on Monday. A team cannot start work on "become the default tool", but it can start work on first-week approvals. If an objective reads like a goal, it is too broad to guide anyone; if a goal reads like an objective, the company has no long-term direction for objectives to add up to. The guide on objectives, not tasks covers what an objective should contain and what it should leave to the team.

When does using OKRs and KPIs together go wrong?

The strongest objection is that running both is overhead: two sets of numbers, two review rituals, and a constant argument about which one counts. That is a real cost, and small teams often do better with a North Star and a short KPI list until they have more than one team pulling in different directions.

The common failure, though, is not overhead but confusion. Teams turn every KPI into a key result, so the OKR set becomes a dashboard with forty lines and no focus. Or they write key results as tasks ("launch the new receipt scanner"), which re:Work warns against directly: "OKRs are not a shared to-do list." Keep OKRs to a few outcomes you are choosing to move, keep KPIs as the things you are choosing to protect, and the two stop competing. The OKR definition entry covers writing key results in more detail, and AI for OKRs covers drafting and reviewing them with an assistant.

Where does this fit in Builders Camp's bootcamps?

Setting Powerful Objectives is a one-week bootcamp with 9 microlessons, directed by Andre Albuquerque and part of the Data & Analytics Specialist Track. Its published topics include outcome-first goal setting, choosing the right metrics, aligning teams and stakeholders, turning objectives into initiatives, review cadence and accountability, and common goal-setting traps. If your team already works in OKRs and the problem is the key results, How to Design OKRs is the alternative: a one-week bootcamp, also directed by Andre Albuquerque, whose published topics include objective crafting, key results that measure progress, and cadence, scoring and learning. The write-up of its practical challenge shows a broken OKR set being fixed.

Builders Camp runs live and self-paced bootcamps in product management and AI product building. See the Setting Powerful Objectives bootcamp for dates and the full syllabus.