Writing Objectives
An Objective is not a metric target with a label on it. It is a sentence the team would be glad to make true. This chapter covers what that looks like, how to find one, and why picking just one is the hardest part.
An Objective is qualitative and inspiring
The Objective answers "why bother this quarter". It is qualitative (no numbers), specific to your scope, time-boxed, and ideally points at a benefit for a real person rather than an internal convenience. It should be a sentence the team would be glad to achieve. If it reads like a KPI or a task, it is not an Objective yet.
Ask, then wait: "Say the Objective out loud. Does anyone lean in, or does the room stay flat?"
- If faces stay blank, ask what would make this worth a quarter of their working lives.
- A metric in disguise ("increase activation by 10 percent") goes straight to the KR column.
- A task in disguise ("complete the migration") gets the question: "and then what changes for someone?"
Example: from flat to compelling
Increase activation by 10 percent.
Make a new user's first day feel effortless. (The 10 percent lives in the Key Results underneath.)
The second version is qualitative, human-facing, and worth aiming at. It leaves room for the team to find several routes to the outcome rather than assuming one number covers the full intent. The metric is still there. It just went to the right layer.
An Objective people can repeat without checking their notes is the simplest form of alignment.
Start from your biggest obstacle
A reliable way to find a real Objective is to name the single biggest thing in the team's way, then flip it into the positive state you want instead. The obstacle is concrete and shared. The flip gives you something worth aiming at. This beats brainstorming aspirational directions because it starts from pain the whole room can agree is real.
Ask, then wait: "What is the one obstacle you would remove if you could only remove one thing this quarter?"
- Silent write first: everyone writes their own answer before anyone speaks.
- Cluster the cards on the wall, let the group pick the biggest shared pain.
- Then flip it together: "what does the world look like when that obstacle is gone?"
Example: obstacle flipped to Objective
Setup takes days of manual back-and-forth before a new customer goes live.
Customers get set up in one sitting, with almost no manual work from us.
The obstacle is concrete and everyone agreed it was real. The flip is human-facing and qualitative. It does not specify a portal, a form, or an API. That leaves the team free to find the most direct route, which might not be the one they would have assumed if they had started from a brainstorm.
Focus comes from agreeing what hurts most, not from brainstorming everything that could be nice.
Saying no
One Objective per team per time-box is the norm for a reason. Two competing Objectives means the team will quietly default to the comfortable one when things get busy. The act of choosing one is the hardest and most valuable thing the whole exercise produces. It forces the conversation about what this quarter is actually for.
Ask, then force: "We have three candidates. The team gets three votes total, not three per person. Which one?"
- Lay all candidate Objectives out on cards or a screen before any voting.
- Give the group three votes combined. The scarcity forces real prioritisation.
- Name explicitly what was deferred and why. That story matters for the next cycle.
Example: the cost of choosing two
Both Objectives run simultaneously. Each gets half the attention. By quarter end both sit at 0.4. The team reports progress on both and calls it a success. Nothing moved enough to matter.
One Objective, fully backed. By quarter end it lands at 0.8. The team can say clearly what was deferred and why. That conversation shapes the next quarter's planning.
The argument that surfaces during the vote is the prioritisation the organisation has been avoiding. Getting it on the table, even uncomfortably, is more valuable than any perfectly worded Objective. Two at 0.4 is always worse than one at 0.8 and one honest deferral.
Saying no is focus made real, and it is almost always the thing the team finds hardest.
Paste your OKR into Diagnose and see how it scores on clarity, timebox, and strategy.