How to Write OKRs: A Practical Guide for UK Leaders (2026)

Most advice on how to write OKRs starts in the wrong place. It starts with the template.

Write an Objective. Add a few Key Results. Put it in a slide deck. Call it alignment.

That’s how teams end up turning project plans into OKRs. “Launch the new onboarding flow.” “Hire two SDRs.” “Run three campaigns.” The format looks correct. The thinking is wrong. Those aren’t outcomes. They’re tasks with better branding.

When leaders struggle to write good OKRs, I rarely see a writing problem. I see a strategy problem. The team hasn’t made the hard choices. Priorities are fuzzy. Ownership is blurred. Nobody has agreed what must change, for whom, and why it matters commercially.

OKRs are useful because they expose that confusion fast. If you can’t write a clear Objective, your direction is unclear. If you can’t define measurable Key Results, you don’t know what success looks like. If every initiative becomes a Key Result, your team is still managing work instead of managing outcomes.

Most OKR programmes start to rot at this point. They become admin. Then scorecards. Then theatre.

Your OKRs Are Probably Just a To-Do List in Disguise

The most common OKR failure isn’t bad syntax. It’s bad thinking.

Leaders tell teams to “create OKRs”, and teams respond by reformatting their quarterly delivery plan. Projects become Objectives. Milestones become Key Results. The result is predictable. Everyone stays busy, and nobody can say whether the business outcome improved.

That’s why mechanical cascading usually fails. When OKRs are pushed down as instructions, teams comply on paper and disconnect in practice.

The real mistake

Most bad OKRs share one trait. They describe what the team will do, not what will change.

A weak set of OKRs sounds like this:

• Objective: Launch the new customer portal
• Key Result: Complete design by May
• Key Result: Release version one
• Key Result: Train support team

That isn’t an OKR. It’s a project plan.

A better version sounds like this:

• Objective: Make customer self-service fast and reliable in order to reduce support dependency
• Key Result: Increase successful self-serve resolution rate from X to Y
• Key Result: Reduce support tickets related to common account actions from X to Y
• Key Result: Improve customer satisfaction for help journeys from X to Y

Now the team has a result to own, not a checklist to complete.

If your OKRs read like a status update, they’re already broken.

What writing OKRs actually diagnoses

Writing OKRs forces leadership teams to answer uncomfortable questions:

1. What matters most right now
2. What are we willing to deprioritise
3. What measurable change would prove progress
4. Which teams need to shape the goal, not just receive it

If you can’t answer those, don’t run another OKR workshop. Fix the strategy conversation first.

How to Frame a Powerful Objective

A good Objective is the headline for a meaningful change. It should tell a team, in plain English, what will be different if they succeed and why that matters.

I use one structure because it forces discipline:

Verb + what you will do + in order to + business value

For example:

Improve the company website’s effectiveness as a marketing tool in order to generate more leads and online purchases.

That works because it names the change and connects it to value. It doesn’t hide behind jargon.

The six tests I use

Run every Objective through this checklist.

• Inspirational: It should give the team something worth aiming at.
• Attainable: Stretch is good. Fantasy is useless.
• Qualitative: Keep numbers out. Numbers belong in Key Results.
• No weasley waffle: If it sounds like boardroom fog, rewrite it.
• Single change in state: One Objective. Not three stuffed into one sentence.
• Doable in the timescale: If it can’t move in a quarter, it’s probably too broad.

Weak versus strong Objectives

The weak examples are generic enough to mean anything. That’s exactly the problem. Teams can’t execute against vagueness.

What a strong Objective sounds like

A strong Objective creates a picture in the team’s head. People can tell what success feels like before they see the metrics.

Practical rule: If two leaders can interpret the Objective in different ways, it isn’t ready.

I also watch for the word “and”. It usually signals that the writer has combined multiple ambitions into one sentence. “Improve onboarding and reduce churn and increase expansion” is not focus. It’s avoidance.

If you want a useful benchmark for clear business goal language, review these aims and objectives for business. The point isn’t to copy wording. It’s to see how much sharper your own language needs to become.

A simple rewrite method

When an Objective is weak, ask one question:

What specifically will be different if we succeed?

That question strips out fluff fast.

“Drive operational excellence” becomes “Reduce handoff friction in customer fulfilment in order to improve speed and reliability.”

“Build a high-performance culture” becomes “Create a management system that gives teams clear priorities and faster decisions.”

That’s how you write Objectives. Not by polishing empty words, but by naming a real change.

How to Define Measurable Key Results

Bad Key Results expose bad strategy.

That is the part many OKR guides skip. They teach a format, teams fill in blanks, and everyone pretends the numbers mean something. Then the quarter ends and leadership learns an expensive lesson. A metric is only useful if it proves the Objective is becoming true.

Use one structure:

Verb + metric + from X to Y

Examples:

• Increase monthly newsletter subscribers from 500 to 1,000
• Reduce time-to-first-value from 11 days to 5 days
• Improve lead-to-qualified-opportunity conversion from 22% to 32%

This format forces discipline. You have to choose a metric, name the starting point, and commit to a target. If a team cannot do that, the issue is rarely wording. The issue is that the team does not yet agree on what success looks like.

Why vague Key Results fail

“Improve engagement” is not a Key Result. It is a placeholder for unfinished thinking.

Vague language creates predictable failure. Teams cannot score progress consistently. Leaders debate interpretation instead of making decisions. Work gets reported as activity because activity is easier to defend than impact.

Researchers behind the State of Organizations 2023 report from McKinsey found that organizations perform better when goals are clear, measurable, and tied to outcomes people can act on. That lines up with what happens in real OKR cycles. Precise Key Results improve choices because they show whether the work is changing the business condition you care about.

Seven tests for a strong Key Result

Use these checks before you approve any KR.

1. It stretches the team
   A target that feels safe will not change behaviour.

2. The team can influence it
   If the metric is controlled somewhere else, ownership becomes fiction.

3. It is quantitative
   If progress cannot be measured, scoring turns into opinion.

4. It shows movement on a scale
   “Complete rollout” belongs in an initiative plan. “From X to Y” belongs in a Key Result.

5. It proves the Objective
   The metric should confirm the Objective is happening, not sit nearby as a vanity number.

6. It has one definition and one source
   If sales, finance, and product each calculate it differently, the KR is broken before the quarter starts.

7. It drives the right behaviour
   Any metric can be gamed. Choose one that rewards the result you actually want.

Output versus outcome

Weak OKRs usually collapse at this point.

Outputs describe work. Outcomes describe change.

That distinction matters because OKRs are not a project tracker. They are a test of whether your chosen actions are producing the result your strategy requires. If your KR says “launch,” “build,” “publish,” or “run,” you are measuring effort. You are avoiding the harder question of whether the effort worked.

If your team struggles to define the right measures, this guide on How to Measure Anything is useful because it pushes teams to choose better proxies, clarify evidence, and measure with enough precision to make decisions.

How many Key Results are enough

Use 3 to 5 Key Results per Objective.

Fewer than three usually means you are oversimplifying a complex outcome. More than five usually means the Objective is bloated or leadership refused to make trade-offs. Both are strategy problems disguised as writing problems.

Reviewing strong objectives and key results examples helps because the gap is usually not grammar. It is whether the metric demonstrates progress toward the outcome.

Connecting Outcomes to Action with Initiatives

Objectives are often well-understood. Some teams grasp Key Results. Many forget Initiatives entirely.

That’s a mistake because initiatives are where execution happens. They are the projects, actions, experiments, and tasks a team believes will move the Key Results.

Keep the layers separate

The distinction is simple.

• Objective tells you what you want to achieve.
• Key Results tell you how you’ll know it’s happening.
• Initiatives tell you what you’ll do to try to make it happen.

That separation gives teams room to think.

Say your Key Result is increase lead-to-qualified-opportunity conversion from 22% to 32%. Your initiatives might include:

• Implement CRM lead scoring
• Train the SDR team on qualification criteria
• Create a new demo script

Those are good initiatives because they are plausible actions. They are not the goal itself.

The quarter should not hinge on whether an initiative shipped. It should hinge on whether the Key Result moved.

Why this matters in practice

When teams confuse initiatives with Key Results, they become rigid in the wrong place. They protect the project plan instead of the outcome.

A healthier pattern is this:

• Keep the Objective stable for the quarter.
• Keep the Key Results stable unless the metric is clearly wrong.
• Change Initiatives quickly if they aren’t moving the numbers.

That’s how teams learn instead of defend.

If you want a practical view of how strategy gets translated into real work, this piece on turn your strategy into action is worth reading. It addresses the operational gap that sits between ambition and delivery.

Start with the Problem Not the Solution

The easiest way to write bad OKRs is to start with a blank template and ask, “What should our OKRs be?”

That question invites opinion, politics, and recycled wish lists.

Start with a problem statement instead. It forces the team to diagnose reality before prescribing action.

The writing quality matters, but so does the operating rhythm behind it. Teams write specific OKRs when they're solving a defined problem — not filling in a form.

The four-part problem statement

A useful problem statement has four parts.

1. Current situation
   What is happening now?

2. Impact
   Why is that a business problem?

3. Desired state
   What needs to be different?

