Why OKRs fail in organisations that already use them

The first OKR cycle often goes well.

There's energy, curiosity, and a genuine attempt to set meaningful objectives. Leadership is engaged. Teams are excited about a new way of working. Key results are debated, agreed, and — for the most part — taken seriously.

By the third cycle, something has shifted. OKRs are still happening, but the energy has gone. Key results are vague or over-safe. Reviews are perfunctory. Teams treat OKRs as a compliance exercise rather than a management tool. Leaders wonder whether OKRs were the right call.

This is the most common failure mode I see — not organisations that reject OKRs, but organisations that adopt them, see early promise, and then watch them slowly hollow out.

Why the second cycle is harder

The first cycle works partly because of novelty and partly because the OKRs are usually set by people who care deeply about making them good. Leaders spend time on them. External facilitators help. There's a shared sense that this matters.

The second and third cycles expose what the first cycle didn't need: a functioning operating system to hold OKRs in place.

OKRs only work as part of something bigger. They need:

• A genuine strategic intent they're designed to measure
• A portfolio process that aligns work to the outcomes
• A review rhythm that treats key result progress as a signal to act on
• Enough psychological safety for teams to set honest, stretching targets rather than safe ones

Without those things, OKRs drift. They become a layer on top of how the organisation actually operates, rather than the lens through which it operates.

The patterns that hollow OKRs out

Targets set to hit, not to stretch. The first cycle usually includes some honest conversation about what ambitious but achievable looks like. By the third cycle, teams have learned that key results they miss are uncomfortable to explain. They respond by setting targets they're confident they can reach. The result is key results that are technically met but don't represent any real progress.

Disconnection from the actual work. If the day-to-day work doesn't connect visibly to the key results, the key results become irrelevant. Teams do their jobs. They score their OKRs at the end of the quarter. The two activities feel unrelated. This is usually a signal that either the OKRs are set at the wrong level or the portfolio process isn't working.

Review rituals that don't change anything. The OKR review meeting happens. Progress is reported. Nothing changes as a result. Nobody is challenged on a key result that's slipping. No decisions are made about what to do differently. The review becomes a status update rather than a steering conversation.

Leadership OKRs that aren't really owned. In many organisations, the leadership team sets aspirational company-level OKRs but doesn't treat them as genuine personal commitments. The OKRs live in a document but don't visibly shape how leaders spend their time or make decisions. Teams notice this. They conclude that OKRs are for them, not for leadership. Engagement falls.

Too many OKRs. The format invites coverage. Teams add key results until every workstream has a measure. The result is a sprawling set of targets that nobody can hold in their heads and which compete with each other for attention. Two or three genuinely important key results are worth more than ten diffuse ones.

What actually makes OKRs stick

OKRs are a measurement tool, not a management system. They show you whether you're moving in the right direction. They don't replace the conversations, decisions, and operating rhythms that strategy actually requires.

Organisations that make OKRs work over time tend to do a few things differently:

They use OKRs to connect, not to cover. Company-level key results reflect genuine strategic choices. Team-level key results show how the team is contributing to those choices. The connection is visible and deliberate — not aspirational.

They run honest mid-quarter conversations. A key result that's off track is a signal, not a failure. The mid-quarter check-in is an opportunity to understand what's happening and make adjustments. Organisations that treat missed key results as failures to avoid create an environment where honesty disappears.

They protect OKR count. Three company objectives. Three key results each. That's it. The discipline of a small set focuses attention and makes the OKRs meaningful. When organisations try to represent everything they're doing in OKR format, the format loses its purpose.

They change the leadership operating rhythm. If OKRs don't show up in how the leadership team reviews performance and makes decisions, they won't influence how anyone else operates. The leadership calendar has to reflect the OKR cycle.

The harder question

If your OKRs aren't working, the instinct is often to improve the OKRs themselves — better workshops, clearer templates, more training.

Sometimes that helps. More often, the OKRs are a symptom. The underlying problem is that the organisation doesn't have a functioning strategy-to-execution system — a clear intent, a coherent portfolio, a working delivery system, and a review rhythm that generates real learning.

OKRs were designed to live inside that system. When they're introduced without it, they do their best — but they can't substitute for what isn't there.

---

I run a specialist OKR Hub offering consulting, training, and implementation support for organisations working with OKRs. If your OKR programme has stalled, that's a good place to start.