Measure What Matters

by John Doerr
A Chapter-by-Chapter Summary
Condensed to preserve the author’s structure, logic chain, and emotional arc.

About John Doerr

John Doerr was born in 1951 in St. Louis, Missouri, the middle of five children in a middle-class family. His father worked in manufacturing and modeled an entrepreneurial restlessness that Doerr absorbed early. He excelled in science and mathematics through school, then earned dual degrees in electrical engineering from Rice University in Houston — where he also met the woman he would later marry, Ann Howland. He went on to Harvard Business School, graduating in 1976 with an MBA and a desire to start something of his own.

The starting-something came sooner than expected. Doerr moved to Silicon Valley not for a job but to find Ann, who was already working there. He joined Intel in 1974 — a stroke of personal luck that turned into professional destiny. Andy Grove, Intel’s legendary CEO, ran the company as a laboratory of management thinking, and Doerr absorbed it all. He worked as an engineer and one of Intel’s most effective salespeople, held patents in memory devices, and watched Grove build a system of goal-setting — Objectives and Key Results — that was quietly transforming how the company operated. That system would follow Doerr for the rest of his life.

In 1980, Kleiner Perkins came calling with an offer to join as a venture capitalist. Grove warned him off the idea. “Venture capital, that’s not a real job,” he said. “It’s like being a real estate agent.” Doerr joined anyway. Over the next four decades at Kleiner Perkins — eventually rising to chairman — he became one of the most consequential investors in the history of Silicon Valley: early backer of Compaq, Netscape, Intuit, Amazon, and Google. When two graduate students named Page and Brin told him Google might generate ten billion dollars in revenue, he wrote the largest check Kleiner Perkins had ever cut. He introduced OKRs to Google’s founders in 1999 with a twenty-minute PowerPoint presentation. It was, as Larry Page later wrote, the start of something that would help lead the company to 10x growth, many times over.

Measure What Matters, published in 2018, was Doerr’s attempt to package what he had seen and done across fifty companies over four decades. It is part case study collection, part management manual, and part memoir. The book made the New York Times bestseller list and is now required reading at companies and business schools around the world. Beyond the book, Doerr has channeled his fortune and influence toward causes he believes in: climate, education, and global poverty. In 2022, he and Ann donated $1.1 billion to Stanford University to establish its first new school in 70 years — the Stanford Doerr School of Sustainability. He sits on the boards of Alphabet and the Obama Foundation, among others. He has signed the Giving Pledge.

Doerr’s genius is that of a translator. He did not invent OKRs — Andy Grove did. He did not build Google — Page and Brin did. What he did was see clearly how a single idea about goal-setting could travel from a chip company in Santa Clara to every corner of the modern organization, and then spend his career proving it.

Table of Contents

Foreword by Larry Page
Preface
PART ONE: OKRs in Action
1. Google, Meet OKRs
2. The Father of OKRs
3. Operation Crush: An Intel Story
4. Superpower #1: Focus and Commit to Priorities
5. Focus: The Remind Story
6. Commit: The Nuna Story
7. Superpower #2: Align and Connect for Teamwork
8. Align: The MyFitnessPal Story
9. Connect: The Intuit Story
10. Superpower #3: Track for Accountability
11. Track: The Gates Foundation Story
12. Superpower #4: Stretch for Amazing
13. Stretch: The Google Chrome Story
14. Stretch: The YouTube Story

PART TWO: The New World of Work
15. Continuous Performance Management: OKRs and CFRs
16. Ditching Annual Performance Reviews: The Adobe Story
17. Baking Better Every Day: The Zume Pizza Story
18. Culture
19. Culture Change: The Lumeris Story
20. Culture Change: Bono’s ONE Campaign Story
21. The Goals to Come

Foreword by Larry Page

[context and credibility]

Doerr arrives at Google in 1999 with a deck of twenty slides and an idea he calls Objectives and Key Results. The company has fewer than forty employees. It is making almost no money. Page is not particularly interested in management frameworks — few founders are. But he sits through the presentation, and something sticks.

