LLM Book Knowledgebase

OKRs: Objectives and Key Results

7 min read

OKRs: Objectives and Key Results

OKRs — Objectives and Key Results — are a goal-setting framework developed at Intel by Andy Grove in the 1970s and popularized globally after John Doerr introduced them to Google in 1999. They represent one of the most widely adopted management systems of the 21st century, used by Google, Intel, LinkedIn, Twitter, Netflix, and thousands of organizations worldwide.

The framework is deceptively simple. An Objective is the answer to “what do we want to achieve?” A Key Result is the answer to “how will we know we’ve achieved it?” Together, they create a precision instrument for translating ambitious vision into measurable, time-bound execution.

The Core Structure

“An OBJECTIVE, I explained, is simply WHAT is to be achieved, no more and no less. By definition, objectives are significant, concrete, action oriented, and (ideally) inspirational. When properly designed and deployed, they’re a vaccine against fuzzy thinking—and fuzzy execution.” — Measure What Matters

“KEY RESULTS benchmark and monitor HOW we get to the objective. Effective KRs are specific and time-bound, aggressive yet realistic. Most of all, they are measurable and verifiable.” — Measure What Matters

The relationship between Objectives and Key Results is structural: if all Key Results are achieved, the Objective is necessarily achieved. If that relationship doesn’t hold — if you can score 1.0 on every Key Result and still not accomplish the Objective — the OKR was poorly designed.

The limit rule: Most practitioners agree on three to five OKRs per cycle and three to five Key Results per Objective. The logic mirrors 4DX’s focus discipline: when everything is a priority, nothing is.

“Less is more. ‘A few extremely well-chosen objectives,’ Grove wrote, ‘impart a clear message about what we say yes to and what we say no to.‘” — Measure What Matters

The Four Superpowers

Doerr frames OKRs around four organizational superpowers:

Superpower 1 — Focus and Commit to Priorities: OKRs force leaders to make hard choices. By limiting objectives to three to five per cycle, the system creates genuine prioritization rather than the illusion of it. “As Steve Jobs understood, ‘Innovation means saying no to one thousand things.‘”

Superpower 2 — Align and Connect for Teamwork: OKR transparency means every team member can see how their goals connect to company goals. “Research shows that public goals are more likely to be attained than goals held in private. Simply flipping the switch to ‘open’ lifts achievement across the board.” The result is a “team of teams” where anyone can see where collaboration is needed.

Superpower 3 — Track for Accountability: OKRs are living documents, reviewed on a regular cadence rather than set annually and forgotten. Doerr distinguishes between committed OKRs (expected at 100%) and aspirational OKRs (expected at 60-70%). The act of tracking creates accountability without requiring a punitive culture.

Superpower 4 — Stretch for Amazing: Aspirational OKRs — “moonshots” in Google’s parlance — expand what teams believe is possible. At Google, a score of 0.7 on an aspirational OKR is considered success, because the goal was set to be challenging enough that achieving it in full would have required extraordinary luck.

Committed vs. Aspirational OKRs

Google’s most sophisticated OKR insight is the explicit separation of two fundamentally different types of goals:

Committed OKRs are tied to core business metrics — product releases, revenue targets, hiring quotas. They are expected to be achieved in full (1.0). Falling short requires explanation. These are the non-negotiables.

Aspirational OKRs express bigger-picture, higher-risk ambitions. They originate from any tier of the organization and aim to push the frontier. Google explicitly expects to fall short roughly 40% of the time on aspirational OKRs. Failure — at that rate — is built into the system design.

“The way Page sees it, a ten percent improvement means that you’re doing the same thing as everybody else. You probably won’t fail spectacularly, but you are guaranteed not to succeed wildly. That’s why Page expects Googlers to create products and services that are ten times better than the competition.” — Measure What Matters

The critical design choice is being explicit about which type an OKR is. Treating an aspirational OKR as committed creates defensiveness and priority inversion. Treating a committed OKR as aspirational increases the probability of dangerous failure.

The Timing and Cadence

OKRs are most effective at quarterly intervals. Annual cycles are too slow — the world changes, goals become obsolete, and the feedback gap (the time between action and measurable result) is too long to enable learning. Quarterly cadence creates urgency without the artificial compression of monthly cycles.

“A quarterly OKR cadence is best suited to keep pace with today’s fast-changing markets. A three-month horizon curbs procrastination and leads to real performance gains.” — Measure What Matters

The OKR lifecycle has three phases: setting (at the start of the cycle), tracking (continuous check-ins during the cycle), and reflecting (structured retrospective at cycle end). Without frequent status updates, goals become “zombie OKRs” — on-paper whats and hows devoid of life or meaning.

OKRs and the CFR System

Doerr pairs OKRs with a complementary system called CFRs: Conversations, Feedback, and Recognition. OKRs provide structure; CFRs provide the human context in which that structure operates.

The connection to performance management is intentional and counterintuitive: OKR scores should be kept separate from compensation decisions. When OKRs are tied directly to bonuses, people sandbag — they set easily achievable objectives to protect their pay. Separating the two allows aspirational goal-setting to function as intended.

OKR Traps

The framework identifies six common failure modes:

  1. Failing to differentiate committed from aspirational OKRs — creating confusion about what’s required vs. what’s aimed at
  2. Business-as-usual OKRs — writing goals that describe what would happen anyway, not what requires real focus
  3. Timid aspirational OKRs — starting from the current state and asking “what could we do with extra resources?” rather than “what would the ideal world look like?”
  4. Sandbagging — setting goals well within available resources so achievement is guaranteed
  5. Low Value Objectives (“Who cares?” OKRs) — objectives that, even if achieved at 1.0, produce no meaningful outcome
  6. Insufficient Key Results for committed Objectives — writing KRs that are necessary but not collectively sufficient to achieve the Objective

Relationship to Adjacent Frameworks

With 4DX: 4DX’s WIGs and OKRs are structurally similar — both use the “from X to Y by when” finish line format, both separate lag measures (objectives) from lead measures (key results), and both use visible scoreboards and weekly accountability cadences. The key differences: 4DX is more prescriptive about execution mechanics (WIG sessions, scoreboards, lead vs. lag measures as a discipline), while OKRs are more flexible and operate across the full organizational hierarchy with explicit transparency requirements.

With Fix It: Connors and Smith’s Key Results concept in Fix It is closely related — both frameworks argue that accountability requires crystal-clear, measurable results definitions. Without them, “accountability will break down, resulting in lower morale and misaligned work.”

OKRs and Culture Fit

OKRs require a specific cultural substrate to function: psychological safety, transparency, and a tolerance for public failure on aspirational goals. Organizations with punitive accountability cultures — where falling short of a goal is politically dangerous — will find that people systematically sandbag, eliminating the aspirational dimension entirely. OKRs can reinforce existing cultures but cannot transform dysfunctional ones on their own.

Backlinks