Turning Ambition Into Something a Team Can Actually Measure
OKR stands for Objectives and Key Results: one ambitious goal, paired with a small number of measurable outcomes that prove you got there. This guide explains what an OKR is, how objectives and key results fit together, how OKRs differ from KPIs, the mistakes that make them useless, and how to run them so they change what a team actually does. It is written for managers, team leads, strategy and HR teams, and anyone who has been asked to "write some OKRs" and wants to do it well.
What an OKR Is
An OKR is a goal-setting method with two halves. The Objective is what you want to achieve, stated in plain language that a team can rally behind. The Key Results are the two to five measurable outcomes that prove you achieved it. If the objective is the destination, the key results are the instruments that tell you whether you arrived.
The method came out of Intel, where Andy Grove developed it, and reached the wider world through John Doerr, who introduced it to Google in 1999. It spread because it is simple enough to fit on one line and strict enough to stop teams from claiming success without evidence.
What makes an OKR different from a to-do list is that key results describe outcomes, not activity. "Run six webinars" is a task. "Raise qualified leads from 400 to 700 a quarter" is a key result. The first can be completed while nothing changes; the second cannot.
Objectives and Key Results, Separated
The Objective: Qualitative and Ambitious
A good objective is short, memorable, and slightly uncomfortable. It says where the team is going and why it matters, without hiding behind numbers. "Make onboarding something new customers finish without help" is an objective. It is directional, and everyone can repeat it from memory.
The Key Results: Quantitative and Falsifiable
Each key result carries a number and a deadline, and it has to be possible to fail it. Two to five per objective is the working range, because a longer list is a signal that the team has not chosen. Connecting those numbers to the wider measurement system is what performance measurement and KPI tracking is for.
Grading and the 0.7 Rule
Google grades OKRs on a scale from 0.0 to 1.0 and treats an average of 0.6 to 0.7 as the healthy range. A team scoring 1.0 every quarter is not excelling; it is sandbagging. This is why OKRs are usually kept away from bonuses: the moment the score decides someone's pay, the goals get easier.
Cadence and Alignment
Most organizations set OKRs annually at company level and quarterly at team level, then review them openly. The point of alignment is not to cascade a number down through every layer, but to let each team see how its own goals connect to the ones above, which is the same logic behind strategic alignment of projects and business goals.
How OKRs Differ From KPIs
Teams often ask whether OKRs replace KPIs. They do not. KPIs tell you whether the business is healthy; OKRs tell you what you are trying to change. Most organizations need both, and confusing them is the fastest way to get a bad set of goals.
| Dimension | OKR | KPI |
|---|---|---|
| Purpose | Change something on purpose, within a set period. | Monitor whether the business stays healthy. |
| Ambition | Deliberately a stretch; full marks every time is a warning sign. | Held at a standard; meeting it is the whole point. |
| Lifespan | Set and retired on a cycle, usually quarterly. | Tracked continuously, often for years. |
| Tied to pay | Usually not, so teams keep setting hard goals. | Often part of formal targets and appraisal. |
Keeping OKRs out of the appraisal conversation is a deliberate design choice, not an oversight. Pay, promotion, and rating belong to the systems taught in performance management and appraisal systems, which answer a different question from the one OKRs are built to answer.
Common Mistakes to Avoid
Writing the Task List Again
The most common failure is a set of key results that are really just the work the team was already going to do. If every key result would be ticked off by finishing the existing plan, the OKR is decoration. Ask what would have to be true at the end of the quarter for the objective to be real.
Setting Too Many
A team with nine objectives has no objectives. Two or three per team per quarter is usually the limit, because the value of the method lies in what it forces you to leave out.
Attaching Them to the Bonus
Tie an OKR score to compensation and you will get achievable OKRs forever. Researchers have documented what happens when goals are pushed too hard in the wrong system: narrow focus, distorted risk-taking, and, at the extreme, unethical behavior. Ambition only survives when missing is safe.
Setting Them and Never Looking Again
OKRs written in January and read in December were a paperwork exercise. A short weekly or fortnightly check on where each key result stands is what keeps them alive, and it takes minutes rather than meetings.
Making OKRs Work in Practice
Set Them With the Team, Not for the Team
Goals handed down are met with compliance; goals written together are met with argument, which is what you want. The people doing the work know which numbers can actually move, and they own the ones they helped choose.
Make Them Visible
OKRs that only the manager can see cannot align anyone. Publishing them, including the scores, is what lets two teams discover they are pulling in opposite directions before the quarter ends rather than after.
Review, Score, and Retire Honestly
At the end of the cycle, score each key result, say plainly what was missed, and decide what carries forward. Doing that across a complex organization, where goals collide and priorities compete, is the discipline behind managing complexity and strategic execution.
Frequently Asked Questions
What does OKR stand for?
OKR stands for Objectives and Key Results. The objective is a short, qualitative statement of what you want to achieve. The key results are the two to five measurable outcomes that prove you achieved it, each with a number and a deadline.
What is an example of an OKR?
Objective: make onboarding something new customers finish without help. Key results: raise the share of customers completing setup unaided from 55% to 80%; cut support tickets in the first week by half; reach an onboarding satisfaction score of 4.5 out of 5. The objective inspires; the key results settle whether it happened.
What is the difference between an OKR and a KPI?
A KPI monitors whether something important stays healthy, and it usually runs for years. An OKR sets out to change something within a cycle, and it is deliberately ambitious. KPIs tell you the state of the business; OKRs tell you what you are trying to move next.
How often should OKRs be set?
Most organizations set company OKRs annually and team OKRs quarterly, then review progress every week or two and grade at the end of the cycle. A quarter is long enough to change something real and short enough that a bad goal does not survive a full year.
Should OKRs be linked to bonuses?
Generally no. OKRs are meant to be a stretch, and the healthy grading range sits well below full marks. Once the score decides someone's pay, teams set goals they know they can hit, and the method loses the ambition that made it useful. Keep pay and rating in the appraisal system.
Turn Goals Into Results Your Teams Can Prove
EuroQuest International runs leadership and strategic management programs that put goal setting, alignment, performance measurement, and strategic execution into practice, delivered in classroom and hybrid formats across our global hubs.
Explore Leadership and Strategic Management Programs