There’s a management paradox that plays out in organisations of almost every size: the people doing the work are busy, the leaders setting the direction are busy, and yet somehow the two groups are frequently working toward subtly different things. Not because anyone is misaligned in principle. But because “aligned in principle” and “aligned in practice” turn out to be very different conditions.
John Doerr spent decades watching this gap open and close, and Measure What Matters is his answer to the question of how to close it deliberately. The tool he offers — OKRs — is deceptively simple. The discipline required to use it well is anything but.
Where OKRs Actually Come From
Before the framework, the origin story — because it matters more than most books acknowledge.
Doerr didn’t invent OKRs. He learned them from Andy Grove at Intel in the late 1970s, when Grove was running one of the most operationally disciplined technology companies in the world. Grove’s insight was that clarity about what you’re trying to achieve, combined with measurable evidence of whether you’ve achieved it, produces a fundamentally different quality of execution than vague goal-setting ever can.
Doerr carried that insight to Google in 1999, introduced OKRs to Larry Page and Sergey Brin in a conference room presentation, and the framework has been at the centre of Google’s operating model ever since. The book is Doerr’s attempt to share what he’s watched OKRs do across four decades and dozens of organisations — from Intel and Google to Bono’s ONE Campaign and the Gates Foundation.
The lineage matters because it establishes that OKRs aren’t a management consulting invention or a Silicon Valley trend. They’re a battle-tested operating discipline with roots in one of the most demanding execution environments the technology industry has ever produced.
What an OKR Actually Is
The structure is straightforward. An Objective answers the question: what are we trying to achieve? It should be qualitative, inspirational, and time-bound — the kind of goal that tells everyone why the work matters, not just what it involves.
Key Results answer the question: how will we know we’ve achieved it? They are quantitative, specific, and binary in their honesty — either you hit them or you didn’t. Three to five Key Results per Objective. No more.
The combination does something that neither element does alone. Objectives without Key Results are aspirations — inspiring but unmeasurable, which means they can’t be honestly tracked or honestly evaluated. Key Results without Objectives are metrics — measurable but directionless, which means hitting them doesn’t necessarily mean you’ve moved toward anything that matters.
Together, they create a unit of work that is both meaningful and verifiable. That combination, it turns out, is rarer than it should be.
The Stretch Goal: Why 70% Can Be Success
Here is where OKRs diverge most sharply from conventional goal-setting — and where most organisations get them wrong initially.
Doerr distinguishes between two types of OKRs: committed goals, which are expected to be hit at 100%, and stretch goals, or “moonshots,” which are intentionally set beyond what’s currently achievable. For stretch goals, hitting 70% is considered a success. Missing at 100% suggests the goal wasn’t ambitious enough.
This is counterintuitive for organisations with performance cultures built around hitting targets. If missing a goal is acceptable, doesn’t that reduce accountability? Doerr’s answer — and I find it persuasive — is the opposite. Stretch goals produce a different quality of thinking and effort than achievable ones do. When the objective is just within reach, teams optimise incrementally. When the objective requires a genuine leap, they ask fundamentally different questions about how to get there.
The practical implication: OKR scores should never be directly tied to performance reviews or compensation. The moment people’s bonuses depend on their OKR scores, they stop setting stretch goals and start setting safe ones. The incentive structure would have destroyed the framework’s most valuable feature.
Alignment: The Superpower
Doerr describes alignment as OKRs’ “superpower” — and it’s the dimension that most justifies the investment in implementing them properly.
In most organisations, goal-setting is a parallel process. Leadership sets company goals. Departments set their own goals, loosely connected to the company ones. Teams set their goals, loosely connected to the department ones. By the time you get to individual contributors, the line of sight between their daily work and the company’s strategic priorities has usually become too faint to navigate by.
OKRs, when implemented well, make that line of sight explicit at every level. Company OKRs are public. Department OKRs are nested within them. Team OKRs connect to department OKRs. The result isn’t just that everyone knows what the company is trying to do — it’s that everyone can see how their own work connects to it. That connection is, in my experience, one of the most underrated drivers of engagement and performance in any organisation.
I’ve implemented OKR-style frameworks across multiple teams, and the alignment conversation is always the most valuable one the process generates — not the goal-setting itself, but the moment when teams realise their priorities don’t connect to the organisation’s as cleanly as they assumed.
CFRs: The Human Layer
One of the most important additions in the book — and the one most often missed in summaries — is Doerr’s introduction of CFRs: Conversations, Feedback, and Recognition. He positions CFRs as the human complement to OKRs’ structural discipline.
OKRs tell you what you’re working toward and whether you’re getting there. CFRs are the ongoing dialogue that makes the journey sustainable: regular one-on-ones where progress is discussed honestly, feedback that flows continuously rather than pooling in an annual review, and recognition that connects specific contributions to specific outcomes.
The argument Doerr makes — and it’s backed by Google’s own research on what makes teams effective — is that the measurement framework and the human framework have to coexist. OKRs without CFRs become mechanical and demoralising. CFRs without OKRs become pleasant but directionless. Together, they create the conditions where people know what they’re working toward, know how they’re doing, and feel that their contribution is seen.
What This Book Changed for Me
I’ve used OKR-adjacent frameworks throughout my leadership career, but reading Measure What Matters sharpened two things specifically.
The first is the discipline of the Key Result. It’s surprisingly easy to write Key Results that sound measurable but aren’t — outcomes that could be claimed as achieved or not depending on how generously you interpret them. Genuine Key Results are uncomfortable in their specificity. They remove the wiggle room. And that discomfort, I’ve found, is exactly where the value lives.
The second is the transparency principle. Making OKRs visible across the organisation is a cultural act as much as a management one. It signals that the organisation trusts its people with strategic context, believes alignment matters more than information control, and is willing to be held publicly accountable for what it said it was going to do.
That’s a harder commitment than it sounds. But the organisations that make it tend to build something different — and something better.
In your organisation, if you asked every team member today what the company’s top three priorities are — how consistent would the answers be? And what would you do with that information?
Let’s keep learning — together.
harish.balasubramanian 
Share your thoughts