CheckItNEWAI DecodedIndia
Management2018 · 320 pages

Measure What Matters

by John Doerr

4.5

How Google, Bono, and the Gates Foundation rock the world with OKRs.

The short route — our review and key takeaways, 5 min read. The long route — buy the book on Amazon if you want to go deeper. Both routes work.

JD

About the author

John Doerr

OKRsgoalsperformance

The short route

northstar's take on this book

Reviewed by northstar editorial·Updated 18 May 2026

Measure What Matters is the book that took OKRs from a private Intel/Google management practice to a mainstream framework adopted by basically every venture-backed company in the 2018-2024 era. John Doerr — Kleiner Perkins partner, the person who literally taught OKRs to Google in 1999 after learning them from Andy Grove at Intel — wrote it in 2018 as a long-overdue explainer for a framework that had been operating mostly through whisper networks.

Its central contribution is the formalization of OKRs as a goal-setting and operating system: Objectives (qualitative, ambitious, time-bound) paired with Key Results (quantitative, measurable, scorable). The 0.7 'sweet spot' rule (set objectives ambitiously enough that achieving 0.7 of them is success), the cascade vs. alignment distinction, and the public-OKR transparency norm are the operational details most companies got wrong before this book formalized them.

Timing made the book influential. It came out in 2018, mid-cycle in the OKR-adoption boom that started around 2015 when companies like Spotify, LinkedIn, and Twitter publicly attributed parts of their operating discipline to OKRs. By 2018, every Series B+ startup was either using OKRs or trying to, and most were doing them badly. Doerr's book gave that audience a canonical reference document. By 2023, OKRs were probably the single most-adopted management framework in venture-backed tech.

Newsletter

Like this review? Get the next book breakdown in your inbox.

One book or case study every few days — the short route, with the takeaways and our honest read. Free.

Free forever. Unsubscribe anytime. No spam.

The most common misreading by far is treating OKRs as a performance management system. They are not, and Doerr is explicit about this — OKRs are a focus and alignment tool, and tying them directly to compensation breaks the ambition mechanism (people will sandbag KRs to ensure 1.0 scoring rather than aiming for the 0.7 sweet spot). The number of companies that ignored this warning and ended up with bureaucratic, gamed OKR systems is enormous, and most of them blame the framework rather than their implementation.

Its main limitation is the case-study format. Roughly half the book is profile chapters of specific OKR implementations at Google, Intuit, the Gates Foundation, Bono's ONE Campaign, etc. These are fine as illustrations but skew Silicon Valley and large-NGO heavy. Readers looking for a structured how-to manual sometimes find the case-study density frustrating. The actual operating instructions are scattered across the book rather than concentrated in a single methodology chapter.

For Indian companies, OKRs have been adopted broadly but unevenly. The Indian tech industry's promotion-and-compensation culture is often more directly tied to measured outputs than US tech, which makes the 'don't tie OKRs to performance reviews' rule harder to maintain in practice. Many Indian product teams in 2026 are running OKR systems that have gradually drifted into performance scorecards, with the predictable consequences. The book is most useful in India as ammunition for product leaders trying to defend the original framework from HR/compensation creep.

Pair with High Output Management for the underlying management philosophy OKRs are built on (Grove invented them at Intel; Doerr is essentially writing the second edition), and with Empowered for how OKRs interact with product-team autonomy.

Key concepts

  • OKRs (Objectives + Key Results)Objectives are qualitative ambitions (where we want to go). Key Results are 3-5 measurable outcomes that show whether you got there. Together they form a structured goal-setting and alignment system.
  • The 0.7 sweet spotOKRs should be set ambitiously enough that scoring 0.7 (70%) on average is the target — not 1.0. Teams that consistently score 1.0 are sandbagging; teams that score 0.3 are setting unrealistic goals.
  • Public OKRs (transparency norm)Every team's OKRs should be visible to every other team. Public OKRs surface dependencies, enable bottom-up alignment, and prevent the silo-driven misalignment that destroys most strategy execution.
  • CFRs (Conversations, Feedback, Recognition)Doerr's companion to OKRs — the soft-side rhythms of management (frequent 1:1s, continuous feedback, recognition of progress) that make the hard-side goal-setting actually work.
  • Separate from compensationDoerr is explicit: never tie OKRs directly to bonuses or performance reviews. Doing so breaks the ambition mechanism — people will sandbag KRs to ensure 1.0 scoring rather than aiming high and falling short.

Who should read it

CEOs and heads of operations / product / engineering rolling out or repairing an OKR system. Highly applicable for Indian product leaders defending OKR design against HR drift. Less useful for very small teams (under 20 people) where lightweight goal-setting is enough.

Frequently asked

4 questions
Measure What Matters is the book that took OKRs from a private Intel/Google management practice to a mainstream framework adopted by basically every venture-backed company in the 2018-2024 era. John Doerr — Kleiner Perkins partner, the person who literally taught OKRs to Google in 1999 after learning them from Andy Grove at Intel — wrote it in 2018 as a long-overdue explainer for a framework that had been operating mostly through whisper networks.