OKRs vs KPIs vs goals: what each one is for, with examples for a 10-person team
A goal is a direction, a KPI is a number you watch, and an OKR is a goal with measurable results and a deadline.
On this page
A goal says where you want to end up. A KPI is a number you keep watching to know whether the business is healthy. An OKR is a goal written with two to five measurable key results and a deadline, so that in a quarter you can say plainly whether you got there. KPIs monitor; OKRs push; goals point. Most small teams need KPIs, a few goals, and OKRs only once the team is large enough that people would otherwise pull in different directions.
That is the whole distinction. The rest of this post gives one worked example of each for a 10-person team, a comparison table, the case for skipping OKRs when you are small, and how we keep ours visible without turning it into a ritual.
Goals: the direction
A goal is a statement of intent with no particular format: "become the default tool for independent clinics in the UK", "ship the mobile app this year", "stop losing customers in month two". Goals are useful because they are short and memorable, and they are weak for the same reason. Two people can agree on the goal and disagree completely on what counts as achieving it.
A goal does not need a number. It needs an owner and a rough horizon. Where it fails is when a team has twelve of them and nobody can say which three matter this quarter.
Example for a 10-person team. "Make onboarding good enough that new customers do not need a call." That is a clear direction. It says nothing about how you will know, which is what the other two formats add.
KPIs: the numbers you watch
A key performance indicator is a metric the business tracks continuously because it reflects health: monthly recurring revenue, churn, active customers, support response time, cash runway, deals won per month. A KPI does not have a deadline. It has a current value, a history and usually a threshold that triggers attention.
KPIs are operational. You look at them every week whether or not anything is changing, and the point is to notice early when something is. They are not targets by themselves; "churn" is a KPI, "cut churn to 2% by March" is a target built on it.
Example for a 10-person team. Monthly churn, tracked weekly, with a line at 3%. Nobody is working on it specifically this quarter; if it crosses the line, somebody will be.
OKRs: goals with measurable results
Objectives and key results come from Andy Grove's management practice at Intel, and were spread widely by John Doerr, who brought them to Google and wrote them up in "Measure What Matters" in 2018. The format is simple:
- An objective: a qualitative, motivating statement of what you want to achieve in a fixed period, usually a quarter.
- Two to five key results: measurable outcomes that, if hit, mean the objective was achieved. Each has a number and a baseline.
The discipline is in the key results. They must be outcomes, not tasks. "Launch the new onboarding flow" is a task; "70% of new customers complete setup without a support call, up from 40%" is a result. A team can finish every task and miss the outcome, and the OKR is designed to make that visible.
OKRs also carry a built-in cadence: set at the start of the period, checked in on regularly, scored at the end. Grading is honest rather than punitive; a key result scored at 0.7 is a normal outcome for an ambitious target, and scoring 1.0 on everything usually means the targets were too safe.
Example for a 10-person team.
Objective: New customers succeed without us holding their hand.
Key results, Q1:
- 70% of new workspaces complete setup within 24 hours, from 40%.
- Onboarding support tickets per new customer fall from 1.8 to 0.5.
- Month-two retention rises from 78% to 88%.
Notice that the goal from the first section became the objective, and the KPI from the second section (churn, in its month-two form) became a key result. The three formats are not competing; they are the same concern at different levels of precision.
OKRs vs KPIs vs goals: the comparison
| Goal | KPI | OKR | |
|---|---|---|---|
| What it is | A direction | A metric you monitor | An objective with measurable key results |
| Has a number | Not necessarily | Always | Every key result does |
| Has a deadline | Loosely | No; it is continuous | Yes; usually a quarter |
| Changes how often | Rarely | The metric is permanent; thresholds move | Every period |
| Answers | Where are we going? | Are we healthy? | Did we move the thing we chose to move? |
| Best for | Giving a team a shared story | Spotting problems early | Focusing effort on a few outcomes |
| Fails when | There are too many, or no owner | It is mistaken for a target | Key results are tasks, or there are too many |
| Typical count for 10 people | 2 to 4 standing | 5 to 10 watched weekly | 1 to 3 objectives per quarter |
How the three fit together
The practical arrangement for a small company is layered. Goals set the story for the year. KPIs run underneath all the time and tell you when something needs attention. OKRs are how you choose, each quarter, which one or two things to push on deliberately, and they borrow their key results from the KPIs you already watch.
This keeps the work small. You are not inventing new metrics for the OKR; you are picking the existing ones you want to move and naming the target. When the quarter ends, the KPI keeps running, and the OKR is either scored and closed or carried into the next quarter with a new number.
The mistake we see most often is running all three as separate systems: a goals page nobody opens, a KPI dashboard nobody reads, and an OKR spreadsheet updated the week before the review. The fix is to put the key results next to the metrics they come from and look at both in the same weekly check.
When a startup should skip OKRs
OKRs are a coordination tool. They earn their cost when enough people are working on enough things that, without a shared list of outcomes, effort scatters. Below that point they are overhead, and we would say that plainly to any team of our size asking.
Skip OKRs for now if:
- You are fewer than about eight people and sit in the same channel. Everyone already knows what matters this month. A written objective adds a ceremony to a conversation that is already happening.
- You have not found what to repeat yet. Pre-product-market-fit, the honest objective every quarter is "find out", and key results for discovery are mostly made up. Track inputs (conversations, experiments) and one or two KPIs instead.
- Your priorities change every few weeks. A quarterly OKR that is rewritten in week three has cost you the setting and the rewriting and given back nothing.
- Nobody will check in. An OKR that is looked at twice, at the start and the end, is a goal with extra formatting.
Adopt OKRs when two or more of these become true: there are more than one or two teams, people are surprised by what others are working on, the founders cannot be in every decision, or an investor or board wants to see quarterly targets and results. At that point the format pays for itself, because it is cheaper than the meetings it replaces.
How we keep ours visible
We run a team of between five and ten on our own products, and we have gone back and forth on this. What settled for us is one or two objectives a quarter, each with three key results taken from numbers we already track, and a short check-in every other week where whoever owns each key result updates the current value and one sentence of context.
We keep them in Atrix, our workspace, because that is where the work and the numbers already are. Atrix Goals holds an objective with its key results, each with a baseline, a target and a current value, and a check-in records the new value and a note so the history is kept. The goal sits next to the projects and issues that serve it, which is the whole reason we do it there rather than in a slide. It is a plain structure: there is no automatic scoring, no cascading of objectives through an org chart, and no dashboard that pulls KPIs from outside tools; the check-in is a person typing a number. For a team that wants OKR software with rollups and alignment maps, dedicated tools do more. For a team that wants the objective in the same place as the work, this is enough, and the goal-setting template is where we started.
FAQ
What is the difference between an OKR and a KPI?
A KPI is a metric you monitor continuously to judge health, with no deadline. An OKR is an objective for a fixed period with two to five measurable key results. Key results are often built on KPIs: the KPI is "churn", the key result is "reduce churn from 3% to 2% by the end of Q2".
Are OKRs the same as goals?
No. A goal is a direction with no required format. An OKR is a goal written in a specific shape: a qualitative objective plus measurable key results and a deadline. Every OKR contains a goal; most goals are not OKRs.
Can a KPI be a key result?
Yes, and it usually should be. A key result is a KPI with a baseline, a target and a date attached. Choosing key results from metrics you already track keeps the OKR cheap to run and makes the check-in honest.
How many OKRs should a small team have?
One to three objectives per quarter, each with two to five key results, for the whole company. More than that and the focus the format is meant to provide disappears. A ten-person team usually does best with one or two.
Do startups need OKRs?
Not early. Under about eight people, or before product-market fit, or when priorities change weekly, OKRs add ceremony without coordination benefit. Track a handful of KPIs and keep one or two plain goals. Adopt OKRs when multiple teams or an outside board need a shared list of quarterly outcomes.
Who invented OKRs?
The practice comes from Andy Grove at Intel. John Doerr learned it there, introduced it to Google, and described it in his 2018 book "Measure What Matters", which is where most teams first meet the format.
Next step
Read the OKR entry in the glossary for the format and a scoring note, then write one objective with three key results using the OKR template. If the numbers you need are already in your workspace, keep the goal next to them and check in every other week.