OKRs
5 min read · 4 principles · apply it by lunch
Good morning. Intel built it. Google scaled it. Here’s why it actually works.
Do the people on your team know the top three outcomes this quarter — and could they tell you without looking anything up?
OKRs — Objectives and Key Results — were developed at Intel by Andy Grove in the 1970s and brought to Google by John Doerr in 1999, when the company was barely a year old. They became the most widely adopted management framework in tech, used by organisations from 10 to 100,000 people. The structure is deceptively simple: an Objective is a qualitative, ambitious, time-bound direction. Key Results are the measurable outcomes that prove you got there. The discipline they create is alignment: everyone from the C-suite to the individual contributor knows what success looks like this quarter, and can see how their work connects to it. The failure mode most companies hit is vanity OKRs — objectives that sound ambitious but key results that measure output (calls made, features shipped) instead of outcome (revenue closed, retention improved).
OKRs is Day 12 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee