Bad OKR vs Good OKR: 8 Real Examples Side by Side
Everyone has heard of OKR. Half of all companies have tried it. And most quit within two quarters thinking the methodology was the problem.
It wasn't.
The problem was the OKRs were wrong from the start. And nobody noticed because they looked right.
Before you talk about tools, quarterly cycles, or weekly check-ins, you need to be able to answer one thing.
The question that defines everything
If someone outside your company looks at your OKRs 90 days from now, can they say without a shadow of a doubt whether you hit them or not?
If the answer is "depends" or "kind of," your OKRs are wrong.
OKR isn't about intent. It's about undeniable outcome. You either hit the number or you didn't. No interpretation. No "I think it went well."
That's the starting point. Now we build.
If the basic concept still feels fuzzy, start with How to Write OKRs: step-by-step guide with examples.
What an Objective is and how to write one that works
The Objective is the direction. It's qualitative, inspiring, and answers a single question:
Where are we going this quarter?
No number. No percentage. A sentence that makes the team want to get there.
Look at the difference in practice:
| WEAK Objective | Why it doesn't work | STRONG Objective | |
|---|---|---|---|
| Improve customer service | Vague. What does improve mean? | Make our customers feel they're being served fast and well | |
| Grow sales | Too obvious. Every company wants this | Turn our current base into a referral machine | |
| Be more efficient | Nobody knows what that means in practice | Deliver more without having to hire | |
| Improve the product | For whom? On what? | Get new customers to first result in less than 7 days |
See the pattern? A strong Objective creates a mental image. You can visualize what arriving means.
If I read this sentence to someone on the team, will they understand where we're going and feel like getting there?
If not, rewrite it.
What a Key Result is and where everyone gets it wrong
If the Objective is the direction, the Key Result is the proof you got there.
It's quantitative. It has a number. It has a deadline. It's undeniable.
And here lives the mistake that kills 90% of OKRs before they start.
If I hit this number, am I sure the business advanced? Or did I just do a lot?
Look at what happens when you don't ask that question. These 8 examples are real. I've watched them happen more than once:
| BAD Key Result | Why it's wrong | GOOD Key Result | |
|---|---|---|---|
| Implement new ticket system | Measures activity. You can implement and the customer can stay unhappy | Cut average response time from 48h to 4h | |
| Train the support team | Measures activity. Training doesn't guarantee outcome | Raise CSAT from 6.2 to 8.5 | |
| Create FAQ on the site | Measures delivery. Customer can ignore the FAQ and keep opening tickets | Cut repeat ticket volume by 40% | |
| Make 50 sales calls | Measures effort. You can call 50 times and close nothing | Close 8 new contracts by 6/30 | |
| Publish 12 blog posts | Measures production. Google doesn't pay you to publish | Grow organic traffic by 35% | |
| Hire 2 salespeople | Measures process. A hired salesperson isn't generated revenue | Grow pipeline by $40k | |
| Launch a new landing page | Measures delivery. The page existing changes nothing | Raise visitor-to-lead conversion from 1.8% to 3.5% | |
| Run 8 prospecting meetings | Measures effort. A booked meeting isn't a closed deal | Generate $15k in qualified proposals |
The difference between activity and outcome is simple. Activity measures what you did. Outcome measures what changed in the world because of what you did.
For more side-by-side examples, read Good vs Bad Key Result: 10 real examples.
How to build a complete OKR from scratch
Now put it all together. Here's a poorly written OKR and the same OKR redone correctly:
Objective: Improve customer service.
| Key Result | Target | |---|---| | KR1 | Implement new ticket system | | KR2 | Train the support team | | KR3 | Create FAQ on the site |
Question: in 90 days, will you know if you hit this OKR?
No. Because even if you do all that, the customer can still be unhappy and you'll call it a success anyway.
Objective: Make our customers feel they're being served fast and well.
| Key Result | Starting | Target | Deadline | |---|---|---|---| | KR1: Average first-response time | 48h | 4h | 6/30 | | KR2: CSAT (satisfaction score) | 6.2 | 8.5 | 6/30 | | KR3: Repeat tickets | 100% | Cut by 40% | 6/30 |
Now you can implement the system, train the team, and create the FAQ. But what counts is whether the numbers moved. Whether the customer felt the difference.
You can do everything right and the numbers don't move. The OKR tells you mid-quarter, not at year-end when there's nothing left to do.
The 3 questions to test any OKR before publishing
Before closing the quarter with your OKRs, run each one through this filter:
Does someone outside the team understand where we're going and want to get there?
If I hit this number, am I sure the business advanced? Or did I just do a lot?
If I hit every Key Result and the Objective wasn't reached, what went wrong?
If the third question doesn't make sense, your KRs aren't measuring the right thing.
How many OKRs you should have
Here's another classic mistake: the company that discovers OKR and decides to set 6 objectives with 5 KRs each in the first quarter.
That's 30 metrics to track at the same time.
Nobody tracks. Nobody remembers. The OKR becomes wall art.
Max 3 objectives per team, with max 3 Key Results each. That's 9 numbers. Nine things that actually matter.
Focus isn't doing less. It's knowing exactly what matters and going deep.
The ritual that separates who uses OKR from who just has OKR
Writing the OKRs is the easy part. What most people skip is the weekly tracking.
OKR without a weekly check-in is decoration. It looks nice on the wall and changes nothing.
The check-in doesn't have to be a long meeting. It needs to answer three questions every week, for each Key Result:
- Is the number moving in the right direction?
- If not, what changed last week?
- What are we doing differently this week?
Twenty minutes a week looking at the right numbers is worth more than a two-hour retrospective at quarter-end when there's nothing left to fix.
To structure the ritual, read Weekly Check-in: the ritual that makes OKR work.
What to do when an OKR isn't moving
It's mid-quarter and the number didn't move. What do you do?
| Situation | Diagnosis | What to do | |
|---|---|---|---|
| The team isn't executing | People or process issue | Conversation, realignment, remove blockers | |
| The KR doesn't move even with execution | The KR was wrong | Conscious revision. The premise was false | |
| The market changed and the objective no longer applies | Context issue | Courage to revise. OKR isn't law. It's a tool |
The wrong answer is hoping the last weeks save it. The right answer is opening the OKR now, understanding what's wrong, and making a decision.
To avoid the most common traps, When OKR Fails: 5 traps that kill the methodology.
The provocation I want to leave you with
Take this quarter's OKRs, if you have them.
For each Key Result, answer honestly:
- Does it have a number with starting and final target?
- Does it measure consequence or activity?
- If I hit this KR, did the business actually advance?
If the answer is no on any of these, you don't have an OKR. You have a well-formatted task list.
The difference between a company that grows and one that just stays busy lives exactly here: what you decide to measure.
Build cycles, define objectives, and track Key Results with weekly check-ins. Right in your browser, no account.
Create My OKRs Now →OKR isn't about doing more. It's about knowing if what you're doing moves the business in the right direction. And that only shows up when you measure the right thing.
Keep reading about OKR
OKR Complete Guide: What Actually Works in Practice
OKR isn't magic. It's method. When it works, it turns a reactive company into one that executes. When it fails, it becomes a to-do list with a fancy name.
OKR vs SMART Goals: Which Works for Small Teams
OKR and SMART are goal frameworks. They work in different situations — picking the wrong one for a small team is a recipe for nobody delivering.
Personal OKRs: How to Set Goals That Actually Stick
Wanting to lose weight, save money, or grow professionally aren't goals. They're wishes.
Frequently asked questions
What's the difference between a wrong OKR and a right one?
A wrong OKR measures activity (what you did): implement system, train team, make calls. A right OKR measures outcome (what changed in the world because of what you did): response time dropped, CSAT rose, contracts closed. The difference between being busy and growing.
How do I know if my OKR is measuring the right thing?
Ask three questions. For the Objective: would an outsider understand where we're going and want to get there? For each Key Result: if I hit this number, did the business actually advance, or did I just do a lot? For the set: if I hit every KR and the Objective wasn't reached, what went wrong? If the third doesn't make sense, your KRs are measuring the wrong thing.
How many OKRs should a company have per quarter?
At most 3 Objectives per team, with up to 3 Key Results each. That's 9 numbers. More than that and nobody tracks, nobody remembers, the OKR becomes wall art. Focus isn't doing less. It's knowing exactly what matters and going deep.
What do I do when an OKR isn't moving mid-quarter?
Diagnose the cause. If the team isn't executing, it's a people or process issue. If the KR doesn't move even with execution, the KR was wrong. If the market changed and the objective no longer makes sense, revise it. OKR isn't law, it's a tool. Hoping the last weeks save it is the wrong answer.
Why are weekly check-ins essential for OKR to work?
OKR without a weekly check-in becomes wall art. The ritual answers three questions for each KR: is the number moving in the right direction? If not, what changed? What will we do differently? 20 minutes a week is worth more than a 2-hour retrospective at quarter-end when it's already too late.