OKRs Done Wrong: The Most Misused Framework in Business

Objectives and Key Results, the framework that Google made famous, is one of the most powerful management tools ever invented. It is also, in the hands of most companies, one of the most reliably destructive. The framework is not the problem. The way it gets implemented is. Done right, OKRs align an entire organisation around a few priorities. Done wrong, they create a bureaucracy of meaningless goals, gaming, and frustration.

The pattern is always the same. A company hears about OKRs, rolls them out with great fanfare, everyone writes objectives, everyone struggles with key results, and six months later the whole thing is quietly abandoned, with a lingering resentment toward "that goal-setting stuff". The failure is predictable, and it is entirely avoidable.

1. The Framework in One Paragraph

The whole of OKRs fits in one paragraph. Objectives are qualitative, inspiring statements of what you want to achieve: "become the most reliable provider in our market". Key results are quantitative measures of how you will know you got there: "achieve 99.9% uptime", "cut complaint rate in half". Objectives say where you are going. Key results say how you will know you arrived.

That is the entire framework. Everything else is implementation. And the implementation is where the trouble starts, because companies cannot resist adding process: cascading, scoring, grading, linking, reviewing, all of which is optional, and most of which is harmful.

2. The Cascade Mistake

The most common implementation error is the cascade: the company sets its OKRs, then each department copies them, then each team copies the departments, until every person in the organisation has five objectives and twenty-five key results, all saying roughly the same thing.

The cascade fails because it multiplies bureaucracy without adding direction. The company objective becomes meaningless by the time it reaches the individual, and the individual's OKRs become a paperwork exercise detached from real work. The antidote is the opposite: few objectives, owned locally. The company has its objectives, and each team sets its own, connected by intention but not by copying. Alignment is a direction, not a template.

3. The Goals-As-Contract Mistake

The second killer is treating OKRs as a performance contract. The moment key results are linked to bonuses or reviews, the behaviour changes. People set easy goals they can surely hit. People sandbag. People game the numbers. People fight to remove anything uncertain from their objectives, which removes exactly the ambitious work that OKRs exist to encourage.

OKRs are a planning tool, not a performance tool. The distinction is fundamental. The plan says "this is what we intend to do". The review says "this is how well you did". Mixing them corrupts both: the plan becomes conservative, and the review becomes a negotiation. The teams that use OKRs well never connect them to compensation, and the freedom is what makes the goals honest.

4. The Everything-Is-Important Mistake

The third killer is the list. An OKR system where every team has ten objectives is not an OKR system, it is a to-do list with better formatting. The entire point of the framework is focus: if everything is important, nothing is, and the framework has failed at its one job.

The discipline is brutal and simple: a team should have no more than three objectives, and each objective should have no more than three key results. That is nine numbers for a quarter, and even that is a lot. The question that enforces the discipline is "what are we not doing this quarter". If you cannot name the things you are refusing, you have not actually prioritised.

5. The Key Results Are Not Metrics

A key result is not "improve customer satisfaction". That is a wish, not a measure. A key result is "raise our support satisfaction score from 4.1 to 4.4". It is specific, numeric, and time-bound. The difference between the two is the difference between hoping and managing.

The hard work of OKRs is precisely this: converting vague intentions into measurable outcomes. The conversion forces the team to define what success means, and defining success is where the real thinking happens. If the team cannot agree on a number, they do not actually agree on what they are trying to do, and the argument they are avoiding will surface anyway, later, expensively.

6. The Stretch Goal Fallacy

Google's original OKR culture included the idea of stretch goals: ambitious targets that you might only hit seventy percent of, and that is fine. Most companies adopted the mechanics without the culture. They set stretch goals and then punished the seventy percent, which produces the sandbagging described above.

The stretch goal only works if failure is genuinely safe. The leader's job is to say, explicitly and repeatedly, "we are setting goals we may not hit, and that is the point". Without that permission, the entire framework collapses into conservatism. The teams that get the most from OKRs are the ones where the leader has actually created the safety, not just the slide.

7. The Weekly Pulse

OKRs die between quarters. Written in a workshop and forgotten until the next workshop, they become decoration. The fix is the weekly pulse: a short, regular check where each team asks "are we on track for our key results, and what is blocking us".

The pulse does not need to be elaborate. Fifteen minutes, a simple status per key result, and a focus on blockers rather than blame. The pulse is what keeps the goals alive, and it is also the early warning system that catches the quarter before it collapses. The teams that skip the pulse are not too busy for OKRs, they are too busy to have direction, which is a very different problem.

8. The Honest Version

The honest version of OKRs is unglamorous. A few objectives. A few numbers. A weekly pulse. A leader who actually wants to know the truth. No cascade, no contracts, no games. The framework succeeds exactly to the degree that the company can tolerate honesty about what it is trying to do.

And that is the real lesson: OKRs do not create honesty, they reveal its absence. The company that cannot set three priorities, cannot agree on numbers, cannot discuss failure, will fail at OKRs, and the failure will be blamed on the framework. The framework is a mirror. It shows you how your organisation actually thinks. If you do not like what you see, the mirror is not the problem.

Tags

#management #business