Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs
Doerr's book is the popular introduction to OKRs — objectives and key results — the goal-setting system Andy Grove developed at Intel and Doerr carried to Google and from there to most of Silicon Valley.
The case studies are the strongest part: Bono, the Gates Foundation, early Google, showing OKRs working in settings where the usual management vocabulary falls apart.
The framework itself is deceptively simple; the book's real value is in the chapters that walk through how teams fail at it, which are more instructive than the success stories.
For product direction it is worth reading even if your organisation uses a different system — the book's diagnostic on goal-setting is portable.
Pair it with Grove's High Output Management (the source text) for the deeper version.
Central argument
Doerr argues that most organisations fail not from lack of ambition but from lack of disciplined goal architecture — and that OKRs solve this by separating the qualitative direction (objectives) from the quantitative proof of progress (key results), forcing alignment between intent and measurement. Drawing on Andy Grove's original system at Intel and its adoption at Google, Doerr contends that OKRs work precisely because they make goals transparent across the organisation, exposing misalignment that hierarchy normally conceals. The deeper claim is that the cadence of OKRs — regular check-ins, scoring, and reset cycles — matters as much as the goal structure itself.
Critique
The book conflates the OKR framework with the specific cultural conditions of the organisations it profiles — Intel under Grove, early Google — where radical transparency and psychological safety already existed; it does not adequately address how OKRs perform in organisations where those preconditions are absent, which is most organisations. Doerr is also a Kleiner Perkins partner who seeded Google, which means the book's primary case study is one in which he is personally invested, a conflict of interest that goes largely unexamined and makes the causal claims about OKRs driving Google's success difficult to disentangle from other factors.
Why it matters for product
For a product leader, the book's most transferable insight is its diagnostic on metric selection: key results must measure outcomes, not output, and teams consistently confuse the two — shipping features versus moving the numbers that actually matter to users. The chapters on failed OKR implementations are directly applicable to the recurring product problem of roadmaps that are locally coherent but strategically incoherent, where each team is busy but the product is not advancing any meaningful objective. The framework also gives CPOs a concrete tool for exposing where engineering, design, and commercial goals are nominally aligned but practically contradictory.