OKRs Are Not Your Strategy. Here Is What I Learned Running Them at Fortune 1 Scale.

By Anjan Kumar Nayak | December 2025 | 11 min read

I need to tell you something that might save your next quarter, and possibly your team's sanity: your OKRs are not your strategy. They never were. And the fact that most technology leaders treat them as interchangeable is the single biggest reason OKR implementations fail.

I have implemented, inherited, redesigned, and occasionally blown up OKR systems at McAfee, Intel, Walmart, and TVS Motor. Across 23 years, four companies, and teams spanning three continents, I have seen every version of OKR dysfunction that exists. And the root cause is almost always the same: leaders skip the strategy and jump straight to the framework.

Let me explain what I mean, and more importantly, what to do instead.

The Most Common OKR Failure I See (And It Is Everywhere)

A leadership team goes to an offsite. Someone has read Measure What Matters. Everyone is excited. They spend two days writing OKRs. They come back with 47 objectives across 12 teams. Each objective has 3 to 5 key results. There is a Notion board. There is a Slack channel. There is genuine optimism.

By week six, nobody is updating the board. By month three, the OKRs have become a performance review artefact that people fill in retrospectively. By quarter's end, the leadership team quietly moves on to the next framework.

Sound familiar? Harvard Business Review research found that only 26% of employees feel aligned with their company's strategies. And that is not because the employees are not paying attention. It is because the strategies, as expressed through OKRs, were never clear enough to align to.

Here is the fundamental problem: OKRs are a vehicle for executing strategy. They are not strategy itself. When you write OKRs without first having a clear, specific, defensible strategy, you are giving your teams a beautifully formatted list of activities that do not connect to anything meaningful.

Strategy answers: Where will we compete? How will we win? What will we say no to?

OKRs answer: Given that strategy, what outcomes do we need to achieve this quarter to know we are on track?

Skip the first question and the second one is useless.

