Goal setting / focus & alignment
OKRs (Objectives & Key Results)
OKRs pair a qualitative Objective, where you are going and why it matters, with three to five measurable Key Results that prove you got there.
Scored transparently on a quarterly rhythm, they exist to focus effort and expose progress. Used as an input to performance ratings, they collapse into sandbagging.
- Problem
- Goal setting / focus & alignment
- Altitude
- Team to enterprise
- Effort to run
- Moderate
- Evidence base
- Established
Theory & origin
Andy Grove built the method at Intel out of Drucker's management-by-objectives, stripping away MBO's annual, top-down, pay-linked machinery and replacing it with a fast, transparent rhythm. John Doerr carried it to Google in 1999, and his book Measure What Matters made it the standard approach everywhere. The design principles carry the real value: fewer objectives than feels comfortable, key results written as evidence rather than tasks, ambition calibrated so that hitting about 0.7 counts as success, and the rule most organizations break first, keeping it decoupled from compensation. The moment OKRs start pricing bonuses, everyone negotiates for targets they have already hit.
Key components
The parts of the model and what each one means, in plain terms.
- Objective
- The qualitative destination: significant, concrete, and inspiring enough to survive a whole quarter of Mondays. It answers "where are we going, and why."
- Key Results (3-5)
- The measurable evidence that you arrived: outcomes with numbers attached, not activities. If it cannot be scored, it is not a key result.
- Initiatives
- The work bets placed to move the key results. Deliberately kept separate, since an initiative can fail while the key result still moves, and the reverse can happen too.
- Cadence & scoring
- Weekly confidence check-ins, quarterly scoring done in the open. The rhythm is the real system. The documents are just what is left over from it.
Explore the model
Objective
Key results
How a consultant runs it
- 01 Cut the list first: three objectives per team, maximum. An OKR set with nine objectives is just a task list wearing a costume.
- 02 Rewrite key results as outcomes with numbers, like "activation 22% to 35%," not as activities, like "launch the campaign."
- 03 Calibrate ambition openly: 0.7 counts as success, and 1.0 across the board means the targets were sandbagged.
- 04 Install the rhythm: weekly confidence check-ins, quarterly scoring done in the open. OKRs die of neglect, not of bad design.
- 05 Keep them out of the bonus formula, and say so in writing. It is the first thing a new CFO will try to change.
When to use
- 01 Focusing an organization that is busy everywhere and making progress nowhere
- 02 Making cross-team dependencies visible through transparent, public objectives
- 03 Replacing an annual MBO ritual that measures activity instead of outcomes
When not to use
- 01 Tied to compensation. This is the single most common way implementations fail, and it is fatal.
- 02 For run-the-business work. Keeping the lights on belongs in health metrics, not in aspirational objectives.
- 03 In cultures unwilling to score honestly in public. Secret or inflated scoring is worse than having no OKRs at all.
Worked example
A 60-person product company runs quarterly planning that produces 40 "priorities," and ships late on all of them. The OKR reset: each of four teams gets a maximum of two objectives, key results get rewritten from activities into outcomes, and scores get published at the all-hands.
First-quarter scores average 0.5, and two teams discover their key results were secretly dependent on each other, a piece of visibility the old system never produced.
By the third quarter the average sits at 0.68, cycle time on top priorities has halved, and the exec team kills eleven zombie projects that the OKR lens exposed as belonging to nobody's objective.
Common pitfalls
- 01 Linking OKRs to bonuses and converting ambition into negotiation
- 02 Key results that are just relabeled tasks, scoring effort instead of outcomes
- 03 Set-and-forget: written during planning week, rediscovered during scoring week
- 04 Cascading mechanically down the org chart until frontline OKRs are just fragments nobody actually chose
Sample deliverable
One real engagement, start to finish. Watch the numbers travel from raw input, onto the chart, into the finished artifact.
Input
- KR1: activation 22% to 35%hit 33%
- KR2: trial-to-paid 8% to 12%hit 10.5%
- KR3: churn 3.1% to 2.4%hit 3.0%
- KR4: NPS 31 to 40hit 38
Process
Key results are scored 0 to 1.0 in the open. The pattern calibrates ambition and exposes where things are blocked.
Quarter scorecard: Digital Banking growth team
- Average0.60, a healthy level of ambition
- KR3 blockedchurn is owned by no one
- Next quarterchurn gets its own objective