OKR vs KPI: which one you actually need this quarter

A key performance indicator is a number you watch continuously because it tells you whether something important is working — churn, gross margin, on-time delivery, response time. An objective and key result is a time-boxed statement of something you intend to change, with the measurable outcome attached. The distinction is between monitoring and changing, and confusing them causes specific, recognisable damage.

The most common version: a team takes a healthy KPI — say, ninety-eight per cent on-time delivery — and makes it a quarterly key result. Nothing needs to change; the number is already fine. The quarter is spent maintaining, the OKR is scored green, and the method has produced exactly nothing.

How they differ

• Purpose: KPIs monitor the health of ongoing work. OKRs describe a deliberate change.
• Time: KPIs are permanent and reviewed continuously. OKRs are set for a quarter and retired.
• Ambition: a KPI has a threshold you want to stay above. An OKR has a target you are not certain of reaching.
• Number: a business watches a handful of KPIs indefinitely; a team runs one to three objectives a quarter.
• Consequence of missing: a KPI going the wrong way means something is broken. Missing an OKR by a margin can be a perfectly good quarter, if the target was genuinely ambitious.

How they connect

The useful relationship is that a KPI going the wrong way is the most common reason to write an OKR. Churn drifts up for two quarters; that is a KPI telling you something. The response — reduce churn among customers in their first ninety days from twelve per cent to seven — is an OKR. When the work is done and the number is healthy again, the OKR retires and the KPI goes back to being monitored. OKRs are what you do about KPIs, not a replacement for them.

1. List the numbers you would want to see if you were away for a month. Those are your KPIs; most businesses have between five and ten and are watching too many.
2. Set a threshold for each, so that a problem is visible without interpretation.
3. Look at which ones are drifting, or which part of the business you have decided to change deliberately.
4. Write one to three OKRs against those, for the quarter.
5. Keep the KPI dashboard and the OKR page separate, so that neither swallows the other — the dashboard side is covered in kpi dashboard.

Never put routine operational numbers into OKRs. Keep invoicing accurate and Maintain uptime are obligations, not objectives; putting them in the quarterly set makes the set easy to hit and squeezes out the one thing you actually intended to change. If a number must simply not get worse, it belongs on the dashboard.

Which to start with

For most small businesses, KPIs first and OKRs later or never. Knowing your handful of health numbers, with thresholds, is more valuable than any quarterly goal ceremony, and it is the prerequisite for writing a useful OKR at all — you cannot set a target from a starting point you have never measured. The method itself, and when it earns its cost, is covered in okr.

Where they live

Ettex Board holds the quarterly objectives and the work under them; the continuous numbers come out of Ettex Sheets and Ettex Books, with the monthly reporting rhythm described in management accounts.

The limits, plainly: no scoring engine, no automated dashboards, no alerting when a KPI crosses a threshold. What we provide is where the numbers are calculated and where the work is tracked; the judgement about which numbers matter is not something software supplies.