OKRs vs KPIs for People Teams: What to Measure, What to Chase

When the company adopts OKRs, the people team dutifully writes some — and usually writes them badly. "Maintain attrition below 18%." "Complete appraisal cycle on time." These are not objectives; they are job descriptions with numbers attached.

The confusion is between two different instruments. KPIs monitor the health of an ongoing system. OKRs drive a deliberate change. People teams need both, and need to stop dressing one up as the other.

KPIs: the dashboard you watch

These run continuously, whether or not anything is being "transformed":

• Regretted attrition, overall and for high performers
• Offer acceptance rate and time-to-fill for open roles
• 90-day new-hire retention
• Engagement or eNPS trend
• Span of control and people-cost as a percentage of revenue
• Diversity of hiring pipeline and of promotions

KPIs belong on a dashboard reviewed monthly. They trigger investigation when they move, and they should be stable in definition year over year so trends mean something. A KPI does not need a quarterly "goal" — it needs a healthy range and an owner who notices departures from it.

OKRs: the changes you commit to

OKRs are for the two or three things the people team intends to make different this quarter or year. Good examples:

• Objective: Make manager quality our retention engine. Key results: 100% of managers through feedback-skills training; manager effectiveness score up from 3.4 to 3.9; regretted attrition in bottom-quartile-manager teams cut by a third.
• Objective: Fix the leaky hiring funnel for engineering. Key results: offer acceptance from 62% to 80%; candidate NPS above 50; structured interviews adopted in 100% of panels.

Notice the pattern: each OKR changes a system, and the key results are outcomes, not activity. "Conduct training" is a task. "Manager effectiveness score moves" is a result.

The classic failure modes

• Everything becomes an OKR. Running payroll accurately is not an objective; it is the job. Teams with twelve OKRs have zero priorities.
• Activity masquerading as outcome. "Launch new PMS" is output. The outcome is whether feedback quality, clarity, or retention moved.
• HR metrics nobody in the business cares about. If your key results do not connect to retention, capability, cost, or speed, the business will treat people OKRs as decorative. HR's measures should read like business measures — which is also the heart of earning a seat at the strategy table.
• Gaming. Any measure that determines someone's appraisal will be optimised, sometimes destructively. Keep stretch OKRs partially decoupled from individual ratings.

A simple operating rhythm

• Monthly: KPI dashboard review — fifteen minutes, exceptions only.
• Quarterly: OKR scoring and reset — honest scoring, including failures, with lessons recorded.
• Annually: re-derive people OKRs from the business strategy, not from last year's list.

That last step is the discipline most teams skip. People-team goals should fall out of the company's strategy: if next year's plan is "expand to three new cities," the people OKRs concern leadership pipeline and hiring engines, not a new intranet.

If your people metrics feel busy but not consequential, we can help you rebuild the measurement architecture — start a conversation or see how we approach it in our case studies.