Most OKR advice is really a list of loopholes dressed up as guidance — a rule for every situation, an exception for every rule, until a document meant to bring clarity is longer and more confusing than the strategy it's supposed to express. That's backwards. The whole point of an OKR is that it's simple enough to actually hold in your head during an ordinary Tuesday. Simple isn't the easy version of this — it's the disciplined version. It's harder to write a short, sharp OKR than a vague, comprehensive one, which is exactly why most people don't.
These are the rules Keel actually uses — the same ones built directly into the OKR writer inside the platform, not a looser blog-post version of them. Each one exists for a specific, practical reason, and the reason matters more than the rule — once you understand why a rule exists, you stop needing to check it, because you can feel when something breaks it.
The Objective: Verb + Outcome, nothing else
Why: an objective is what everyone looks at constantly — on a dashboard, in every review, every time someone wants a quick read on where things stand. The moment it starts carrying its own justification, it gets congested, and something meant to be scanned in a second turns into something people start skimming past. The reasoning still needs to exist. It just doesn't live here — it goes in the definition.
Vague verbs — understand, explore, support, ensure — don't survive this rule either, and that's deliberate. None of them can be verified true or false. "Ensure the team is aligned" can mean almost anything to almost anyone, which means it will. Strong verbs commit to something checkable: grow, build, launch, reduce, increase, win, close, ship.
The Definition: where the justification actually lives
Why: stripping the objective down to verb and outcome only works if the "why" has somewhere real to go — otherwise you've just deleted the reasoning instead of relocating it. The definition is that place. And there's a second, quieter benefit to writing it the same way every time: when every objective across a team is defined in exactly this format, everyone already knows where to look the moment they're unsure what something means. Nobody has to guess whether the justification is buried in the objective, hidden in a key result, or explained somewhere in someone's head. It's always in the same place, written the same way — which is what actually lets a room full of different people look at the same dashboard and see the same thing.
The Key Result: a symbol, a short name, a date, a number
Why the number: ambiguity is where OKRs quietly die. "Improve retention" can be declared a success by whoever's presenting it, regardless of what actually happened. A number is falsifiable — either it moved, or it didn't, and everyone in the room saw the same result.
Why the cap at three: beyond that, you've stopped focusing and started reporting. Every additional key result dilutes attention on the ones that actually matter, and creates the illusion of precision — as if measuring more things makes the objective more real, when usually it just makes the review meeting longer.
Mix leading and lagging
At least one key result should be something you can measure before the outcome is confirmed — a leading signal. At least one should be the outcome itself — lagging, the final number that proves it worked. Lagging measures alone mean you find out you missed the target only once it's too late to do anything about it. A leading measure gives you a chance to notice you're off course while there's still time to change something.
The Initiative: the actual work, not the aspiration
Why: a key result tells you what needs to move. It doesn't tell you what you're actually going to do about it. Without a named initiative attached, an OKR is just a target with no plan underneath it — a wish with a due date. The initiative is where "are there projects we must complete?" gets an honest answer, and where progress gets reported against something concrete enough to actually check on, not just against the same target number every review.
Best possible, not moonshot, not safe
One level below the objective it's attached to
A personal OKR that just restates the organisation's strategic objective isn't really an OKR — it's a copy-paste with someone's name attached. The actual discipline is translating a shared priority into what this specific person, in this specific role, is going to change about their own work to move it. If you can't tell, reading someone's OKR, what they personally are on the hook for, the OKR hasn't done its job — the accountability has quietly evaporated into "the organisation will handle it."
What this actually looks like
Every objective above is verb first, outcome second, no "and," no justification. Every one has a two-sentence definition carrying the reasoning instead. Every key result opens with its symbol, has a short name, a date, and a number, with at least one leading and one lagging measure. Every objective has a named initiative behind it. None of this is decorative — every constraint here exists because a looser version of it has a specific, predictable way of failing, and this is what's left once you've deliberately closed off each of those failure modes.
There's a second reason to hold the format this tightly, beyond any single rule: consistency is its own feature. When every OKR in a room is written the same way, everyone already knows what they're looking at and where to look if they're not sure — the definition, always, for the why. Nobody has to learn a new structure to read someone else's objective. That shared fluency is worth more, over a full year of quarters, than any individual rule on its own.
Simple isn't the beginner version of OKRs. It's the actual discipline — the part that's easy to describe in a blog post and genuinely hard to hold to in the room, three objectives into a long afternoon, when a vague one would be so much easier to let slide.