Measure what matters

About the book

Measure What Matters sets out John Doerr's argument for OKRs, short for objectives and key results. An objective names what an organization wants to achieve; key results are the measurable outcomes that show whether it happened. Doerr treats the method as a discipline for focusing effort and tracking progress openly.

The book draws on companies that adopted OKRs at different stages of growth. It pairs explanation with case material: how goals get set, how they connect across teams, how often progress is reviewed, and what happens when priorities conflict. Doerr also covers stretch goals, transparency, and the difference between committed and aspirational targets.

The subject is management by objectives and organizational effectiveness, which places the book in a long tradition of performance-management writing. Its contribution is the OKR framing and the emphasis on measurable results over activity, written for a general business audience rather than as an academic treatment.

How to read it

Read the book as a practitioner's case. Doerr is advocating a method, and the examples are chosen to show it working. Start with the explanatory sections, then treat the company stories as illustrations to test against your own organization's size, cadence, and appetite for public goal-setting.

The prose is accessible and example-driven, which makes it quick to read but easy to skim past the mechanics. Slow down on how key results are written and reviewed, since vague or unmeasurable results are the usual failure point. Pay attention where Doerr separates OKRs from compensation and from ordinary task lists. Those distinctions carry much of the argument.

Who it suits

Managers, founders, and team leads who need a shared vocabulary for priorities will find the most here, especially those frustrated by goals that never translate into measurable outcomes. Executives considering a performance-management change can use it to frame a pilot. Readers curious about how venture investors think about operating discipline will also get something from the case material.

Reading considerations

The evidence is largely anecdotal and drawn from companies that embraced the method, so success stories read as advocacy rather than proof of cause and effect. Test the framework with a small team before treating it as an organization-wide system, and watch for the gap between adopting OKR language and changing how decisions actually get made.