OKR: objectives and key results | Henri Sora | Negotiator 58

Summary

Henri Sora, co-author of a Finnish book on running strategy with OKRs, explains the mechanism that travelled from Andy Grove’s Intel through John Doerr to Google: a short text objective, numeric key results beneath it, a maximum of five per level, weekly confidence tracking, and — critically — no money attached. The episode covers why tying a bonus to a key result turns goal-setting into the budget game, why OKRs are not KPIs, how a quarter boundary should be run, and where the model gets awkward: sales, and individual performance review.

What is discussed

• The lineage. Doerr learned the mechanism at Intel under Andy Grove, took it into Google as an investor, and Google’s own people credit it with results more than ten times what they expected.
• Text plus numbers. ‘Go to the American market’ is an objective; five per cent market share by year end and five reference customers are key results.
• Where it sits. Strategic thinking produces options, strategy is the decision, and OKRs carry that decision into the everyday — the tactical box, roughly a year out.
• The negotiation. Company objectives first, then the leadership team’s own quarter, then downward — but items can be pushed back up when a team recognises something that belongs to the whole firm.
• No money, no punishment. Attach a bonus and the incentive is to negotiate the target down to 80 or 90 per cent and bank it; remove both money and punishment and people set targets that scare them.
• Weekly, not quarterly. A short session each week reporting position, plan and confidence — and a culture where a hand goes up as soon as there is a problem, rather than at the quarter wall.
• Five, preferably fewer. One workshop arrived with seventeen objectives; compressing them to five was a relief to everyone, because it told them what they were not doing.
• Retro first. At a quarter boundary you look backwards and ask what can be learned before asking whether the objectives are still valid — not update the numbers and move on.
• Transparency as a working tool. Seeing another unit’s objectives tells you what to talk to them about, and makes otherwise invisible work legible in a large organisation.
• Not a scorecard. Because targets are relative and negotiated, comparing 60 per cent against 70 per cent between people or teams is meaningless.
• KPI or key result? Sora insists on the vocabulary precisely because the two decay into each other: a hundred KPIs read the engine; an OKR points somewhere.
• Sales is the hard case. Qualitative objectives — this kind of customer, five of them — can be set with OKRs, but they must stay in sync with whatever the commission scheme actually pays for.
• Down to one person. The book’s Finnish translator used OKRs on her own strategy and found the same discipline useful: reduce first, define, then move.
• The compressed argument. As Sora puts it, the model produces conversation rather than instruction — and if that conversation is about what matters and what should be done, it is hard to name something more important.

Watch

The recording lives on the Neuvottelija channel: OKR objectives and Key Results | Henri Sora | Neuvottelija 58. A Finnish edition of this episode is published at www.neuvottelija.fi.