Objectives and key results: a short qualitative objective, three or so measurable results that would show it had been achieved, reviewed quarterly.
The framework came out of Intel and spread through Google, and it works well in the setting it was built for. Applied to one person's personal goals it mostly doesn't, and the reason is worth understanding before you spend a Sunday setting them up.
The problem OKRs actually solve
Alignment across people who can't see each other's work.
In an organisation, the difficulty isn't that individuals don't know what to do. It's that two hundred people making locally sensible decisions produce incoherence, and nobody has visibility into whether the sum of everyone's effort adds up to anything. OKRs make intent legible: written down, shared, and framed so that a person in another team can tell whether their work supports it.
Almost every design feature follows from that. The public writing, the quarterly cycle matching planning cycles, the deliberate separation of the ambition from its measures, the scoring — all of it exists to coordinate people who are otherwise operating blind to one another.
You do not have that problem. There is one of you, and you have complete visibility into your own intentions.
That's the whole analysis in one line, and most of what follows is working out which parts of the framework were solving the coordination problem and which were solving something else. The answer turns out to be that nearly all of it was coordination.
What survives for an individual
One thing, and it's genuinely valuable.
Separating the ambition from its measures. The objective is what you want, stated in ordinary language. The key results are how you'd know. Keeping those apart stops two common failures — chasing a number that stopped representing the thing, and holding an ambition so vague that nothing follows from it.
In practice that's the same structure as a goal with a one-line reason underneath and a concrete next action attached. Swim Tuesday and Thursday before work. Because my back stops hurting when I swim regularly. The reason is the objective; the behaviour is the measure. You don't need the vocabulary to get the benefit.
What doesn't survive
Four parts, and they're most of the framework.
Quarterly cycles. Companies plan in quarters because budgets and reporting do. Your life doesn't, and a personal quarter is an arbitrary box that some goals will fit and most won't. A book is eight quarters. A fitness practice has no end. Forcing them into a quarterly frame produces artificial milestones that mean nothing on the day they're missed.
Scoring. Grading yourself 0.7 on a key result requires an estimate of progress towards a destination, which is exactly the number that lies in personal work. It also introduces a small quarterly ritual of self-assessment, which for most people produces a mood rather than a decision.
Stretch targets. The deliberate practice of setting goals you'll only partly achieve makes sense when the alternative is sandbagging, and there's a manager, and everyone knows 70% is a good result. Alone, with nobody calibrating you, a target you consistently miss is just a target you consistently miss, and the accumulated effect is corrosive rather than motivating.
The writing overhead. An hour of setting up, a quarterly review session, a scoring exercise. In an organisation that's cheap relative to the coordination it buys. For one person it's a substantial ceremony purchased with nothing in return.
The failure mode
The predictable one: setup becomes the activity.
OKRs are enjoyable to write. They produce a document that looks serious, feels like clarity, and takes an entire Sunday. Then a quarter passes, and the review is a slightly awkward accounting exercise, and the second quarter's OKRs are written with rather less enthusiasm, and by the third quarter the whole apparatus is quietly gone.
That's not a failure of discipline. It's what happens when you install machinery for a problem you don't have. The effort goes into maintaining the framework rather than into the work, which is the standard failure of every system borrowed from an organisation and applied to one person.
The honest case for using them anyway
The counter-argument, and it's not weak.
If you work for yourself, OKRs may be doing genuine coordination work. A founder with contractors, or a freelancer with several concurrent clients, has something closer to the original problem — multiple threads, limited visibility, and a real need to check whether the sum adds up.
There's also a case for borrowed structure as a forcing function. Some people genuinely benefit from a fixed quarterly moment where ambitions have to be written down and last quarter's have to be faced. The framework is a reason to do that, and I do OKRs is easier to sustain than I intend to think carefully about my priorities every so often.
And if your job uses them, using the same structure personally has a real advantage in reduced friction. One vocabulary, one cycle, one habit.
The criticism is narrow: for a person with three or four personal goals and nobody to align with, the framework costs more than it returns. It isn't wrong, it's oversized.
What to use instead
The same benefit at a fraction of the overhead.
A short list — three or four live goals, because that's what a person sustains. Each with a next action concrete enough to do this week, and a one-line reason that does the objective's job.
Measure the behaviour rather than progress towards the destination, because behaviour is countable without estimation and stays honest when the work turns.
And review by silence rather than by score. Which of these has gone quiet, and why. That question produces decisions; how am I tracking against key result two produces a number you invented.
The quarterly moment is worth keeping, though not for scoring. Once every three months, run the relief test on everything: imagine each goal over permanently, and delete the ones that produce lightness. Fifteen minutes, and it reliably returns more capacity than any amount of objective-setting.
Which is roughly what a quarterly OKR review is reaching for, arrived at from the other end. The organisational version asks whether you achieved what you said. The personal version that's actually useful asks whether you still want it.
Related: Outcome goals vs process goals · The quarterly cull · Three goals, not thirty
Share: