Objective
An Objective is a clear, inspiring, time-bound statement of what you aim to achieve: qualitative, starting with a verb, carrying a what and a why. It sets the direction that its Key Results then measure.
The craft is in the balance. An Objective must be specific enough to guide decisions, and broad enough to leave room for approaches nobody has thought of yet. "Make onboarding effortless for first-time admins" guides: you can test any week's work against it. "Improve the product" guides nothing. "Ship the new onboarding flow" forecloses: it has decided the solution before the quarter has started, which quietly turns a goal into a task list.
The narrative underneath
In our methodology every Objective is supported by a written narrative: the hypothesis behind it, its connection to strategy, the guardrails, and the constraints the team is deliberately accepting. This is the part most rollouts skip, and the part that makes autonomy safe. A team that can read the reasoning does not need to escalate every judgement call; a leadership team that has to write the reasoning discovers quickly whether it has any. The narrative is where aligned, not cascaded stops being a slogan and becomes a working mechanism.
The Opposite Test
Before committing to a draft Objective, run it through the Opposite Test, an idea we take from Roger Martin: would any sane rival pursue the reverse? "Improve customer satisfaction" fails instantly, because no competitor is pursuing dissatisfaction, which means it is not a choice at all. It is an operating imperative, business-as-usual in costume, and it belongs on a scorecard with a threshold. Objectives that survive the test are genuine choices: they commit you to one path at the visible expense of another, which is what makes them worth a quarter of a team's focus.
Qualitative by design
An Objective carries no number, and that is deliberate. The measurement lives in its Key Results; the Objective carries the meaning. If your Objective needs a metric to make sense, it is probably a Key Result wearing a hat, and you have skipped the harder question of why the number matters. Keep the ambition in words and the proof in figures, and each does the job it is good at: the words recruit people, the figures keep them honest.
One per team, occasionally two
The discipline of wildly important focus applies most sharply here. One Objective per team is the target; two is the ceiling; a team insisting on three usually means nobody has yet made the hard call about what matters most. A short, ownable Objective everyone can recite beats an exhaustive one nobody remembers, because the whole point of the Objective is to be the sentence people navigate by when the plan meets reality.
In practice
Draft the Objective last, not first. Begin with the problem and the desired change, write the Key Results that would prove it, and let the Objective crystallise from them. Teams that work in this order finish faster and argue less, because the statement is describing a decision they have already made rather than standing in for one they have been avoiding. The Opposite Test then catches whatever ambition-shaped filler slipped through.
Weak: "Improve our onboarding." A what with no why and no ambition. Real: "Make onboarding so effortless that new users reach value in their first session." Memorable, worth chasing, and it implies the trade-offs: effortless means cutting steps, not adding tooltips.
How many Objectives should a team have? +
One is the discipline; two is the ceiling. A team that insists it needs three usually means nobody has made the hard call yet.
Should an Objective contain a number? +
No. The Objective carries the ambition in words; the numbers live in its Key Results. If your Objective needs a number to mean anything, it is probably a Key Result wearing a hat.
What makes an Objective different from a task? +
A task decides the solution ("ship the flow"); an Objective names the change and leaves the method open ("make onboarding effortless"). If it forecloses the approach, it is a task.
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.
A good Objective is a decision, not a slogan. We coach leaders to make the choice, then install the system that turns it into weekly progress.