OKR vs KPI (vs Rocks vs SMART Goals): The Difference, Examples, and Which Your Leadership Team Needs

By Andreas Pettersson, Founder, Leaders ADAPT

The sales lead calls pipeline coverage a KPI. The CEO calls it a key result. The implementer calls it a Rock. The new finance hire calls it a SMART goal.

Everyone agrees it matters. Nobody agrees who owns it.

That is not a goal problem. That is a vocabulary problem, and it costs leadership teams a meeting a month in arguments about labels.

This page settles OKR vs KPI, adds Rocks, SMART goals and KRAs to the same table, and gives you the order to install them in. It belongs to our operating cadence guide. I have run the Entrepreneurial Operating System (EOS), OKRs and Scaling Up, and my honest view is that all of them are good. The order is what matters.

What is the difference between an OKR and a KPI?

A KPI is a measure you watch every week to know whether a part of the business is healthy. Gross margin. On time delivery. Cash position. It has no end date. It runs as long as that part of the business exists.

An OKR is a goal for a fixed period that states what should change and how you will measure the change. One objective, two to four key results. When the quarter ends, it is scored and replaced.

Teams confuse the two for a simple reason. Both are numbers, and both live in the same spreadsheet. The difference is not the format. It is whether the number is supposed to stay where it is or move.

So the question of KPI vs OKR is really a question about direction. A KPI asks: are we still fine? An OKR asks: what will be different by the end of the quarter?

A thermostat reading is a KPI. Deciding to replace the boiler before winter is an OKR. You need the reading to know whether the boiler decision is worth making.

How do OKRs, KPIs, Rocks, SMART goals and KRAs compare?

Five terms, one table. This is the version I give leadership teams when the label argument starts.

A few notes on the rows. The OKR vs Rocks choice is covered in depth in EOS vs OKRs. SMART is a writing format, not a system, so compare OKR vs SMART goals only on how each goal is written, and use our company goals guide for the format itself. KPI vs OKR vs KRA confuses people mainly because KRAs belong to role descriptions, not to planning.

What do OKR vs KPI examples look like side by side?

These OKR vs KPI examples show one health measure per function, the OKR you would write when it needs to move, and the Rock version of the same intent.

Read across a row and the relationship is obvious. The KPI tells you something is wrong. The OKR or the Rock is how you fix it this quarter.

Which does your leadership team need first?

KPIs. Every time.

KPIs First is the Leaders ADAPT rule that a company runs a weekly scorecard of owned KPIs for at least one quarter before it adds OKRs or Rocks on top. Without the baseline, you cannot tell whether a goal is ambitious or ridiculous.

Then keep the scorecard small. Too many numbers is the issue I see most. My rule: everyone needs one number they are measured by, and one thing they can actually impact. Spell out who the ultimate owner of each number is, and favour leading indicators, the ones that move before the result does.

Leading or lagging: which KPIs belong on the scorecard?

A lagging indicator tells you what already happened. Revenue booked, customers lost, margin for the month. You cannot change it by the time you read it.

A leading indicator moves first. Proposals sent, first meetings held, jobs scheduled two weeks out. You can still act on it this week.

A leadership scorecard needs both, weighted toward leading. An EOS implementer I spoke with put the leadership team scorecard at 5 to 15 numbers, each with a goal and a name next to it. My own bias is toward the low end, one per person. If the leadership team cannot say from memory what its numbers are, there are too many of them.

How many of each should a leadership team carry?

As a working range for a team of five to eight leaders: 5 to 10 KPIs on the weekly scorecard, one to three quarterly goals, whether you call them Rocks or OKRs, and one KRA per role in each job description. Anything above that is a sign that labels are being used to avoid choosing.

Our weekly scorecard guide covers choosing the numbers, and the weekly scorecard template gives you the sheet. If you want the verdict on EOS as the system around it, read my independent EOS review.

Once the scorecard is honest for a quarter, add the goal layer.

My own rule of thumb is a 90 day target for each priority, measured the way an OKR would measure it. Rocks for focus. OKR thinking for the measure. One to three of them for the whole leadership team.

Can a KPI become a key result, and when does it go back?

Yes, and this is the loop that makes the two systems work together.