[testimony]

Page opens the book with a short endorsement that carries more weight than most. He writes that OKRs helped Google to 10x growth, many times over. He does not say this with the enthusiasm of a man recounting an inspirational story. He says it the way an engineer reports a result: it worked, the data confirms it, here is the outcome.

[invitation]

His note is brief, but its function in the book is clear. It gives the reader permission to believe. If OKRs were good enough to help build the world’s most valuable company, they are probably worth understanding.

Preface

[origin story]

Doerr opens with the summer of 1975. He is a young engineer, recently graduated, chasing a woman and a job in Silicon Valley. Both are at Intel. The woman is Ann Howland, who later becomes his wife. The job delivers something more lasting: Andy Grove.

[the teacher]

Grove runs Intel’s internal management training like a university course. He is precise, demanding, and philosophically serious about how organizations work. In one of those sessions, he introduces a goal-setting method he has borrowed and refined from Peter Drucker’s management-by-objectives framework. Grove’s version is cleaner, harder, more honest. He calls the targets Objectives and the benchmarks Key Results. Together: OKRs.

[the thesis]

Doerr carries the idea with him when he leaves for venture capital in 1980. Over the next four decades, he introduces OKRs to more than fifty companies. Some implement them halfheartedly and see modest results. Those that adopt them fully — Google chief among them — achieve things that no one predicted. The preface is Doerr’s argument that the difference between organizational success and organizational drift is often not strategy, not talent, not funding. It is the ability to decide what matters and to measure whether you are getting there.

[scope]

This book, he writes, is his attempt to share what he has seen. It is built on case studies — first-person accounts from the CEOs, founders, and operators who lived the stories — alongside his own framework and commentary. The goal is not to produce a theory of management. The goal is to give the reader a working system they can use tomorrow morning.

Part One: OKRs in Action

Chapter 1: Google, Meet OKRs

[scene setting]

Late 1999. Google has a product that works and a team that is growing faster than anyone can manage. Larry Page and Sergey Brin are brilliant engineers who have not yet decided what kind of company they are building. A mutual friend arranges for Doerr to present to the team. He has twenty slides and twenty minutes.

[the framework, stated plainly]

An Objective is what you want to achieve. It should be significant, concrete, action-oriented, and if possible, inspirational. A Key Result is how you measure whether you got there. Key Results are specific, time-bound, and verifiable. You either hit them or you don’t. There is no partial credit. Objectives point to the horizon; Key Results tell you how far you’ve walked.

[the example]

Doerr uses a hypothetical to demonstrate. Objective: Win the Indy 500. Key Results: Hire a crew chief with at least two wins, secure a top-tier engine contract by March, test the car at three tracks before qualifying. You can see immediately what the system does. It forces the aspiration down into specifics. It converts intention into action.

[early adoption]

Google’s founders are not immediately converted. But they agree to try it for one quarter. That trial never really ends. OKRs become part of Google’s operating system, used quarterly by every employee from intern to CEO, public to the entire company, graded without shame and without consequence to compensation. They are a tool, not a weapon.

OKRs answer two questions every organization must ask: What do we want to achieve? And how will we know when we’ve achieved it? Without both, ambition is just noise.

Chapter 2: The Father of OKRs

[portrait of Andy Grove]

Andrew Grove was born Andras Grof in Budapest in 1936, survived both Nazi occupation and Soviet communism, and arrived in America at twenty as a refugee who spoke almost no English. By the time he ran Intel, he was one of the most rigorous management thinkers in the history of American business. Grove believed that what separated good organizations from mediocre ones was not the quality of their ideas but the quality of their execution. OKRs were his mechanism for closing that gap.

[the intellectual foundation]

Grove built on Peter Drucker’s Management by Objectives but stripped away its weaknesses. Drucker’s MBOs were annual, hierarchical, and often secret. Grove’s OKRs were quarterly, transparent, and set collaboratively. He observed that knowledge workers could not be managed like factory workers — you could not see their output the way you could see a machined part. The only honest way to manage them was to agree on what success looked like, then let them find their own path to it.

