Objectives and Key Results (OKRs)

Definition

An OKR splits a goal into two parts: the Objective is WHAT is to be achieved — significant, concrete, and inspirational; the Key Results benchmark HOW you get to the objective — specific, time-bound, and measurable, so there is no ambiguity about whether they were met. A key result "must be described in terms of outcomes, not activities" — it has to be verifiable, ideally by a number.

In the Book

Doerr traces OKRs to Andy Grove at Intel in the 1970s, who evolved them from Peter Drucker's Management by Objectives (MBO). The book's table contrasts the two directly: MBOs were annual, private and siloed, top-down, tied to compensation, and risk-averse; Intel's OKRs were quarterly, public and transparent, set bottom-up or sideways roughly half the time, mostly divorced from compensation, and aggressive and aspirational. Doerr's own first Intel OKR, written as an intern in 1975, illustrates the shape: Objective — "Demonstrate the 8080's superior performance as compared to the Motorola 6800," with four measurable key results (deliver five benchmarks, develop a demo, develop sales training materials, call on three customers). He posted it on his cubicle wall for anyone to see. Chapter 3 shows the mechanism at scale in Operation Crush, Intel's 1980 campaign to beat Motorola in the 16-bit microprocessor market — top management, sales, marketing, and legal all worked from cascading OKRs bound to one rallying objective.

Why It Matters

Turning a goal into an objective plus a handful of falsifiable key results forces the gap between "we want to succeed" and "we will know by Tuesday whether we're succeeding" to close. It converts intention into something that can be tracked, contested, and graded without relying on a manager's subjective impression — the same discipline that makes any commitment (a strategy, a habit, a research claim) auditable rather than aspirational rhetoric.