John Doerr's Measure What Matters is the playbook behind Google, Intel, and dozens of the world's fastest-growing organizations. Here's what it actually teaches and how you can use it.
In 1974, a young engineer at Intel attended a lecture by the company's legendary CEO, Andy Grove. The engineer was John Doerr. The lecture introduced a simple management framework called OKRs: Objectives and Key Results. Decades later, Doerr would carry that framework to a small startup in a garage in Menlo Park, California. That startup was Google.
Measure What Matters is Doerr's account of what happened next and a practical field guide for anyone who wants to lead with clarity, alignment, and relentless focus on what actually counts.
An OKR pairs two things: an Objective — a clear, inspiring goal — with a set of Key Results, the specific, measurable outcomes that tell you whether you've reached it. Together, they answer two questions every team needs to ask: Where are we going? And how will we know when we get there?
Notice what's missing: vague platitudes, long lists of tasks, and activity metrics. An OKR is not a to-do list. It is a contract with your future self — a declaration of what success actually looks like, made before you begin.
"Ideas are easy. Execution is everything. It takes a team to win."
— John Doerr, Measure What MattersDoerr identifies four disciplines that OKRs uniquely enable — disciplines that separate high-performing organizations from ones that merely intend to perform.
OKRs force a choice. A team that commits to three objectives is choosing not to do seventeen other things.
When OKRs are public and transparent, everyone can see how their work connects to the mission.
Regular check-ins turn OKRs into living tools — not annual reports filed and forgotten.
"Moonshot" OKRs push teams beyond what feels safe. A 70% score on a moonshot beats 100% on a timid goal.
Doerr's book makes a second argument that often gets overlooked: OKRs alone are not enough. They need to be paired with a culture of continuous conversation. He calls this CFR: Conversations, Feedback, and Recognition.
Frequent, authentic one-on-ones between manager and contributor — not performance reviews, but real dialogue about what's working and what isn't.
Bidirectional assessment shared in real time. The best feedback is specific, timely, and given in the spirit of helping — not judging.
Expressing gratitude for contributions of every size — not just for heroic outcomes, but for the daily acts of progress that make outcomes possible.
CFRs are what give OKRs their soul. Metrics without humanity create scorecards, not cultures. The organizations Doerr profiles — Google, Bono's ONE campaign, the Gates Foundation — used both systems together. The numbers tracked direction. The conversations kept people in the room.
The most compelling parts of the book are the case studies: the people and organizations that picked up OKRs and ran with them. Their results speak louder than any management theory.
Doerr is candid about how OKRs fail. The most common mistake is treating them as a top-down reporting tool a way for management to monitor compliance rather than a shared language for navigating toward something meaningful. OKRs imposed from above without dialogue become the thing everyone games rather than the thing everyone believes in.
A second mistake: setting too many. Doerr recommends no more than five objectives per cycle, with three to five key results each. The discomfort of choosing of saying no to nineteen things so you can truly say yes to three is not a bug in the system. It is the system.
Finally, conflating output with outcome. "Ship the feature" is an output. "Increase user activation by 20%" is an outcome. OKRs live in the world of outcomes. If your key results are to-do items in disguise, you haven't written OKRs you've written a project plan and given it a new name.
"If the goal is achieved, did it matter? That's the question OKRs keep asking."
—On the spirit of Doerr's frameworkMeasure What Matters is ultimately a book about clarity, about the courage to name what you actually want, to make it visible to everyone around you, and to hold yourself honestly accountable to whether you got there. OKRs are the mechanism. But the deeper practice is organizational honesty: agreeing, as a team, on what counts.
In a world that measures everything, that can feel radical. But it's exactly what separates the organizations that grow from the ones that only intend to.
"Not everything that can be counted counts,
and not everything that counts can be counted."
but with OKRs, you at least know which is which.