[the ground rules]

Grove articulated six operating principles that Doerr carries through the entire book. Less is more — a few well-chosen OKRs signal what you’re really saying yes to. Set goals from the bottom up — roughly half of every team’s OKRs should originate with the people doing the work. No dictating — OKRs are a social contract, not a mandate. Stay flexible — a goal that no longer serves the mission should be dropped, not defended. Dare to fail — aspirational OKRs should be uncomfortable, even unattainable. And treat OKRs as a tool, not a weapon — never tie them directly to compensation, or people will stop taking risks.

[the legacy]

Grove died in 2016. But the system he created now runs in thousands of organizations across every sector of the economy. Doerr’s debt to him is explicit and unashamed. The book is, in many ways, an extended act of gratitude.

OKRs are Andy Grove’s answer to a simple problem: smart people, working hard, in the wrong direction. The system does not replace leadership — it gives leadership somewhere to go.

Chapter 3: Operation Crush — An Intel Story

[crisis]

In 1980, Motorola launches a microprocessor that threatens to displace Intel’s 8086 chip as the industry standard. The threat is existential. If OEMs commit to Motorola, Intel loses the market it has spent a decade building. Grove’s response is to deploy OKRs not as a planning tool but as a battle plan.

[execution]

Operation Crush is a company-wide offensive with a single objective: make the Intel 8086 the industry’s dominant microprocessor. Every department sets its own Key Results in support of that objective — engineering, marketing, sales, manufacturing. The OKRs cascade through the company in weeks, not months. Four weeks after the crisis is identified, Intel has a coordinated response across a near-billion-dollar company.

[result]

IBM, the most important OEM in the market, chooses the Intel chip over Motorola’s. The decision shapes the next twenty years of computing history. Doerr uses this chapter not to brag about Intel but to demonstrate what OKRs do in conditions of urgency: they compress the time between a decision and aligned action.

OKRs do not just help organizations move faster. They help them move together — which is often more valuable than speed alone.

Chapter 4: Superpower #1 — Focus and Commit to Priorities

[the core argument]

The most important thing a leader does with OKRs is not write them — it is decide which ones not to write. Doerr’s first superpower is focus: the deliberate act of choosing three to five objectives per cycle, no more, and resisting every reasonable argument for adding a sixth. The things you say no to define you as much as the things you say yes to.

[clarity]

Focus requires transparency. For OKRs to focus an organization, they must be visible to everyone in it. When top-line goals are clear and public, every team and individual can orient their own work toward them. When goals are private or vague, alignment is impossible — people optimize for what they can see, which is usually their own inbox.

[dual cadence]

Doerr recommends running OKRs on two timescales simultaneously: annual objectives for strategic direction and quarterly OKRs for the work that actually gets done. The quarterly cycle creates urgency. It compresses the feedback loop. A deadline six weeks away is real in a way that a deadline twelve months away is not.

[pairing key results]

A technical point that matters in practice: Key Results should come in pairs — one measuring output, one measuring quality. An objective to hire fifty engineers must be paired with a Key Result measuring interview satisfaction or first-year retention, or the organization will hit the number by lowering the bar. Quantity without quality is not progress.

Focus is not a natural state for organizations — it is a discipline. The OKR cycle forces that discipline every quarter, making it structural rather than aspirational.

Chapter 5: Focus — The Remind Story

[company portrait]

Brett Kopf and his brother Brian build Remind, a platform that lets teachers communicate safely with students and parents outside school hours. The product solves a real problem — teachers were using their personal cell numbers; parents were texting at midnight — but the company keeps drifting. Every new feature request feels important. Every partnership seems strategic. The team is busy but not building.

[the intervention]

Doerr invests and introduces OKRs. Kopf starts printing his quarterly objectives on paper and keeping them at his desk. Three to four objectives, nothing more. When someone brings a new idea — a new feature, a new market, a new partner — the filter is simple: does this support one of the current OKRs? If not, it waits.