What I Learned at Walmart (Fortune #1)

Walmart is the world's largest company by revenue. When you operate at that scale, OKR dysfunction does not just waste time. It wastes hundreds of millions of dollars in misallocated resources.

Here is what I observed and internalised about how OKRs work when they actually work:

Lesson 1: Strategy comes first, always

Before a single OKR was written, the strategic direction was crystal clear. Not "be the best supply chain in retail" (that is an aspiration, not a strategy). But specific choices: which customer segments to prioritise, which capabilities to build, which competitive threats to address, and crucially, what to stop doing.

The OKRs flowed from those choices. They did not create them. This sounds obvious, but I estimate that 80% of the OKR implementations I have seen in Indian tech companies skip this step entirely. They go straight from "company vision" to "team OKRs" with nothing in between. That gap is where alignment dies.

Lesson 2: Fewer OKRs, more conviction

At Fortune 1 scale, you would expect more OKRs, not fewer. The opposite was true. The most effective teams I worked with had 2 to 3 objectives per quarter, not 7. Each one represented a genuine strategic bet, not a restatement of business-as-usual work.

Here is the test I use now: if removing an OKR would not change anyone's behaviour, it should not be an OKR. It is just a KPI dressed up in aspirational language.

Lesson 3: The real work is in the "no"

The hardest part of OKR design is not deciding what to include. It is deciding what to exclude. At Walmart, the supply chain product team I was part of had to explicitly name the things we were not going to optimise for that quarter. Not because they did not matter. Because you cannot optimise for everything simultaneously.

Most leadership teams I work with now cannot name a single thing they have decided not to focus on. That is a strategy problem, not an OKR problem.

The Five OKR Traps I See Indian Tech Leaders Fall Into

These are specific to the Indian technology ecosystem, where I have spent significant time coaching and advising. They are not unique to India, but the cultural and organisational dynamics here make them particularly common.

Trap 1: The Cascading Waterfall

A CEO writes company OKRs. Then each VP writes team OKRs that "cascade" from the company ones. Then each director writes sub-team OKRs. By the time they reach the people who actually do the work, the OKRs are so abstracted and diluted that they have lost all strategic meaning.

What works instead: Co-create OKRs with the teams closest to execution. The leadership team defines the strategic priorities (the "what" and "why"). The execution teams propose the OKRs that will deliver on those priorities (the "how" and "how much"). This is not bottom-up versus top-down. It is both, meeting in the middle, which is where alignment actually happens.

Trap 2: OKRs as Performance Review Ammunition

The moment OKRs become tied to compensation or performance ratings, people sandbag. They set easy targets. They avoid ambitious objectives because missing them has career consequences. The entire purpose of OKRs, which is to push teams toward ambitious outcomes and learn from what works, collapses.

Google figured this out years ago. Their early OKR system explicitly separated OKRs from performance reviews. The logic was simple: if you want people to aim high, you cannot punish them for falling short. In India's corporate culture, where performance reviews carry enormous weight, this separation is even more critical.

Trap 3: Too Many OKRs, Not Enough Focus

I recently reviewed an OKR document from a 200-person Indian SaaS company. They had 43 objectives across 8 teams for a single quarter. That is not a strategy execution framework. That is a to-do list with formatting.

The research is clear on this: the most effective OKR implementations have 3 to 5 objectives per company per quarter, with 2 to 3 key results each. Anything beyond that signals a failure to prioritise, which signals a failure of strategy.

Trap 4: Confusing Outputs With Outcomes

"Launch the redesigned dashboard" is an output. "Increase user activation rate from 34% to 52%" is an outcome. Most OKRs I review are filled with outputs masquerading as key results.

The distinction matters because outputs give you a false sense of progress. You shipped the dashboard, so the OKR is "complete." But if nobody uses it differently, nothing has actually changed. Outcomes force you to measure whether the thing you shipped actually moved the needle.

Trap 5: Set and Forget

OKRs are written in January and reviewed in March. In between: silence. No weekly check-ins. No mid-quarter adjustments. No conversations about what is working and what is not.

OKRs are a learning system, not a planning system. Their power comes from the cadence of review, reflection, and adjustment. If you are only looking at them at the end of the quarter, you have turned them into a retrospective scorecard, which is the least valuable thing they can be.

What an OKR System That Actually Works Looks Like

After 23 years, here is my operating model for OKRs. It is not complicated. But it requires leadership discipline that most teams underestimate.

Step 1: Nail the strategy first (before you touch an OKR)

Before any OKR planning, your leadership team needs a one-page strategy document that answers three questions:

What are we betting on this quarter? (2 to 3 strategic themes, maximum)

What are we explicitly not focusing on? (This is where discipline lives)

What would have to be true for these bets to pay off? (Your assumptions)

If you cannot answer these three questions in clear, specific language, you are not ready for OKRs.

Step 2: Write fewer, bolder objectives

Each strategic theme gets one objective. Not three. One. And it should be ambitious enough that achieving it would represent a meaningful shift in your competitive position, your capabilities, or your market standing.

Test: if you read your objective out loud and nobody in the room feels a little nervous, it is not ambitious enough.

Step 3: Design key results that are outcomes, not outputs

Each objective gets 2 to 3 key results that are measurable, time-bound, and focused on outcomes. Not activities. Not deliverables. Outcomes.

Before writing a key result, ask: "If we achieved this number, would we actually be closer to the objective?" If the answer is not an immediate yes, you have the wrong metric.

Step 4: Build the review cadence before the quarter starts

Weekly: 15-minute team check-in on key result progress (what moved, what is stuck, what needs to change).

Monthly: 60-minute leadership review (are we on track? do we need to adjust? what have we learned?).

End of quarter: Structured retrospective (what worked, what did not, what changes next quarter).

This cadence is the product. The OKR document is just the input.

Step 5: Separate OKRs from everything else

Your team does a hundred things every quarter. Most of them are business-as-usual: keep the servers running, respond to customer tickets, ship the features on the roadmap. Those are important. They are not OKRs.

OKRs should represent the 20% of your team's effort that is aimed at changing your trajectory. Everything else is tracked through KPIs, project management tools, and regular operational reviews. Mixing them together is how you end up with 43 objectives and zero strategic clarity.

The Hard Truth About OKRs and Leadership

Here is what nobody tells you in the OKR books and certification programmes: OKRs do not create discipline. Leaders do.

When leaders consistently reinforce strategic priorities, ask the right questions in reviews, make evidence-based decisions about resource allocation, and have the courage to stop work that is not delivering, OKRs become a powerful accelerator. The framework amplifies good leadership.

When leaders are unclear on strategy, avoid difficult prioritisation conversations, reward activity over impact, and treat OKRs as an HR compliance exercise, the framework amplifies bad leadership too.

The question is not "Should we use OKRs?" The question is: "Do we have the leadership clarity and discipline to make any execution framework work?" If the answer is no, fix that first. No framework, OKRs or otherwise, can compensate for unclear strategy, weak alignment, poor communication, or inconsistent follow-through.

And if the answer is yes? Then OKRs, done right, will be the best operating system your team has ever had.

Anjan Kumar Nayak is an Executive and Leadership Coach based in Bengaluru, working with senior technology leaders, product executives, and founders. He has implemented OKR systems at Walmart (Fortune #1), Intel, McAfee, and TVS Motor across teams spanning the US, India, and APAC. Book a Discovery Call