4. Importance
   Why does fixing this matter now?

Here’s a practical example.

• Current situation: Our customer support response time averages 48 hours.
• Impact: Customers escalate repeatedly, and support volume keeps rising.
• Desired state: We need to reduce average response time to under 24 hours.
• Importance: Faster resolution should improve retention and reduce internal firefighting.

Once you’ve written that, the Objective is obvious: Transform our customer support experience in order to build the loyalty that drives retention.

The Key Results also become easier:

• Reduce average first response time from X to Y
• Increase first-contact resolution from X to Y
• Improve customer satisfaction on support interactions from X to Y

Why this approach works better

Teams write cleaner OKRs when they start from pain, not aspiration. The conversation changes. Instead of debating language, they debate evidence.

Start with the business problem. The Objective should read like the answer to it.

If your teams keep writing activity-heavy OKRs, they usually haven’t made the shift from task thinking to value thinking. This explanation of the difference between outcome vs output helps because that distinction sits underneath almost every weak OKR I see.

Common OKR Writing Mistakes and How to Fix Them

Weak OKRs are rarely a wording problem. They expose fuzzy strategy, avoidance of trade-offs, and a habit of confusing motion with progress.

You can usually diagnose the failure in a single review. The team has written a project plan, labelled it an OKR, and called the exercise done.

Research from What Matters reinforces a basic rule that many teams ignore: keep Objectives concise, make Key Results measurable, and avoid turning tasks into outcomes. When teams miss those distinctions, OKRs stop being a strategic tool and become reporting theatre.

The mistakes that keep showing up

Fast rewrites that work

These examples show the difference.

• Bad Objective: Increase NPS to 50
  Fix: Improve the customer experience so loyalty and retention rise

• Bad KR: Launch new website
  Fix: Increase website visitor-to-enquiry conversion from X to Y

• Bad KR: Hold weekly cross-functional meetings
  Fix: Reduce decision turnaround time for priority product issues from X to Y

• Bad Objective: Drive excellence across sales and marketing
  Fix: Improve the handoff between marketing and sales to raise pipeline quality

What these mistakes actually mean

Each bad OKR points to a deeper issue.

A numbered Objective usually means the team started with metrics before it had strategic intent. A task-based Key Result usually means nobody defined what success should change in the business. A long list of Objectives usually means the leadership team wants to avoid the cost of saying no.

That is why formula-only OKR advice falls short. The formula matters, but the thinking matters more. OKRs are a diagnostic tool for strategy. If the writing is weak, the strategy conversation upstream is usually weaker.

If your organisation keeps repeating the same patterns every quarter, review these common reasons OKRs fail in practice. The problem is usually operating discipline and strategic clarity, not grammar.

The Correct Process for Writing Effective OKRs

Good OKRs are written in a strict order. Disregarding that order often leads to goals feeling disconnected.

They start with metrics because metrics look rigorous. But metrics without direction are just numbers on a page.

Poorly written OKRs create the appearance of discipline without the substance of alignment. The sequence below fixes that.

Use this sequence

1. Strategy first
   Get clear on the few priorities that matter this quarter. If leadership can’t name them, stop there.

2. Define the problem
   Write the issue in concrete business terms. What’s happening, why it matters, and what needs to change.

3. Write the Objective
   State the qualitative outcome. Keep it sharp and commercially relevant.

4. Define the Key Results
   Choose 3 to 5 measurable signs that prove the Objective is being achieved.

5. List the Initiatives
   Identify the projects and actions most likely to move those metrics.

Keep the number of Objectives low

Leadership teams should have 2 to 3 Objectives maximum. More than that is usually a sign that the executive team hasn’t had the hard conversation about focus.

If a team can’t choose, it doesn’t have an OKR problem. It has a prioritisation problem.

This sequence also clarifies ownership. Strategy belongs to leadership. Problem diagnosis should be shared. Teams should help shape Key Results and initiatives so the goals are grounded in operational reality, not just executive intent.

If you want to see worked OKR examples across different functions, compare them against your own drafts. If you’re trying to solve the broader challenge of implementing OKRs beyond the writing exercise, or need clarity on the distinction between OKRs and KPIs, deal with that before your next planning cycle. And if your teams still confuse measures with motion, revisit the fundamental shift from output to outcome thinking.

If managers need help facilitating the process — running the writing sessions, challenging weak drafts, and coaching teams on the distinction between projects and outcomes — OKR training for managers addresses exactly that gap.

If your leadership team knows the strategy but still can’t translate it into focused execution, I can help fix that gap. Explore OKR consulting if you want practical support applying this properly — not just writing better-looking documents. Or book a call if you want to talk through where your current OKRs are breaking down.