[the outcome]

Remind grows to serve millions of teachers and students across the US. Kopf credits the OKR discipline with the difference between building a product and building a company. The framework did not generate the ideas. It protected the team from their own best intentions.

A startup with too many priorities has no priority. OKRs give founders permission to say no — and a structure that makes saying no defensible to everyone in the room.

Chapter 6: Commit — The Nuna Story

[the organization]

Jini Kim co-founds Nuna, a healthcare data platform built on Medicaid data, serving government payers who desperately need analytics but have almost no modern infrastructure. The company operates in a sector where the stakes are high, the margins are thin, and trust is everything.

[the learning curve]

Kim’s first OKRs are too aspirational, too vague, too difficult to grade at the end of the quarter. She learns through iteration: objectives need to be specific enough that everyone on the team, without further explanation, knows what they are working toward. Key Results need to be measurable enough that grading them at the end of the quarter requires judgment, not interpretation.

[the leadership lesson]

The chapter’s main argument is about commitment from the top. OKRs only work if the leadership team uses them visibly and takes them seriously. If executives set OKRs and then ignore them for three months, contributors notice. The system collapses. Kim installs OKRs at every level of Nuna and holds herself to the same standard she holds her team.

OKRs cannot be delegated to contributors while leaders operate above them. The system earns credibility from the top down, or it earns nothing at all.

Chapter 7: Superpower #2 — Align and Connect for Teamwork

[the problem of silos]

Most organizations are secretly tribal. Each department optimizes for its own goals — engineering wants clean code, sales wants to close deals, marketing wants brand recognition — and the gaps between them cost more than any individual department’s inefficiency. Doerr’s second superpower is alignment: using OKRs to connect the work of every team and individual to the organization’s top-line goals.

[the cascade, used wisely]

The conventional image of OKR alignment is a cascade: company objectives become departmental Key Results, which become team objectives, which become individual targets. This works in moderation. But when taken too literally, it becomes mechanical — a color-by-numbers exercise that produces compliance without ownership. The healthiest organizations cascade company-level objectives while inviting teams to set their own Key Results in response.

[horizontal alignment]

OKRs also create alignment across teams, not just up and down the hierarchy. When every team’s OKRs are public, engineers can see what marketing is trying to do. Sales can see what product is building. The visibility alone reduces the coordination tax that consumes so much organizational energy.

[bottom-up contribution]

Research shows that employees who set some of their own goals are more committed to hitting them. Doerr’s recommendation: roughly half of every team’s OKRs should originate with the people doing the work, not just be handed down. The leader’s job is to set the destination; the team’s job is to find the road.

Alignment is not agreement — it is shared direction. OKRs create alignment not by telling people what to do, but by making visible what everyone is trying to accomplish.

Chapter 8: Align — The MyFitnessPal Story

[the scale problem]

Mike Lee and his brother Albert build MyFitnessPal into one of the world’s largest fitness tracking platforms, eventually reaching 80 million users. At that scale, alignment between engineering, product, design, and marketing is not a nice-to-have — it is the difference between shipping and spinning.

[OKRs as connective tissue]

The Lee brothers use OKRs to keep teams pointed in the same direction without requiring constant coordination meetings. When each team’s objectives are public and tied to company-level goals, the need for top-down coordination decreases. Teams can see each other’s priorities and route around conflicts without escalating to leadership.

[the commitment choice]

Unlike Google, which separates committed from aspirational OKRs, MyFitnessPal treats all OKRs as committed — difficult but achievable in full. This approach has a clarity advantage: there is no ambiguity about whether a 0.7 score is acceptable. The tradeoff is that it may discourage the kind of moon-shot thinking that stretch goals are designed to produce.

There is no single right way to structure OKRs. The right structure is the one that the team understands, that leadership models, and that drives the behavior you actually want.

Chapter 9: Connect — The Intuit Story

