Objective and a Key Result:The Difference in Two Tests
Objective and a key result: one is a direction, the other is proof the world changed. Two simple tests tell you which is which, with examples to sort it out.
What is the difference between an objective and a key result? An objective is a direction: where you're heading and why it matters. A key result is evidence: a measurable state showing the world changed. If you can finish it by ticking boxes, it's neither. It's a task.
What is the difference between an objective and a key result?
The line between an objective and a key result is the whole method. Get it wrong and everything after it is decoration.
Most people get it wrong in the same way. They write the work and call it a goal. "Launch the new onboarding." "Publish twelve articles." Clean, specific, easy to tick off. Also useless, because you can deliver every item perfectly and change nothing about your business.
So let's pull the layers apart, starting with an objective and a key result, because they get mixed up constantly. There are the goals, the plan and the list. Each answers a different question.
| Layer | The question it answers | Sounds like |
|---|---|---|
| Objective | Where am I trying to get to, and why? | A direction, in plain words. |
| Key result | How will I know it's happening? | A number with a starting point and a target. |
| Plan | What do I intend to build or do about it? | The bets you're placing. |
| List | What is the specific work? | The tasks you tick off. |
Only the first two are goals. The bottom two are how you chase them. Mixing the layers is how you end up busy and going nowhere.
An objective is a direction, not a task
An objective says where you're trying to get and why it matters. Written so that someone with no context would understand it.
Good objectives share three traits. They're qualitative. They're memorable. And they're slightly uncomfortable to commit to. If it doesn't make you wince a little, it's probably safe, and safe goals teach nothing.
Here's the test I'd use. Could you complete it by working down a list? Then it's a work plan wearing a goal's clothes.
A real objective can be reached in several different ways. That isn't a flaw. It's the feature. It leaves you room to find a better route than the one you imagined on day one. A project has one route. A direction has many.
It also isn't a feature, a project, or a part of your business with a verb stuck on the front. "Improve the newsletter" is a part of the business with a verb. It tells you where to look, not where to arrive.
Free guide · 23 pagesGoals that change your Monday.The OKR Playbook: how to make a goal change what you do on Monday.Get the free guide →A key result is evidence that the world changed
A key result is how you'll know the objective is being achieved. It has to be a measurable state, not an activity.
Two examples are worth memorising. "Publish twelve articles" is an activity. You can do it flawlessly and change nothing. "Grow signups from forty to a hundred and twenty a month" is a changed state. The articles may be how you try. If they don't work, you switch tactics and the goal is still alive.
Read that again. The activity is allowed to fail. The key result isn't.
That's the freedom the distinction buys you. Because you committed to the change and not the method, you can drop what isn't working without having failed. If you'd committed to the twelve articles, you'd feel obliged to finish all twelve, even in week eight when it's obvious they're not moving anything.
Two tests to tell an objective and a key result apart
You don't need to trust your instincts. Apply two questions to any draft.
- The so-what test. If I achieved exactly this and nothing else, would the business be meaningfully different? If the answer is "well, I'd have shipped it", you've got a task.
- The would-we-know test. Is there a specific number, with a baseline and a target, that I can read at the end of the quarter without arguing about what it means? If the answer involves the word "feels", you've got a wish.
A key result passes both. An objective doesn't need to pass the second, because it's meant to be qualitative. That's the division of labour. The objective gives the direction. The key results make it checkable.
Sort these before you write yours
Practice on items you didn't write, because it's easier to be harsh. Here's how to sort a mixed pile.
| Draft | What it really is | Why |
|---|---|---|
| Become the first name buyers think of in my niche | Objective | A direction. Memorable, uncomfortable, many routes. |
| Grow signups from forty to a hundred and twenty a month | Key result | A changed state with a baseline and a target. |
| Publish twelve articles | Task | Deliverable in full with nothing changing. |
| Launch the new onboarding | Task | A piece of work with a deadline attached. |
| Reach five hundred weekly users | Incomplete | No baseline. Four hundred and fifty or fifty? |
| Improve the newsletter | Neither | A part of the business with a verb attached. |
Notice the fifth row. It looks like a key result. It has a number. But without a starting point you can't tell whether it's ambitious or already met. See how to set a key result baseline for the fix.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →How an objective and a key result fit together in a real quarter
One objective. Up to three key results underneath. That's the shape for a person working alone, and the reason is simple: the key results are the objective made checkable, so each one should be a different way of seeing the same change.
Then the plan sits beneath them. That's where your tasks and projects belong. The twelve articles go there. The onboarding launch goes there. Nothing is wrong with tasks. They just aren't goals.
The useful discipline is to trace any item on your list upward to a key result. And to notice, without drama, when a big share of what you did this week can't be traced to anything.
Skip a layer and you pay for it. A list with no plan produces busy incoherence. A plan with no goals produces confident shipping in no particular direction. A goal with no list is a nice sentence in a document you stopped opening.
If you're wondering how much to put at the top of that stack, how many OKRs to have gives the blunt answer. And once you have the shape right, how to write OKRs walks through the drafting itself.
Why does this matter more when you work alone? Because nobody else will catch it. In a company, someone eventually asks, "We shipped a lot, but did the number move?" You have to ask yourself, and the question is only easy to ask if a number exists. An objective gives you the reason to care. A key result gives you something to be honest about. You need both, and you need them in different sentences.
Try it on your own business this week, with one objective and a key result to match. Write the one direction you most want to move. Then write the single number that would convince a sceptical stranger it had moved. If you can't name the number, you haven't finished thinking. That isn't a failure. It's the work.
Free guide · 23 pagesGoals that change your Monday.The OKR Playbook: how to make a goal change what you do on Monday.Get the free guide →The mistake hiding in the middle
The most common failure isn't confusing an objective with a key result. It's confusing a task with a key result. It looks the same on the page.
You write "Launch X by the end of the quarter". It feels like a commitment. It has a date. It's measurable in the sense that it either shipped or didn't.
But watch what it does. It rewards finishing. And you can finish without any effect on the business. A goal system that rewards finishing has quietly reintroduced the exact problem it was built to solve.
The repair costs one question. Ask what would be different once this is done. Write that. Let the launch be one of the ways you try to get there.
A related trap: setting a number you can't influence. A key result you can't move produces watching rather than working, and it teaches you that the goals are decorative. Check that the owner, which is you, can actually push the number. This is one of the entries in the mistakes to avoid.
Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →Frequently asked questions
Does an objective need a number?
No. An objective is qualitative. It gives the direction and the reason. The numbers belong to the key results, which make the direction checkable.
Can a key result be a launch?
Not on its own. A launch is a piece of work and can be delivered in full while nothing changes. Ask what would be different once it's live and write that as the key result instead.
Where do my projects and tasks go?
In the plan and the list, beneath the goals. The goals say what should be different. The plan says what you'll build or do. The list holds the specific work. Trace every task upward to a key result.
How do I tell an objective and a key result apart when they look alike?
Ask whether it can be completed by ticking items off, or read as a number without argument. A direction with many routes is an objective. A measurable state with a baseline and a target is a key result.
The full method, with the checklists, is in The OKR Playbook, a free 23-page playbook.
How trapped are you, really?
Take the Corporate Suffocation Index, the free solopreneur readiness assessment.