By Hani Mebar | Äctvli Responsible Consulting
OKRs have a reputation problem.
Ask someone who’s been through a failed OKR implementation what they think of the framework and you’ll hear words like “bureaucratic,” “pointless,” “just another thing we have to fill in.” Ask someone in a company where OKRs actually work and they’ll describe something completely different — a way of connecting daily work to what actually matters, of making trade-offs visible, of moving faster without losing direction.
Both of these people are telling the truth. The framework is the same but what it’s the implementation that is quite different.
I’ve been fortunate to be inside organisations at both ends of this spectrum — large multinationals running global programs and fast-moving mid-sized companies trying to scale with coherence. The failure patterns are consistent but I think we so are the fixes.
Why OKRs Fail: My Five Most Common Patterns
1. OKRs Become a Reporting Ritual Instead of a Thinking Tool
The most common OKR failure mode. The organisation adopts the framework, sets quarterly cycles, and dutifully reviews progress at the end of each quarter. But the OKRs themselves were set in a half-day workshop in January and never seriously revisited. By April they’re irrelevant. By July nobody believes in them. By October the Q4 cycle is a chore everyone wants to get through as fast as possible.
OKRs are supposed to change how you think about priorities week to week — not give you something to report on quarterly. If your OKRs don’t influence actual decisions during the quarter — which projects get funded, which get paused, how trade-offs are made — they’re not working.
2. Too Many Objectives, Too Little Focus
OKRs came from Intel. Andy Grove used them to create ruthless focus in a complex organisation. The modern interpretation has drifted far from that.
I regularly see companies with 15 company-level OKRs. Teams with 8 objectives each. Individuals with 5 OKRs on top of their normal job responsibilities. This is not focus — it’s a spreadsheet with the word “OKR” at the top.
The rule that gets ignored most often: if everything is a priority, nothing is. A company should have 3–5 objectives at most, each with 2–4 key results. Teams should have 2–3. The discipline is in the selection, not the documentation.
3. Key Results Measure Activity, Not Outcomes
“Complete the rebranding project.” “Launch the new product.” “Run three training sessions.”
These are tasks. They’re useful as tasks. They are not OKR key results.
A key result answers one question: How will we know if we’ve achieved the objective? It measures a change in the world, not a change in your to-do list.
“Increase qualified inbound leads by 40%” is a key result. “Publish 12 blog posts” is a task that might contribute to it.
This distinction matters because activity-based key results create perverse incentives. A team can complete every task on their OKR list and move the needle on nothing that matters. When that’s what gets measured, that’s what gets optimised.
4. OKRs Are Set Top-Down Without Genuine Buy-in
Leadership sets company OKRs. Managers cascade them to team OKRs. Individuals set personal OKRs to match. The logic is sound. The ownership is absent.
When people don’t understand why an objective matters — not just that it came from above, but the actual reasoning — they don’t engage beyond the minimum required. They set key results that are easy to hit. They interpret objectives narrowly to protect their team from overcommitment.
The fix isn’t removing top-down direction — strategic intent has to come from somewhere. It’s ensuring that the translation from company strategy to team-level OKRs involves genuine dialogue. Why does this matter for us specifically? What does success look like from where we sit? Where do we have the most leverage? These conversations take time. They produce ownership that top-down assignment never does.
5. Missing OKRs Has No Consequence
OKRs work best at around 70% completion — you set ambitious targets and 70% is a strong result. This is right in principle but creates a cultural problem without careful handling.
If missing OKRs triggers no conversation, no reflection, no adjustment, people learn the numbers don’t matter. The quarterly review becomes a performance. Teams learn to set conservative targets they can consistently hit at 100% — which defeats the entire purpose.
The consequence doesn’t have to be punitive. It should be a serious, honest conversation: What happened? What did we learn? What needs to change? That conversation requires psychological safety, which requires leadership that models honest self-assessment before demanding it from others.
How to Fix a Broken OKR Program
If your OKR rollout ain’t doing what it’s supposed, the instinct is usually to improve the mechanics; i.e. better templates, a new tool, a training session. This is like putting band-aid on a deep cut and won’t work.
Start with the purpose, or as I always tell my clients: what is your North star? Then have your leadership team explicitly answer: what are we trying to achieve with OKRs that help guide us? Alignment? Accountability? Focus? Speed? Different answers lead to different implementations. If leadership can’t agree on the answer, you’ve found your root problem.
Simplify aggressively. Cut the number of objectives by half (assuming you have more than 6 let’s say). Cut key results per objective to three. Remove any key result that describes an activity rather than an outcome. This will feel like losing something. You’re actually finding the things that actually matter.
Do a bad OKR audit. Take last quarter’s OKRs and honestly categorise them: Which influenced real decisions? Which were irrelevant by month two? Which key results were tasks disguised as outcomes? Use this as a learning exercise, not a blame exercise.
Invest in the mid-quarter conversation. Most OKR programs spend 90% of their time on the quarterly set-and-review cycle and almost nothing on the weekly and monthly conversations that should happen in between. The cadence matters: a brief weekly check-in, a monthly serious review, a quarterly retrospective. The quarterly review should hold no surprises.
Make leadership behaviour the model. If senior leaders set vague OKRs, hit them all at 100%, and never acknowledge what didn’t work — the rest of the organisation follows that pattern. If they set ambitious OKRs, genuinely wrestle with trade-offs, and openly discuss misses — the rest of the organisation will eventually follow.
OKRs Are a Management Practice, Not a Tool to Deploy
The deepest mistake organisations make with OKR implementation is treating it as a system to install rather than a practice to develop.
You don’t implement OKRs and then have them. You practice them over multiple cycles, getting progressively better at setting the right objectives, writing meaningful key results, having honest progress conversations, and letting them genuinely influence how you work. The first cycle will be imperfect. The third will be better. The sixth will start to feel natural.
Companies that give up after two bad quarters are giving up on the practice before they’ve developed the skill. Companies that persist through the awkward early phases — and fix the structural problems rather than blaming the framework — are the ones that eventually describe OKRs the way the best practitioners do: not as a system they use, but as how they think.
Frequently Asked Questions About OKR Implementation
What does OKR stand for?
OKR stands for Objectives and Key Results. Objectives are qualitative, ambitious statements of what you want to achieve. Key Results are quantitative, time-bound measures that tell you whether you’ve achieved the objective.
Where did OKRs come from?
OKRs were developed at Intel by Andy Grove and popularised by John Doerr, who introduced them to Google in 1999. They have since been adopted by organisations ranging from global technology companies to mid-sized manufacturers and professional services firms.
How often should OKRs be reviewed?
Company-level OKRs are typically set annually and reviewed quarterly. Team and individual OKRs are set quarterly. Progress should be checked in weekly (briefly) and reviewed seriously at least monthly. The quarterly review should reflect what’s been tracked continuously — not a surprise assessment.
How is an OKR different from a KPI?
KPIs (Key Performance Indicators) measure ongoing performance against a baseline — they tell you if the business is healthy. OKRs are goal-setting tools — they define where you’re trying to get to and how you’ll know when you arrive. Both are useful; they serve different purposes.
How many OKRs should a team have?
A team should have no more than 3 objectives per quarter, each with 2–4 key results. More than this signals that the team is not making prioritisation decisions — they’re listing everything they do and calling it an OKR.
What is a good OKR example?
Objective: Become the go-to partner for mid-market supply chain security in the Nordics.
Key Result 1: Close 3 new Tryggvi engagements with companies between 100–500 employees.
Key Result 2: Publish 4 pieces of original content on supply chain security with 500+ organic views each.
Key Result 3: Achieve NPS of 8+ across all active engagements.
Äctvli Praeceptor is our PMO and advisory service. We help organisations build the governance structures, program management disciplines, and leadership alignment needed to make strategic execution actually work — including OKR implementation that sticks. Talk to us about your situation.