[the organization]

Intuit, maker of TurboTax and QuickBooks, is a company that has survived and thrived through multiple platform transitions: from desktop software to web to mobile. That survival required the ability to constantly reprioritize and align thousands of employees around changing goals. Scott Cook, Intuit’s co-founder, becomes an early believer in OKRs.

[radical transparency]

Intuit’s approach to OKRs emphasizes what Doerr calls network transparency: making goals visible not just within teams but across the entire organization, and providing technology tools that make it easy to see how any individual’s work connects to the company’s top-line priorities. Studies consistently show that employees with clear line-of-sight to company goals are more than twice as likely to be top performers.

[preventing silos]

The Intuit chapter’s central lesson is about what public OKRs do to organizational culture. When goals are visible, secrecy becomes harder to sustain. When teams can see each other’s priorities, coordination becomes a design problem rather than a political one. The system does not eliminate silos — but it makes them more expensive to maintain.

Transparency is not a value — it is a mechanism. Public OKRs make organizational behavior visible, and visibility is the first step toward accountability.

Chapter 10: Superpower #3 — Track for Accountability

[OKRs as living documents]

OKRs are not a planning artifact. They are not something you write in January and review in December. They are living commitments that require attention throughout the cycle — weekly check-ins, mid-cycle reviews, end-of-cycle grading, and a retrospective that informs the next round. Without this infrastructure, OKRs become wallpaper: visible, meaningless, and slightly depressing.

[the traffic light system]

Google grades OKRs on a 0-to-1 scale. A score of 0.7 to 1.0 is green — the work was delivered. A score of 0.4 to 0.6 is yellow — progress was made but the goal was not reached. A score below 0.4 is red — something went wrong. The system is explicit that a consistent green score on aspirational OKRs is actually a bad sign: it means the goals were not ambitious enough.

[the four options mid-cycle]

At any point during a cycle, a team has four choices about an OKR. Continue, if the goal is on track. Update, if circumstances have changed and the Key Result needs revision. Start, if a new priority has emerged that deserves its own OKR. Stop, if a goal has become irrelevant and continuing to chase it would waste resources. The system is designed to be adaptive, not rigid.

[reflection as discipline]

Doerr closes this chapter with a practice most organizations skip: the retrospective. At the end of each cycle, teams should ask four questions. Did we accomplish the objective? If yes, what made it possible? If no, what got in the way? What would we change about the goal itself? What does this teach us about next quarter? The retrospective converts outcomes into learning.

An OKR that is set but not tracked is a wish. The tracking infrastructure — check-ins, mid-cycle reviews, scoring, retrospectives — is what converts intention into execution.

Chapter 11: Track — The Gates Foundation Story

[the mission]

The Bill and Melinda Gates Foundation operates at a scale and with a mission that makes goal-setting both more critical and more difficult than in any for-profit company. The foundation’s objectives — eradicating diseases, improving education outcomes, reducing poverty — cannot be accomplished in a quarter. They can barely be measured in a decade.

[the OKR adaptation]

The foundation adapts OKRs to long-cycle work by setting ambitious multi-year objectives and then creating annual and quarterly Key Results that function as milestones. The question at each review is not whether the disease is eradicated yet but whether the work is on track: Are vaccination rates improving? Are the clinical trials progressing? Is the funding reaching the intended populations?

[accountability in philanthropy]

The chapter makes an implicit argument that accountability matters even more in nonprofit work than in business. In business, markets provide feedback — bad products don’t sell. In philanthropy, there is no market signal. If a program is failing, the failure can go invisible for years unless there are explicit Key Results that expose it. OKRs provide that exposure.

In mission-driven work, the absence of market feedback makes rigorous goal-setting more important, not less. OKRs give nonprofits the accountability mechanism that business gets from revenue.

Chapter 12: Superpower #4 — Stretch for Amazing

[the argument for discomfort]