1. A KPI turns red, or the business needs it at a new level.
2. The leadership team makes it a key result or a Rock for one quarter, with one owner and a specific target.
3. The owner reports on it weekly, on track or off track, in the leadership meeting.
4. When the target is reached and holds for a few weeks, it goes back to the scorecard as a KPI with the new target.
5. The goal slot opens for the next thing that needs to change.

A worked example, with the numbers made generic. On time delivery has sat on the scorecard at its target for a year. Then it drops for four straight weeks.

The operations lead takes it as the quarter's Rock: remove the scheduling bottleneck at the second site. Each week in the leadership meeting it is on track or off track, with the KPI beside it as proof. By week ten the rate is back above target and holding.

The Rock is marked done, and on time delivery returns to the scorecard, this time with a higher target, because the team now knows the old one was too easy.

Here is what happens when you skip step 4. The key result is met, everyone celebrates, and nobody watches the number again. Two quarters later it has slid back, and the team sets the same OKR again with a new name.

Measure. Improve. Hand back. Watch.

Where AI fits with KPIs and OKRs

The numbers side is where AI earns its keep. It can pull every KPI from its source system each week, compare it with target, flag the exceptions, and chase each Rock or key result owner for a one line status before the meeting. That is the scorecard pull and status collection work nobody on a leadership team enjoys.

It can also check your writing. Ask it to mark every key result that describes an activity rather than an outcome. It is faster and more honest about it than most leadership teams.

What stays human:

• People decisions about who owns each number
• Issue solving judgment when a KPI turns red
• Accountability consequences for a missed Rock
• Strategic commitments behind the choice of goals
• Performance conversations with the owner
• External promises built on a target

The full reasoning is in what not to delegate to AI, and the map across the whole operating system is in AI for companies running EOS.

What a KPI or an OKR does not fix

A number does not make anyone own it. A goal does not make anyone deliver it.

If people have implemented EOS and moved on, in my experience it is because leadership was never really established properly to begin with. The same is true of OKRs and scorecards. Companies switch frameworks looking for the one that will finally make people accountable. The framework was never the missing piece.

Accountability, delegation and hard conversations are leadership skills, and our leadership team development guide is where that work starts.

Common questions about OKR vs KPI

What is the difference between OKR and KPI?

The OKR vs KPI difference is purpose. A KPI is a number tracked continuously to show whether an existing part of the business is healthy, such as gross margin or on time delivery. An OKR is a goal for a set period that aims to change something, made of an objective and a few measurable key results that show the change happened.

What are OKRs and KPIs?

KPIs, or key performance indicators, are the ongoing measures a company uses to monitor performance, often reviewed weekly on a scorecard. OKRs, or objectives and key results, are time bound goals, usually quarterly, that describe a desired change and the measurable results that prove it. Many companies use both, with KPIs as the baseline and OKRs for improvement.

Can a KPI be a key result?

Yes. When a KPI falls below its target or needs to reach a new level, it can become a key result for a quarter, with a specific target and owner. Once the target is reached and holds, the measure usually returns to the regular scorecard as a KPI with an updated target, and the quarterly goal moves on.

What is the difference between OKRs and SMART goals?

SMART is a checklist for writing any single goal: specific, measurable, achievable, relevant and time bound. OKRs are a goal system that links an objective to several key results and is usually reviewed on a fixed cadence. A well written key result will normally pass the SMART test, but an OKR set adds structure, ownership and a review rhythm.

What is the difference between Rocks, OKRs and KPIs?

Rocks, from the Entrepreneurial Operating System, are a few 90 day priorities with one owner each, judged as done or not done. OKRs are periodic goals with graded key results and room for stretch. KPIs are continuous health measures on a scorecard. Rocks and OKRs change the business, while KPIs monitor it week to week.

What is a KRA compared to a KPI and an OKR?

A KRA, or key result area, is a broad area of responsibility for a role, such as customer retention or cash management. KPIs are the numbers that measure performance within that area. OKRs set a time bound goal to improve something within it. KRAs are most common in role descriptions and performance reviews rather than in company planning.

Your next question

• Annual planning, where the year's KPIs and goals are set
• 25 OKR examples for leadership teams
• The 5 Minute Leader protocols for accountability and rhythm

Now that OKR vs KPI is settled, look at your own sheet. How many of your "KPIs" are actually goals, and how many of your "goals" are actually KPIs? Reply and tell me what you find.