Building the Company

Measure What Matters

How Google, Bono, and the Gates Foundation Rock the World with OKRs

John Doerr · 2018 · Portfolio/Penguin

A practical case for OKRs: a simple goal system that turns a founder's priorities into numbers the whole team can grade.

The big idea

What the book argues

Doerr argues that most organizations fail at execution, not ideas, and that a lightweight discipline called Objectives and Key Results fixes much of that. An objective states what matters; a few measurable key results define what done looks like by a date. Kept few in number, made public across the company, checked weekly and graded honestly at the end of each cycle, OKRs create focus and alignment. Paired with frequent conversations and feedback instead of annual reviews, they keep people stretching without gaming the score.

3-5
Objectives per cycle, each with about three to five key results
0.7
Typical success score on aspirational goals at Google
0-1.0
Grading scale for each key result at cycle end

Key takeaways

7 ideas worth keeping

1

An objective says what; key results prove it

Each OKR pairs one objective, which should be significant and concrete, with roughly three to five key results that are specific, time-bound and checkable. A key result is either hit or missed; there is no room to argue about it. If you cannot tell at the end of the quarter whether it happened, it is an activity or a hope, not a key result.

Illustration: Doerr recounts Google Chrome's early goal of a set number of seven-day active users by year end: a count and a date, not 'improve adoption.'
2

Fewer goals per cycle produce more results

Doerr credits Andy Grove at Intel with the discipline of focus: a short list of objectives each cycle, chosen as much for what they leave out as what they include. When a company lists ten priorities, it effectively has none. The hard part of goal setting is the cutting, and the founder has to own it.

Illustration: Intel's Operation Crush, around 1980, rallied the company against Motorola's competing chip; the campaign helped win the processor slot in IBM's first PC.
3

Make goals public so teams align themselves

OKRs work best when everyone, including the CEO, can see everyone else's. Rather than cascading goals rigidly down the org chart, Doerr recommends that a large share be proposed by teams themselves and linked to company objectives. Transparency exposes duplicated work and hidden dependencies early, and lets people connect their own work to the company's direction.

4

Track weekly, grade honestly, then reflect

OKRs are not set-and-forget. Teams check progress during the cycle, update status, and change or drop key results that no longer make sense. At the end, each key result gets a score from 0 to 1.0 and a short written reflection on what was learned. The value is in honest scoring, not precise scoring.

5

Label every goal as committed or aspirational

Committed OKRs, such as revenue, hiring or delivery promises, are expected to land in full, and a miss needs an explanation. Aspirational OKRs are deliberately ambitious, and at Google a score around 0.7 on them counts as success. Mixing the two without labels either demoralizes people or teaches them to set goals they know they can beat.

Illustration: A team scoring 1.0 on every stretch goal every quarter is probably setting goals too low.
6

Keep OKRs separate from pay; add CFRs

If bonuses ride directly on OKR scores, people quietly lower their targets. Doerr recommends decoupling the two and pairing OKRs with CFRs: ongoing conversations between manager and report, two-way feedback, and recognition. He describes companies such as Adobe replacing annual reviews with regular check-ins anchored to goals.

7

Graded goals are a strong investor update

Doerr introduced OKRs to Google when it was still a small startup, shortly after his firm invested. For founders the lesson is that investors back execution. A monthly update that shows committed results hit, stretch results partly hit, and why, builds more confidence than adjectives about momentum.

Illustration: Update line: 'Committed key results 3 of 3 met. Stretch goal: 0.6, because enterprise pilots slipped a month; here is the fix.'

The framework

The OKR cycle

01

Focus

Pick three to five objectives for the cycle; write down what you are deliberately not doing.

02

Define key results

Give each objective three to five measurable, dated results that are clearly hit or missed.

03

Align in the open

Publish every OKR company-wide; let teams propose many of their own and link them up.

04

Track weekly

Review progress in short check-ins; flag what is off track and adjust or drop stale results.

05

Grade and reflect

Score each key result 0 to 1.0, write what you learned, and feed it into the next cycle.

“Ideas are easy. Execution is everything.”

— John Doerr

Apply it this week

Three moves to make now

  1. Write one objective for the next 90 days and three measurable key results, each with a number and a date. Leave every other goal off the list.
  2. Mark each key result committed or aspirational, and set a 15-minute weekly check-in to update its status.
  3. At quarter end, score each key result from 0 to 1.0, write two lines on what you learned, and share the scores with your team and investors.

Read next

Pairs well with

This page is an original summary and commentary prepared by XRAYCLOUD.AI with AI assistance. It is not affiliated with or endorsed by the author or publisher, and it is no substitute for the book — read it for the full argument.