A goal you are certain you will hit is not a goal — it is a budget. Doerr’s fourth superpower is the stretch goal: an objective set at a level that is genuinely uncertain, possibly unattainable, and almost certainly uncomfortable. The logic is simple. Organizations that aim at what seems possible arrive at what seems possible. Organizations that aim at what seems impossible sometimes get there — and almost always end up somewhere better than they would have otherwise.

[two baskets]

Google distinguishes between committed OKRs — targets tied to operational needs, expected to be hit at 100% — and aspirational OKRs, which are expected to be reached only 60-70% of the time. The distinction matters because it frees teams to set audacious goals without fearing that falling short will damage their performance review. Failure on a stretch goal is not failure. It is information.

[the psychology of stretch]

Andy Grove’s observation: output tends to be greater when people strive for a level of achievement beyond their immediate grasp. This is not motivational theory — it is an empirical regularity. Teams that aim for 100% of an ambitious goal outperform teams that aim for 100% of a modest one, even when the ambitious team falls short.

[the celebration problem]

Grove captured the challenge: after ten milliseconds of celebration, you have to set another impossible objective and find a way to meet that one too. Stretch goals require a culture that can treat achievement as a starting point rather than a destination — and that culture has to come from the top.

Set goals that make you uncomfortable. The aspiration has to be large enough that missing it by 30% still counts as extraordinary progress.

Chapter 13: Stretch — The Google Chrome Story

[the bet]

In 2008, Google has a problem that most companies would envy: too many people using the internet through browsers that are slow, crash-prone, and designed for a world before web applications. Building a browser is not a core Google competency. It is expensive, competitive, and risky. The case against building Chrome is straightforward.

[the OKR]

Sundar Pichai, then VP of Product, sets an aspirational OKR: ship a browser by a specific date, hit a specific user adoption target. The number they choose is the kind that engineers look at and quietly doubt. Pichai’s point is not that the number is guaranteed — it is that the number is honest about what success requires. Comfortable targets do not attract the best engineers or produce the best work.

[the outcome]

Chrome ships. It grows. Within a few years it becomes the world’s most widely used browser. The chapter is not really about Chrome — it is about what happens when leadership is willing to set a goal that might fail and commit to it publicly anyway. Courage, Pichai says, is required to write an OKR that might well fail. But there is no other way to be great.

Stretch goals require public commitment. A target you keep to yourself is easy to quietly abandon. A target written into the company OKRs requires a different kind of resolve.

Chapter 14: Stretch — The YouTube Story

[the impossible number]

In 2012, YouTube’s leadership sets an aspirational OKR: one billion hours of daily watch time. At the time, YouTube’s daily watch time is roughly 100 million hours. The goal is not 10% improvement. It is 10x. By any conventional planning standard, it is absurd.

[the engineering challenge]

Cristos Goodrow, the engineering lead on the project, notes that engineers resist stretch goals for two reasons: they hate crossing lines they might not reach, and they worry that ambitious numbers will corrupt the metrics that guide product decisions. Both concerns are legitimate. The answer to the first is cultural — you have to make it safe to miss a stretch goal. The answer to the second is structural — pair the stretch metric with quality metrics that prevent gaming.

[the result]

YouTube reaches one billion daily watch hours in 2016, ahead of schedule. The chapter’s lesson is not that stretch goals always work. It is that the discipline of setting them — the process of asking what amazing would look like, then building a plan to get there — produces different decisions and different outcomes than planning from the safe baseline.

The question is not whether the stretch goal is achievable. The question is whether aiming for it will produce better work than aiming for something comfortable. It almost always does.

Part Two: The New World of Work

Chapter 15: Continuous Performance Management — OKRs and CFRs

[the problem with annual reviews]

Most organizations still evaluate their people once a year. The feedback arrives months after the relevant behavior. The format is a negotiation between the employee’s self-assessment and the manager’s memory of events they barely recall. The outcome rarely changes anything. Research confirms what managers already know: annual reviews are expensive, disliked by everyone involved, and largely ineffective at improving performance.

[the CFR alternative]

