OKRs look simple, which is exactly why they are easy to get wrong. Many organisations introduce them with enthusiasm, only to find a few quarters later that they have become a bureaucratic exercise nobody believes in. The problems are usually predictable. This guide sets out the most common OKR mistakes, grouped by stage, explains why each one causes harm and shows how to avoid it.
Key takeaways
- Most OKR problems come from too many goals, output-based key results, weak follow-through or culture.
- Focus is the point: a few meaningful OKRs beat a long list.
- Key results should measure outcomes, not tasks.
- Regular check-ins and honest reflection keep OKRs useful.
- Linking OKRs to pay and using them to judge people are among the fastest ways to undermine them.
Mistakes when setting OKRs
1. Too many OKRs
Why it hurts: when everything is a priority, nothing is. Teams spread effort thinly and make little progress on any goal.
How to avoid it: keep to a few objectives, often one to three per team, each with around three to five key results. Christina Wodtke's Radical Focus argues for a single objective per team.
2. Everything cascaded from the top
Why it hurts: rigid cascading is slow, removes teams' ownership and ignores what teams know about customers.
How to avoid it: set a few organisational objectives, then let teams propose how they will contribute, and align through conversation.
3. No connection to strategy
Why it hurts: teams work hard on OKRs that do not move the organisation forward.
How to avoid it: check that each team OKR supports at least one organisational objective.
4. Business-as-usual written as OKRs
Why it hurts: routine work dressed up as OKRs crowds out real priorities.
How to avoid it: track routine health with KPIs, and reserve OKRs for change. See OKRs vs KPIs.
Mistakes when writing OKRs
5. Tasks as key results
Why it hurts: "Launch the new feature" can be done without any benefit to customers. It measures activity, not results.
How to avoid it: ask "how would we know the feature worked?" and measure that instead. Keep tasks as initiatives.
6. Vague key results
Why it hurts: "Improve customer experience" cannot be measured, so nobody knows whether it was achieved.
How to avoid it: use a specific measure with a baseline and a target, such as "from 3.8 to 4.4".
7. Targets without baselines
Why it hurts: a target plucked from the air is either trivially easy or impossible.
How to avoid it: look up current values first. If there is no data, make establishing a baseline part of the plan.
8. No counter-measures
Why it hurts: some key results can be hit in harmful ways, such as reducing call times by rushing customers.
How to avoid it: add health measures that must not suffer. See how to write good OKRs.
9. Key results the team cannot influence
Why it hurts: teams feel powerless and disengage.
How to avoid it: choose measures the team can realistically move, or share the OKR with the teams who can.
10. Unclear ambition
Why it hurts: nobody knows whether 70% is success or failure.
How to avoid it: label each OKR as committed or aspirational.
Mistakes when running OKRs
11. Set and forget
Why it hurts: OKRs written in the first week and not looked at again until the last week change nothing.
How to avoid it: hold short weekly check-ins with confidence scores. See how to run OKR check-ins.
12. Never adapting
Why it hurts: keeping an outdated OKR after circumstances change wastes effort.
How to avoid it: change initiatives first, and change OKRs openly, with an explanation, when truly needed.
13. Adapting too easily
Why it hurts: goals lowered whenever they get hard lose all meaning.
How to avoid it: agree when OKRs can change, typically only for significant changes in circumstances, and discuss it openly.
14. No reflection
Why it hurts: the same mistakes repeat quarter after quarter.
How to avoid it: end every cycle with a short reflection on what worked and what to change.
Mistakes of culture
15. Linking OKRs to pay
Why it hurts: if bonuses depend on scores, people set safe goals and report optimistically. Many practitioners, including John Doerr, advise keeping OKRs separate from compensation.
How to avoid it: use OKRs for focus and learning, and handle performance and pay through separate conversations.
16. Using OKRs to judge or blame
Why it hurts: people stop reporting problems and stop setting ambitious goals.
How to avoid it: treat missed key results as information. Leaders' reactions to bad news matter most. See psychological safety in agile teams.
Mistakes in agile organisations
- OKRs as fixed scope: treating initiatives as a quarterly plan that cannot change undermines Scrum's empiricism.
- Bypassing the Product Owner: OKRs should inform product decisions, not take them away from the person accountable for the Product Backlog.
- Replacing Sprint Goals: every Sprint still needs a Sprint Goal.
See OKRs and Scrum for how to avoid these.
How these mistakes show up in practice
These short illustrations show how common mistakes appear in real organisations.
The spreadsheet nobody reads
A company introduces OKRs with a large spreadsheet. Every team writes five objectives with five key results each. By week three, nobody opens the spreadsheet; by the end of the quarter, teams fill in scores from memory. The fix is fewer OKRs, a short weekly check-in and a single page each team actually uses.
Tasks dressed as results
A product team's key results are "Launch search", "Launch filters" and "Launch saved lists". All three launch on time, and the team scores 1.0. Customers, however, are no more likely to find what they need. The fix is to measure outcomes, such as the share of searches that lead to a purchase, and keep the launches as initiatives.
The bonus effect
A sales organisation ties bonuses to OKR scores. The next quarter, every team sets targets it knows it can hit, and the organisation's growth stalls. The fix is to separate OKRs from pay, so teams can aim high and report honestly.
Signs your OKR process is becoming bureaucratic
- Setting OKRs takes longer than a couple of weeks each quarter.
- Teams spend more time formatting OKRs than discussing them.
- Check-ins are skipped or turned into status reports.
- Nobody can remember their team's OKRs without looking.
- OKRs are updated for leadership reports rather than used by teams.
How to recover from a failed OKR rollout
- Acknowledge it: say openly that the first attempt did not work as hoped, and ask teams why.
- Simplify: reduce the number of OKRs and remove unnecessary process and tooling.
- Restart with volunteers: pilot with a few teams who want to try again.
- Fix the culture signals: separate OKRs from pay and make it safe to miss ambitious goals.
- Build the rhythm: short weekly check-ins and a real reflection at the end of the quarter.
- Share results honestly: including what did not work, before expanding again.
Mistakes leaders make
- Setting too many organisational objectives, which makes team focus impossible.
- Dictating team OKRs, which removes ownership.
- Not following up, which signals that OKRs do not really matter.
- Reacting badly to missed goals, which teaches teams to aim low.
- Changing priorities constantly without updating OKRs, which makes them meaningless.
A quick OKR health check
- Does each team have only a few OKRs?
- Can every key result be measured, with a baseline and target?
- Do key results measure outcomes rather than tasks?
- Does the team check in at least every week or two?
- Is it clear which OKRs are committed and which aspirational?
- Are OKRs separate from bonuses?
- Do people feel safe reporting falling confidence?
- Does the team reflect at the end of each cycle?
If several answers are "no", start by fixing one or two, rather than redesigning everything at once.
Learn more
Our complete OKR guide explains the basics. Scrum Agile OKR Plus covers using OKRs with agile teams; it includes self-paced training and an online exam on ExamVault by CertExpert with three attempts included, and the certificate and digital badge are valid for two years.
Frequently asked questions
What is the most common OKR mistake?
Setting too many OKRs, closely followed by writing tasks as key results.
Why do OKRs fail?
Usually because of too many goals, output-based key results, no regular check-ins, or a culture that punishes missed goals.
Should OKRs be linked to bonuses?
Many practitioners advise against it, because it encourages safe goals and inflated reporting.
Can OKRs be changed during the quarter?
Yes, for significant changes in circumstances, openly and with an explanation. Change initiatives before changing goals.
How many OKRs is too many?
If a team cannot remember its OKRs without looking them up, it probably has too many.
Are OKRs just a new name for targets?
They should not be. OKRs combine a meaningful objective with outcome measures, and are designed for focus and learning rather than top-down targets.
What should we do if our OKRs feel like bureaucracy?
Reduce their number, simplify the process, focus check-ins on priorities and problems, and reflect honestly on what is not working.
How do we know our OKRs are working?
Teams are focused, progress is visible, problems surface early, and each cycle improves on the last.