Key Result narratives
A Key Result narrative is the short written case beneath the number: why this measure, why this target, what we believe will move it, and what would show us we were wrong.
The obvious bit
A number on its own carries no reasoning, so nobody can disagree with it usefully and nobody can learn from it afterwards.
Three months later the goal missed. Was the belief wrong, the target wrong, or the execution? Without the narrative, that argument is settled by whoever remembers it most confidently, which is not the same as correctly.
What goes in it
Three or four sentences. Not a business case, and the brevity is deliberate: a narrative that takes a page will not get written and will not get read.
Why this measure. Where it sits on the metric tree, and what it is a proxy for if it is one.
Why this target. The baseline, the stretch, and the argument for the gap.
What we believe will move it. The causal claim, stated plainly enough that someone could disagree.
What would show us we were wrong. The most valuable line and the one most often missing. It converts the goal from an assertion into something testable.
Why it is worth the ten minutes
It catches bad goals before the cycle starts. A measure whose narrative cannot be written is usually a measure chosen because it was available. That discovery in planning is cheap; in week ten it is not.
It makes the retrospective possible. The first question in any honest retro is what did we believe. If that was never written, the session becomes a discussion of feelings.
It survives people leaving. The reasoning existed once, in somebody's head, and then that person moved on. The narrative is the cheapest defence against organisational amnesia there is.
It makes alignment real. Two teams can have compatible numbers and incompatible beliefs. Only the narrative shows that.
The failure modes
The narrative written after approval. Retro-fitted justification, which teaches nothing because the reasoning did not shape the choice.
The narrative that restates the number. “We will increase retention because retention is important.” No claim, nothing to be wrong about.
The narrative with no falsifier. Comfortable, and useless in the retro.
The narrative nobody reads. Usually a length problem. Four sentences get read. A page does not.
Our opinion
This is the highest-value ten minutes in goal setting, and the first thing dropped when planning runs late.
The tell is simple. If your team cannot write four sentences explaining why a Key Result is the right one, the problem is not the writing. It is that nobody is sure, and the number was going to hide that for a quarter.
One line to keep: a Key Result without its narrative is a number you cannot argue with, which means it is a number you cannot learn from.
How long should a narrative be? +
Three or four sentences. Long enough to carry the belief and the falsifier, short enough that people actually read it in the review.
Who writes it? +
The team that owns the Key Result, at the time they propose it. Written afterwards it becomes justification, and justification teaches nobody anything.
What is the most important line? +
What would show us we were wrong. It is the line most often left out, and it is the one that makes the goal testable rather than merely asserted.
From the ZOKRI OKR Handbook, the methodology we install and maintain. Written by Matt Roberts.
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.
We coach the narrative habit in the first planning cycle. It adds ten minutes per Key Result and removes most of the arguments you would otherwise have in week ten.