Doerr introduces a second acronym: CFRs. Conversations — regular, structured, one-on-one exchanges between manager and contributor aimed at reviewing progress, removing obstacles, and developing the person. Feedback — the continuous flow of assessments, both formal and informal, that give people real-time information about how their work is landing. Recognition — expressions of appreciation, specific and sincere, for contributions of every size. CFRs are designed to run alongside OKRs, providing the human infrastructure that goal-setting alone cannot supply.

[the rhythm]

CFRs are not additional meetings. They replace the annual review with more frequent, lighter-weight interactions that are harder to avoid and more useful when they happen. A manager who speaks honestly with each of their reports every week — about OKR progress, about obstacles, about growth — knows more about their team’s state than any annual performance document could capture.

OKRs tell you what to do. CFRs help people do it. The system only works if both are running — goals without conversation are just numbers, and conversation without goals is just talk.

Chapter 16: Ditching Annual Performance Reviews — The Adobe Story

[the decision]

In 2012, Donna Morris, Adobe’s executive vice president of people and places, eliminates the company’s annual performance review system. This is not a small decision. Annual reviews are embedded in every HR process: compensation, promotion, performance improvement plans. Removing them requires rebuilding all of those processes from scratch.

[check-ins]

Adobe replaces the annual review with a system of quarterly check-ins — structured conversations between managers and contributors that focus on expectations, feedback, and growth. The conversations are not rated. They are not documented in a formal system. They are simply held. Regularly. The absence of a form or a rating forces the conversation to be real rather than bureaucratic.

[the result]

Adobe sees significant improvements in employee satisfaction and retention. Voluntary attrition declines. Manager effectiveness scores improve. The company estimates that eliminating the review cycle saves the equivalent of 80,000 hours of manager time per year — time that is reinvested in the check-in conversations that actually change behavior.

Annual performance reviews are a proxy for the conversations organizations are not having throughout the year. Replace the proxy with the real thing.

Chapter 17: Baking Better Every Day — The Zume Pizza Story

[the company]

Zume Pizza is a West Coast startup that automates pizza production and delivery with a combination of robotics and custom-built delivery trucks that bake pizzas en route to the customer. It is a company with genuine technical innovation and genuine operational complexity — the kind of startup where priorities shift weekly and coordination failures are expensive.

[OKRs as training tools]

Zume’s experience with OKRs produces an unexpected benefit: the process of setting quarterly objectives turns out to be one of the most effective development tools for managers. Writing a good OKR requires a manager to think clearly about what their team is actually responsible for producing, what success looks like in measurable terms, and how their work connects to the company’s goals. Managers who do this consistently become significantly better at the rest of their jobs.

[CFRs in practice]

Zume implements CFRs alongside OKRs and finds that the combination produces a feedback culture that would have been impossible to mandate from above. When managers hold regular check-in conversations, they surface problems faster. When feedback flows continuously, performance corrections happen in weeks rather than quarters. The system turns goal-setting into an ongoing conversation about the work, not an annual documentation exercise.

OKRs are a management training program hidden inside a goal-setting framework. The discipline of writing them clearly is the discipline of thinking clearly about what you are responsible for.

Chapter 18: Culture

[the relationship between OKRs and culture]

Doerr argues that OKRs and culture are not independent. They are mutually reinforcing — or mutually undermining. An organization with strong values but no OKRs has a mission it cannot execute. An organization with rigorous OKRs but weak values has execution without purpose. The companies that achieve extraordinary results combine both: clear goals grounded in a culture that gives those goals meaning.

[how OKRs shape culture]

Public OKRs signal what the organization actually values, as opposed to what it says it values. If the company’s stated value is customer obsession but the top-line OKRs focus exclusively on revenue, the contradiction is visible to every employee. OKRs make culture concrete. They turn values into behaviors and behaviors into outcomes.

[the limits]

Culture cannot be installed with a management system. OKRs can support a healthy culture, but they cannot replace one. An organization with a fundamentally broken culture — one where fear suppresses honesty, where politics override merit, where leaders do not model what they ask of their teams — will corrupt OKRs the way it corrupts everything else. The system only surfaces what is already there.

