OKRs

How OKRs work

An objective says where you want to go, in plain words. It should be meaningful and a little uncomfortable: "Make our hourly hiring the fastest in our market."

Key results say how you'll know you got there. Each is measurable, time-bound and an outcome rather than a task:

• Median time from application to offer for hourly roles falls from 12 days to 5.
• Interview no-show rate drops from 35% to 20%.
• Candidate satisfaction after the interview rises from 3.6 to 4.3 out of 5.

Tasks like "launch self-scheduling" are initiatives that support key results, not key results themselves. Most teams set three to five objectives per quarter at most, with two to five key results each. Progress is reviewed weekly or every two weeks and scored at quarter end.

OKR examples for HR, recruiting and L&D

Talent acquisition

• Objective: Staff the new 200-seat site on time without lowering quality.
• KRs: 200 agents hired by June 30; 90-day attrition at or below 25%; offer acceptance rate at or above 85%.

HR operations

• Objective: Make onboarding paperwork painless.
• KRs: 95% of new hires complete paperwork before day one; zero late I-9 Section 2 completions; new-hire survey rating for paperwork at or above 4.5.

Learning and development

• Objective: Get new agents productive faster.
• KRs: Speed to proficiency down from 10 weeks to 7; nesting pass rate up from 78% to 88%; trainee attrition down by a third.

Notice that each objective is a direction and each key result is a number with a baseline and a target.

OKR vs KPI

A KPI (key performance indicator) is a metric you monitor continuously to know whether business as usual is healthy: average handle time, cost per hire, absenteeism. An OKR is a time-boxed push to change something.

They work together. A KPI that's off track often becomes the subject of an OKR: if time to fill is drifting up, a quarterly OKR might target it. Once fixed, it goes back to being monitored as a KPI. A team with 40 KPIs and no OKRs is maintaining; a team with OKRs and no KPIs is probably missing problems in the day-to-day.

OKRs vs SMART goals

SMART goals (specific, measurable, achievable, relevant, time-bound) are mostly used for individual goals and are meant to be achieved. OKRs are usually set at company and team level, designed to stretch, and often transparent across the organization. Many companies use OKRs for team direction and SMART goals for individual development and performance plans.

Should OKRs drive performance ratings?

Most OKR practitioners say no. If people are rated and paid on OKR scores, they set safe targets, and the method loses its point. Keep OKRs as a planning and focus tool, and handle individual evaluation through your performance management process, where OKR contributions are one input among several. For frontline roles with fixed standards, individual OKRs rarely make sense; team OKRs for supervisors and managers work better.

Common mistakes

• Too many OKRs. Ten objectives means no focus.
• Key results that are tasks: "Run three hiring events" instead of "Hire 60 people from hiring events."
• No baseline, so nobody can judge progress.
• Set and forget: OKRs written in January and opened again in April.
• Cascading everything top-down, so teams just copy leadership OKRs instead of choosing their own contribution.
• Sandbagging: setting targets you know you'll hit because bonuses depend on them.