Common OKR mistakes: six things an OKR is not

Most OKR rollouts do not fail loudly. They fade. By week four the check-ins are late, by week eight nobody opens the sheet, and at the end of the quarter the scores are filled in from memory.

The reasons are usually the same handful of OKR mistakes, and almost all of them come from treating an OKR as something it is not. Here are six, what each one looks like on a real team, and the fix.

Mistake 1: treating OKRs as a to-do list

“Launch the new pricing page” is a task. “Raise trial-to-paid conversion from 8% to 12%” is a result. The first tells you what the team will be busy with. The second tells you whether being busy helped.

A to-do list in OKR form is easy to spot: every key result starts with launch, build, write, hold or ship, and every one can be “done” without anything changing for a customer.

The fix: for each task-shaped key result, ask “and then what?” until you reach a number that moves. The page ships, and then what? More visitors start paying. That is your key result. The page goes on the plan of work under it. There is a full walk-through in how to write key results that measure outcomes.

Mistake 2: tying OKRs to performance reviews

Link OKR scores to bonuses or ratings and people learn quickly. Targets drift toward what is safe, a 0.7 starts to feel like a failure, and honest confidence scores disappear, because nobody wants to report a 4 out of 10 to the person who decides their raise.

The fix: keep OKRs and performance reviews apart. OKRs measure whether the team’s bets paid off. A review looks at how a person worked, which you see far better through notes written during the year. If you want that side of it, see notes that make performance reviews fair.

Mistake 3: putting everything in

A team that lists every responsibility as an OKR ends up with twelve objectives and no priorities. Keep-the-lights-on work, such as running support, closing the books or keeping systems up, is real and important. It just does not belong in OKRs unless you want to change how it goes.

The fix: OKRs are the few things you want to be different at the end of the quarter. Everything else runs as usual and is tracked the way it always was.

Mistake 4: set and forget

This is the most common one. The OKRs are written with care in week one, presented, and then left alone. Without a weekly check-in, OKRs quietly die by week four.

The fix: a five-minute check-in every week, per key result. Update the number, give a confidence from 1 to 10, add one line on what changed. It is not a meeting, and it should not become one. How the check-in works and what confidence means is in OKR scoring and the weekly check-in.

Mistake 5: expecting 100%

If you hit every key result, your targets were too easy. OKRs work best when some of them stretch the team, which means some will land short. For an ambitious key result, a final score of 0.7 is a good result.

The fix: say this out loud when you set the OKRs, and mean it when you score them. If the whole team always scores 1.0, raise the bar next quarter. If it always scores below 0.3, the targets are guesses, not goals.

Mistake 6: handing OKRs down only

When a manager writes every key result alone and hands them over, the team gets a list of numbers they did not choose and often cannot move. The best key results come from the people doing the work, because they know which numbers they can actually change.

The fix: set the objective together with your own manager, then ask the team to propose the key results. You keep the final say, but start from their draft.

How many objectives and key results are too many?

Overload is a mistake of its own, so here are the numbers that hold up for most teams:

Rule of thumb	Why
Two or three objectives per team, per quarter; never more than five	Every extra objective takes focus from the others
Two to five key results per objective; three is the sweet spot	One key result can be gamed; six cannot be tracked
Three to five objectives at company level	Each team picks the ones it can move, not all of them
One owner per key result	Someone who owns more than four usually updates none
At least one key result you can measure every week	Milestones alone show nothing until the very end
Carried three times? Rewrite it	It is either too big or no longer important

Here is what overload looks like in time. A team with six objectives and four key results each has 24 numbers to update every week. At five minutes each, that is two hours of check-ins, every week, before any real work. Cut it to three objectives with three key results each and it is 45 minutes, shared across owners.

How Manager Kit helps you avoid OKR mistakes

In Manager Kit, the OKRs module runs a quality check on every objective and key result. It warns, and never blocks, when a milestone reads like a task, when a key result has no “from X to Y” in its title, when an objective holds numbers, when an objective has fewer than two or more than five key results, or when most key results are milestones. Each key result has one owner, key results due a check-in appear on This week, and the carry count shows how many times a key result has moved to the next quarter. The OKR guide in the module lists these six mistakes with the rules of thumb above.