OKRs vs KPIs in the Boardroom: What the Board Tracks and What Teams Work On
OKRs vs KPIs in the Boardroom: What the Board Tracks and What Teams Work On
Most board packs I see have the same problem. They’re long and full of numbers. And they still don’t tell directors whether the strategy is working.
The data backs this up. Board Intelligence research on board packs, run with the Chartered Governance Institute UK & Ireland, puts the average pack at 226 pages, and 54% of directors struggle to find the key messages in it. The same source reports that 62% of directors find the management information they get too operational and not strategic enough.
That last number matters most. It means boards are buried in KPIs and starved of evidence that anything is changing. At that point the OKR vs KPI debate stops being a definitions exercise. It becomes a governance question: who looks at which numbers, and what they’re supposed to do about them.
OKR vs KPI for executives: two different questions
A KPI answers “Is the business healthy?” An OKR answers “What are we changing, and is it working?”
KPIs run continuously. Revenue, gross margin, cash, customer churn, safety incidents, staff turnover. Each one has a threshold and is expected to stay inside it. When a KPI is green, nobody needs to talk about it in the boardroom.
OKRs are time-boxed. An Objective names a change the organization commits to for a quarter or a half-year, and two to four Key Results define how you’ll know the change happened. They’re meant to stretch. Google’s re:Work guide treats roughly 70% delivery on ambitious OKRs as success and full delivery as exceptional. A board that expects 100% on every line will train management to stop aiming high within two cycles.
The two tools need each other. KPIs without OKRs give you a stable business that doesn’t move. OKRs without KPIs give you ambitious projects while the core quietly erodes.
If you want the full side-by-side comparison with examples by function, our KPI vs OKR guide covers it. This article is narrower. It’s about what reaches the board, what stays with management, and how the two connect.
What the board should track
The board’s job is oversight. Directors need two things from management reporting: confidence that the business is healthy, and evidence that the strategy is moving. The first is a KPI question. The second is an OKR question.
The NACD 2026 board practices survey names the metrics boards focus on as the main barrier to overseeing strategy execution. It also argues that boards should spend less time confirming management did what it said and more time asking whether the strategy still fits conditions. You can’t have that conversation if the pack only shows last quarter’s operating numbers.
A board view that supports it holds:
- A short set of health KPIs, each with a threshold and an owner, across finance, customers, people and risk
- The company-level OKRs for the current cycle, usually three to five Objectives
- For each Key Result: progress against target and management’s confidence it will land
- The one or two decisions management needs from the board this quarter
That’s it. If a metric has neither a threshold nor an owner, it belongs in an appendix or a functional report.
What teams work on
Teams don’t work on board KPIs directly. They work on the Key Results that sit under company Objectives, and they keep their own operational KPIs running in the background.
Take an illustrative case. A company Objective might be “Make enterprise onboarding something customers actually finish.” The customer success team owns a Key Result like “Cut time-to-value from 14 days to 5.” The product team owns another: “Raise the share of new accounts that complete setup within 30 days from 52% to 80%.” Meanwhile both teams still track ticket backlog and release quality as KPIs. Nobody upstairs needs to see those unless one goes red.
The split by level looks like this:
| Level | KPIs reviewed | OKRs reviewed | Cadence | The question they ask |
|---|---|---|---|---|
| Board | Company health KPIs against thresholds | Company Objectives and Key Results, with trend and confidence | Quarterly | Is the strategy still right, and is it moving? |
| Executive team | Company and divisional KPIs | Company OKRs plus cross-team dependencies | Monthly | What do we unblock or stop? |
| Department heads | Functional KPIs | Department OKRs linked to company Objectives | Every two to four weeks | Which Key Results are at risk, and what do we drop? |
| Teams | Operational KPIs for their own process | Team Key Results and the initiatives behind them | Weekly check-in | What did we learn, and what do we try next? |
Read the table from the bottom up and you see the filter. Each level passes up less detail and more judgment. The board should get the top row and nothing below it.
Where KPIs and OKRs meet: the red KPI rule
The bridge between board KPIs and team OKRs is simpler than most frameworks make it look. When a board KPI goes red and stays red, and fixing it needs a different approach rather than more effort, it becomes an OKR. At the OKR Institute we call this healing an unhealthy KPI through OKR.
Stay with the illustrative case. Say customer churn has sat above its 3% threshold for three quarters. The KPI stays on the board page, still red. Management adds the onboarding Objective from above, with its Key Results owned by the teams. Now the board sees two lines that belong together: the KPI tells them whether the problem is still there, and the OKR tells them whether the fix is working.
This pairing also gives directors a better conversation. If the Key Results land and churn doesn’t move, management’s hypothesis was wrong. That’s a strategic discussion, and exactly the kind the NACD survey says boards should be having. It’s far more useful than asking why a number is amber.
It works in reverse too. Once the OKR has done its job, the improved level becomes the new KPI threshold, and the Objective drops off the board page. OKRs are temporary. The gains they produce should become part of how the business is measured.
What a one-page board view looks like
Board Intelligence recommends keeping the KPI dashboard to a single page, with the narrative in a separate document. I agree, and I’d add the OKRs to that same page so directors see health and change side by side.
| Section | What goes in it | Format |
|---|---|---|
| Business health | Company KPIs against thresholds | Traffic-light status plus a four-quarter trend line |
| Strategic change | Company Objectives and their Key Results | Progress against target and a confidence score per Key Result |
| Decisions needed | What management asks of the board this quarter | One line each, two at most |
| Narrative (separate) | CEO commentary on what moved and why | Short prose, kept apart from the data |
Two details make this work. Frame each section as a question (“Is the core business healthy?”, “Is the strategy moving?”) so directors read with a purpose. And report confidence, not only percentages. A Key Result at 40% with high confidence and a clear plan is better news than one at 70% that has stalled.
Cadence: keep weekly check-ins away from the board
Teams check in on OKRs weekly and the executive team reviews them monthly. The board looks once a quarter, at the end of each cycle.
That spacing is deliberate. Weekly check-ins are noisy, full of small slips and course corrections. If directors read them, they’ll start managing teams, and the NACD survey is clear that boards need a forward-looking view without getting pulled into operational decisions. Give the board the trend and what management has learned from it. Leave the week-to-week to management.
Our Team-to-Impact Cycle is built on this layering, from weekly team check-ins up to the quarterly review, so the board receives a summary that teams didn’t have to produce separately.
Mistakes I see in management reporting
- Every KPI goes to the board “just in case.” The pack grows while the signal shrinks. Directors end up questioning whatever is amber.
- OKRs are reported as percent complete and nothing else. Without confidence and learning, a 40% Key Result on a stretch goal looks like failure when it might be the best work of the quarter.
- OKR scores drive executive bonuses. People stop setting ambitious targets the moment their pay depends on hitting them. Keep variable pay on KPIs and business results.
- OKRs that are KPIs in disguise. “Maintain NPS above 45” is a health threshold. If nothing changes in how the team works, it isn’t an Objective.
- Company OKRs set without the people who deliver them. Teams get handed Key Results they had no say in, so ownership never forms.
Most of these come from leaders treating OKRs as another reporting layer. They’re a management system, and the board sees only its output. Our C-OKRL leadership certification spends a lot of its time on exactly this shift.
FAQ
Should the board approve company OKRs?
The board should agree the strategy and the company-level Objectives that express it. Key Results and everything below company level belong to management. When directors start editing Key Results, they’re managing, not governing.
How many KPIs should a board track?
As many as fit on one page with a threshold for each. If a metric has no threshold and no owner, it doesn’t belong in the board pack.
Can a KPI become a Key Result?
Yes. When management decides to move a KPI well beyond its current baseline and that needs a new approach, the target becomes a Key Result for the cycle. The KPI stays on the dashboard.
Should executive bonuses be tied to OKR scores?
No. Linking OKR scores to pay pushes people to set targets they know they’ll hit. Keep variable pay on KPIs and business results, and use OKRs for focus and learning.
How often should the board review OKRs?
Quarterly, at the end of each OKR cycle. The board needs the trend and the confidence level, not the weekly check-in notes.
Get your board view on one page
If your board pack runs long and still doesn’t show whether the strategy is moving, that’s a design problem, not a data problem. The OKR Institute has trained more than 1,000 organizations in over 50 countries, and connecting KPIs to OKRs is a large part of what we do with leadership teams.
Book a call with me and bring your current board pack. We’ll sort out which KPIs belong on the board page and which red metrics should become OKRs.
Not ready to talk yet? Take the free Execution Health Check first. It takes about two minutes and shows where execution is breaking down
CEO of the OKR Institute
Related Courses
Recent Posts
Tags
#OKR
#OKR AI agents
#trends 2026