Definition of an OKR: an objective and proof that it has been achieved
OKR is the acronym for Objectives and Key Results. No standard sets its definition: it is a practice, described by those who use it. In this practice, an OKR brings together two elements. The objective says in words what you want to achieve. The key results, few in number, say how you will tell that it has been achieved: they are measurable and verifiable.
The What Matters website, associated with John Doerr’s book Measure What Matters, gives a formula for it: “I will (objective) as measured by (key results)”. This website attributes the creation of the method to Andy Grove, at Intel, building on Peter Drucker’s management by objectives, and the name OKR to John Doerr, who introduced it to the founders of Google.
What OKRs bring to management
Among the effects attributed to them by What Matters and the “Set goals with OKRs” guide on Google’s re:Work website, three are retained here.
- Focus: a small number of objectives forces the others to be set aside for the period.
- Alignment: objectives are public within the organisation, and those of a team are linked to those of the level above.
- Learning: end-of-period scoring is used to adjust the next objectives.
Google’s guide sets two limits: OKRs are neither an evaluation of people nor a shared to-do list.
Objective, key results, cadence and scoring
| Element | What it sets | Benchmark taken from the sources |
|---|---|---|
| Objective | The desired state, in concrete terms | Three to five objectives (re:Work) |
| Key results | The measures that prove achievement | A result obtained, not an activity carried out (re:Work) |
| Cadence | The period for setting and reviewing | The quarter, with annual objectives in addition at Google |
| Scoring | The end-of-period assessment | Yes or no, three colours, or a scale from 0 to 1 (What Matters) |
What Matters distinguishes committed OKRs, which the team expects to achieve, aspirational OKRs, whose full achievement is not expected, and learning OKRs. On the 0 to 1 scale that Google uses, the re:Work guide puts the expected average across all OKRs between 0.6 and 0.7: a score that is always at the maximum signals objectives that are too cautious.
OKR, KPI and roadmap: not to be confused
A key performance indicator (KPI) continuously measures how an activity is running: availability of a service, processing time for a request. It has no end date. An OKR is bounded in time and designates a change sought. What Matters sums up the difference this way: OKRs measure change, KPIs measure health. Copying your dashboard into OKRs amounts to carrying over the status quo. Our article on PMO KPIs deals with reading indicators.
A roadmap orders dated milestones, the subject of our article on the IT project roadmap; an OKR says what effect those milestones should produce. The objectives that teams set during a PI planning belong to the SAFe framework and its calendar, whereas OKRs are not attached to any framework.
Example: the quarterly OKR of a billing team
Take the billing team of a services company. Its objective for the quarter: “business customers receive an accurate invoice from the first issue”. It attaches three key results to it: the share of invoices corrected after issue goes from its observed value to a target value set at the outset; the time between the end of the service and the issue of the invoice falls below an agreed threshold; no billing dispute remains open beyond a defined period.
“Roll out the new control module” does not appear: it is a means. At the end of the quarter, the team scores each result, then decides to renew the objective, reword it or drop it.
When several teams need to link their objectives to one another and to funding decisions, the subject joins those covered by our pages on agile at scale and on project portfolio management.