The history behind OKR

Most management models feel like they fell from the sky, pre-packaged with an acronym and a workshop template. OKR has an unusually traceable history — and that history explains a lot about why the model looks the way it does.

The problem Andy Grove wanted to solve

In the mid-1970s, Andy Grove at Intel was sitting with a question that was easy to state and hard to answer: how do you measure what a knowledge worker actually delivers, and how do you increase that output?

A goal-setting model already existed — Management by Objectives (MBO), introduced by Peter Drucker back in the 1950s. But Grove saw three weaknesses in it. MBO was set top-down, without employees helping shape the goals. Goals were often tied directly to bonuses, which made people aim low rather than ambitious. And the model was built for industrial production, where output is easy to count — not for engineering work, where value rarely fits into a single number.

Grove coined an idea that became something of OKR's underlying tone: top-down management corrodes motivation. If goals are just orders from above, they never become something you feel ownership over.

The solution he landed on had two parts doing different jobs: a qualitative Objective answering what, and quantitative Key Results proving how. That split — which we'll cover in detail in the next article — wasn't in itself a novel stroke of genius. What made the difference was what Grove deliberately disconnected it from: bonuses, hierarchy, and annual cycles that were too slow for a fast-changing tech company.

The engineer who became the messenger

One of the engineers who learned the system directly from Grove at Intel was John Doerr. Doerr later left Intel to become a venture capitalist at Kleiner Perkins — and brought the model with him wherever he went.

In 1999, Doerr invested nearly $12 million in a small startup with two founders who had enormous technical skill but no real business plan: Larry Page and Sergey Brin. The company was Google. Doerr introduced OKR to them as a way to make hard prioritization calls and keep a growing team aligned around the same direction.

The rest, as they say, is history — but the numbers are still worth mentioning. Google grew from forty employees to more than 70,000, with a market cap that eventually passed $700 billion. OKR has been part of the company's management model the whole way.

Not just a tech-company tool

What makes the history more interesting than a single success story is how widely the model then spread. Doerr gathered his experience in the book "Measure What Matters" (2018), and the book shows something easy to miss if you only think of OKR as a Silicon Valley phenomenon: the model has been used by organizations with nothing in common with a tech company — like the Gates Foundation in its philanthropic work, and Bono's campaign organization ONE.

That says something important about what kind of tool OKR actually is. It doesn't care about industry. It cares about there being a direction to move toward, and a way to prove you're actually moving there.

Next: how it works in practice

The history explains why OKR looks the way it does — but it doesn't say how to actually write a good Objective, or what separates a Key Result that works from one that's just a task list in disguise. That's the subject of the next article: how OKR works in practice.