OKRs reveal culture as much as they shape it. What an organization chooses to measure is a statement about what it believes matters — and those beliefs are the foundation of culture.

Chapter 19: Culture Change — The Lumeris Story

[the problem]

Lumeris is a healthcare technology company trying to shift how hospitals and health systems get paid — away from fee-for-service and toward value-based care. The shift requires changing the behavior of clinicians, administrators, and insurance companies who have operated under the old system for decades. Cultural inertia of this magnitude is not solved by better software or sharper OKRs.

[the sequence]

Lumeris learns that OKR adoption follows a specific sequence. Leadership has to commit first and visibly. The values of transparency, accountability, and collaboration have to exist at least in embryonic form before OKRs can reinforce them. If the culture punishes honesty about failure — if red scores trigger blame rather than problem-solving — OKRs will produce sandbagging, not stretch.

[the lesson]

The Lumeris story is a cautionary tale about implementation sequence. OKRs are not a culture change program. They are a performance management system that works well inside a culture with certain properties. Installing OKRs before those properties exist does not create them. It surfaces their absence.

Before installing OKRs, ask whether the culture can handle honest failure. If red scores are punished rather than examined, the system will produce dishonest green scores — which are worse than no system at all.

Chapter 20: Culture Change — Bono’s ONE Campaign Story

[the ambition]

Bono co-founds the ONE Campaign, a global advocacy organization focused on eliminating extreme poverty and preventable disease in Africa. The ambition is enormous by design — Bono has always thought in terms of scale that makes other people uncomfortable. The early versions of ONE sprawl across too many geographies, too many issues, too many campaigns. The organization is burning its people out chasing goals it cannot measure.

[the OKR intervention]

ONE’s encounter with OKRs produces an immediate diagnosis: the objectives are so large and so numerous that no one can know whether they are making progress. Advocacy is hard to measure — you cannot always draw a straight line from a lobbying campaign to a policy change. But the impossibility of perfect measurement is not a reason to measure nothing. ONE begins setting quarterly OKRs that focus on leading indicators: meetings secured, bills advanced, media coverage generated, governments engaged.

[the insight]

Bono’s reflection on the experience is worth quoting as a principle: they never thought small, the stretch was always there, but the goals were so gigantic they stretched too thin and wore people out. OKRs, he says, saved them. They did not shrink the ambition — they structured it. They gave the organization a way to move toward enormous goals through specific, measurable steps.

Mission without measurement is motivation without traction. OKRs do not make big goals smaller — they make them achievable by breaking them into steps that can be tracked.

Chapter 21: The Goals to Come

[the synthesis]

Doerr closes the book where he began it: with the conviction that execution is everything. Ideas are abundant. What is rare is the ability to choose which ideas to pursue, to commit to them publicly, to measure whether the work is producing results, and to adjust when it is not. OKRs are, at their core, a system for making that kind of discipline structural rather than heroic.

[the adaptability argument]

The final chapter resists the temptation to write a rulebook. Doerr has seen OKRs work in startups with five people and foundations with billion-dollar budgets. He has seen them adapted for quarterly cycles and multi-year missions. He has seen them used by engineers who love metrics and by artists who hate them. The system is flexible by design. What is not flexible is the underlying logic: define what success looks like, measure whether you are getting there, and be honest about what the measurements say.

[the invitation]

The book ends with a challenge. Every organization has goals. Most of those goals are vague, private, and disconnected from the actual work people do every day. OKRs are the technology for closing that gap. But technology, Doerr reminds us, only matters if it is used. The question he leaves the reader with is not what are your OKRs but what are you willing to commit to in public, measure honestly, and change your behavior to achieve.

OKRs are not a management system. They are a commitment device. The value comes not from writing them but from the discipline of treating them as real — and from having the courage to be honest when the numbers say you fell short.

— End of Summary —