When You’re Starting Fresh: Why OKRs Beat KPIs for Leaders Navigating the Unknown
By Amal Aljamal
You walk into your new office. Fresh start. Big ambitions. But also: a team you barely know, systems you don’t understand, long-tenured employees watching skeptically, and incomplete information about everything.
Oh, and leadership wants your annual OKRs. Yesterday.
Sound familiar?
Here’s what I’ve learned: waiting for perfect clarity is a luxury you don’t have. But that doesn’t mean you’re flying blind.
The KPI Trap: When Good Isn’t Good Enough
KPIs measure what you’re already doing. Completion rate at 85%? Check. Satisfaction at 4.2 out of 5? Check. Response time under 24 hours? Check.
But here’s the problem: KPIs are the rearview mirror showing where you’ve been, not the windshield showing where you need to go.
KPIs answer “Are we doing things right?” OKRs answer “Are we doing the right things?”
When you’re tasked with real change, “doing what we’ve always done slightly better” isn’t the mandate. The mandate is evolution.
How Google Learned the Difference
In 1999, John Doerr introduced OKRs to Google’s founders. The framework came from Andy Grove at Intel, where it had transformed how the chip giant operated during the microprocessor wars of the 1980s.
What made OKRs revolutionary wasn’t just the framework – it was the mindset shift. Instead of measuring how efficiently they were doing current work, OKRs forced Google to articulate what they were trying to create that didn’t yet exist.
Early Google OKR: “Build the best search engine” wasn’t specific enough. It became “Index 1 billion URLs by end of Q4” and “Return search results in under 0.5 seconds for 95% of queries.”
Notice the difference? The objective pointed to ambition. The key results made it measurable. And critically, both pushed beyond what Google was currently achieving.
They aimed to hit 60–70% of their OKRs. If you were hitting 100%, you weren’t being ambitious enough.
The Three Elements: What + Where + Impact
Every powerful OKR answers three questions:
- What are we trying to achieve? (The Objective)
Weak: “Improve performance”Strong: “Make our product essential to customers’ daily workflow”
2. Where will we see results? (The Key Results)
Vague: “Increase engagement by 40%”Specific: “Increase daily active users from 2 million to 3.5 million by end of Q3”
3. What’s the real impact? (The Why)
When LinkedIn set an objective to “Create economic opportunity for every member of the global workforce,” their Key Results made it concrete:
• Reach 500 million members across 200 countries
• Enable 1 million jobs to be filled through LinkedIn connections
The impact? They weren’t just growing – they were becoming infrastructure for the global economy.
When Intel Bet Everything on OKRs
The most dramatic example comes from Intel in 1985. Andy Grove faced a crisis: Japanese competitors were crushing Intel in memory chips. The company was hemorrhaging money.
Grove made a radical decision: abandon memory entirely and bet on microprocessors – a market where Intel wasn’t dominant.
Traditional KPIs would have killed this idea. If they’d been tracking memory chip performance, the data would have said: “We’re the market leader; just improve efficiency and cut costs.”
But Grove’s OKRs forced different conversations:
Objective: Establish Intel as the industry standard for microprocessors
Key Results:
• Secure design wins with 80% of major PC manufacturers for our 386 chip
• Achieve 75% market share in 32-bit microprocessor segment
• Build capacity to produce 1 million 386 chips monthly
These OKRs made the memory business irrelevant. They forced Intel to build capability in a different market. They created accountability for a future that didn’t yet exist.
The result? Intel dominated the next three decades of computing. “Intel Inside” became one of the world’s most recognized brands.
Could Grove have achieved this with KPIs? Impossible. KPIs would have optimized Intel into irrelevance.
Why Now Matters More Than Perfect
"But I don’t have complete information yet. Shouldn’t I wait?”
No. OKRs don’t require perfect information – they create the path to information.
When Satya Nadella became Microsoft CEO in 2014, Microsoft was missing every major technology shift: mobile, cloud, social. He didn’t spend a year studying. He set OKRs that forced action and learning simultaneously.
Objective: Make Microsoft essential to mobile productivity – regardless of device platform
Get Amal Aljamal’s stories in your inbox
Join Medium for free to get updates from this writer.
This was radical. It meant building great software for iOS and Android – platforms competing with Windows Phone.
Key Results:
• Launch Office for iPad with 10 million downloads in first month
• Achieve 50% of Office 365 subscriptions from mobile users within first year
• Build Microsoft apps installed on 70% of iOS and Android enterprise devices
Nadella didn’t have perfect information. But waiting for it would have meant watching the market pass Microsoft by. The OKRs themselves created the learning journey.
Turning Uncertainty Into Action
Netflix illustrates this perfectly. In 2007, Reed Hastings set an audacious objective: “Become the world’s leading internet entertainment service.”
Netflix was mailing DVDs. Streaming quality was terrible. Content licensing was a mess. The market barely existed.
But the Key Results forced Netflix to build capability they didn’t have:
• Deliver 1,000 hours of streaming content to 100% of subscribers
• Build infrastructure supporting 5 million concurrent streams without buffering
• Achieve 20% of viewing hours from streaming versus DVD
Did they hit all targets perfectly? No. But the direction was right, and the learning was invaluable. Within years, they’d transformed the entire entertainment industry.
Could they have done this with KPIs measuring DVD rental efficiency? Never.
The Balance: Ambitious Yet Grounded
Google’s experience teaches us: aim to achieve 60–70% of your OKRs. If you’re hitting 100%, you’re not ambitious enough. If you’re hitting less than 40%, you’re being unrealistic.
This creates a culture shift. In KPI environments, missing targets is failure. In OKR environments, hitting 65% of an ambitious target often beats hitting 100% of a safe one.
Amazon embodies this. When building AWS, the objective wasn’t “Create a small cloud service.” It was “Build the infrastructure that powers the internet.”
Key Results:
• Support 1 million active customer accounts within two years
• Achieve 99.95% uptime across all services globally
• Enable customers to launch infrastructure in under 5 minutes versus weeks
Did they hit all of these perfectly? No. But they hit enough to create the world’s leading cloud platform – now generating more operating income than Amazon’s entire retail operation.
What This Means for You
OKRs aren’t about goal-setting. They’re about creating clarity in ambiguity, alignment in chaos, and accountability in uncertainty.
They force conversations about priorities: “If we’re committing to these, what are we not doing?”
They force honesty about resources: “Do we actually have the capability, or are we just hoping?”
They force measurement: “How will we know if we’ve succeeded?”
The companies that mastered this – Google, Intel, Microsoft, Netflix, Amazon – didn’t wait for perfect clarity. They used OKRs to create it.
They didn’t wait to understand everything. They set OKRs that forced learning.
They didn’t avoid ambitious goals because of uncertainty. They embraced uncertainty by making learning part of the framework.
Your Starting Point
Standing in that new office, facing incomplete information and high expectations?
Reject the false choice between perfect OKRs now or waiting for clarity. The choice is between direction and drift.
Write your OKRs:
• Make them clear on the what
• Specific on the where
• Honest about the impact
Be ambitious enough to drive real change but grounded enough to maintain credibility.
Share them widely. Update progress visibly. Plan to review and revise – this isn’t failure, it’s how the framework works.
Andy Grove revised Intel’s OKRs quarterly. Satya Nadella adapted Microsoft’s as results came in. That’s not weakness – that’s wisdom.
The year ahead doesn’t wait for perfect understanding. Your challenges don’t pause while you get up to speed.
The question isn’t whether you’ll face ambiguity, resistance, and pressure. You will.
The question is whether you’ll have a framework to navigate it all.
OKRs, done well, are that framework.
What will you commit to creating?
Share your OKR experiences in the comments – what’s worked, what hasn’t, and what questions you’re wrestling with.
