Setting OKRs for HR Teams: A Practical Framework for Indian Companies
If your HR OKRs look like a to-do list with a fancy label, you are doing it wrong. Here is a framework that actually works.
I spent two years helping HR teams in Indian companies set OKRs. Here’s what I learned the hard way.
Most OKR content online is written for product teams and engineering leads. When HR teams try to adapt those examples, they end up with objectives like “improve company culture” and key results like “conduct 4 town halls.” That’s not an OKR. That’s a to-do list with a fancy label.
HR teams in India deal with specific challenges: high attrition in IT and BPO, strict statutory compliance requirements under PF and ESI, complex payroll structures with multiple components, and hiring volumes that would make most global HR teams blink. Your OKRs need to reflect this reality, not some generic framework copied from a Silicon Valley blog.
Let me walk you through how to build OKRs that actually work for HR teams in Indian companies.
What Makes a Good HR OKR?
An OKR has two parts. The Objective is qualitative: it says what you want to achieve and why it matters. The Key Results are quantitative: they tell you whether you got there.
A good Objective is inspiring but specific. “Become a great place to work” is too vague. “Reduce voluntary attrition to make our teams stable” is better.
A good Key Result has a number, a baseline, and a target. “Improve onboarding satisfaction” isn’t a key result. “Increase onboarding NPS from 6.5 to 8.0” is.
If your Key Result doesn’t have a number in it, it’s probably a task, not a result. This is the single most common mistake I see. HR teams list activities, conduct surveys, hold meetings, create documents, and call them key results. Activities are inputs. Key results measure outcomes.
OKR Example 1: Employee Retention
Objective: Reduce voluntary attrition so our teams stay stable and our hiring costs drop.
Key Results:
1. Reduce voluntary attrition rate from 22% to 15% by Q4
2. Increase exit survey completion rate from 40% to 80%
3. Implement stay interviews for all employees with 2+ years tenure (target: 100% completion)
4. Reduce average time-to-fill for replacement hires from 45 days to 25 days
Why these key results work: each one is measurable. The first tracks the outcome you actually want, people staying. The second gives you data to understand why people leave. The third is a leading indicator that catches problems before they turn into resignations. The fourth controls the cost of attrition when it does happen.
In Indian IT companies, attrition rates between 18 and 25% are common. Getting below 15% is a genuine achievement that directly impacts your recruitment budget. If your attrition is already at 12%, pick a different objective. You’ve already solved this one.
You can find more frameworks for setting measurable people goals at EasyHR’s OKR resource page.
OKR Example 2: Statutory Compliance
Objective: Achieve zero compliance penalties across PF, ESI, and Professional Tax.
Key Results:
1. File all PF returns on time (target: 100% on-time filing, up from 92%)
2. Zero show-cause notices from EPFO or ESIC
3. Complete monthly compliance audit checklist for all 6 locations (target: 100% completion)
4. Reduce ESI contribution reconciliation errors from 8 per quarter to 0
This one is close to my heart because I’ve seen companies get hit with penalties for simple filing errors. In India, statutory compliance isn’t optional, and the penalties compound. A show-cause notice from EPFO can escalate to prosecution if not addressed within 15 days. A zero-penalty quarter is a clear, trackable goal.
The key results here are binary, filed on time or not, notice received or not, plus one improvement metric for reducing reconciliation errors. That mix gives you both a standard to maintain and a process to fix.
If you want to dig deeper into compliance terminology, check the HR glossary for definitions of PF, ESI, and other statutory requirements.
OKR Example 3: Onboarding and New Hire Experience
Objective: Make new hires productive and confident within their first 60 days.
Key Results:
1. Increase onboarding NPS from 6.5 to 8.0
2. Increase new hire 90-day retention from 82% to 95%
3. Reduce time-to-first-productivity (manager-assessed) from 45 days to 30 days
4. Achieve 100% completion of mandatory induction training within first 2 weeks
Onboarding is one area where Indian companies, especially in the services sector, feel real pain. When you’re onboarding 50 people a month in a BPO, a bad process scales fast and hurts more with every batch.
Get Kanhai Chhugani’s stories in your inbox
Join Medium for free to get updates from this writer.
The NPS score tells you how new hires feel about the experience. The 90-day retention number tells you if the experience was good enough to keep them around. The time-to-productivity metric connects HR outcomes to business outcomes, which is how you get buy-in from department heads. And the training completion metric is a process health check.
OKR Example 4: Recruitment Efficiency
Objective: Fill open positions faster without compromising hire quality.
Key Results:
1. Reduce average time-to-fill from 52 days to 30 days
2. Increase offer-to-joining ratio from 65% to 85%
3. Maintain 90-day new hire performance rating at 3.5 or above (out of 5)
4. Reduce cost-per-hire from Rs 45,000 to Rs 30,000
The offer-to-joining ratio is a particularly Indian challenge. Candidates often accept offers and then ghost on the joining date. Sometimes they got a counter-offer. Sometimes they were never serious. Tracking this metric forces you to build a better candidate engagement process between offer day and joining day. Simple things like weekly check-in calls and a pre-joining information packet can move this number significantly.
Notice how the third key result acts as a guardrail. You could reduce time-to-fill by lowering your hiring standards. The performance rating keeps you honest. If your time-to-fill drops but your 90-day performance rating also drops, you’re hiring faster but worse. That’s not progress.
Tools that help track these metrics make a real difference. You can explore performance management features to see how software can help track OKR progress without drowning in spreadsheets.
OKR Example 5: Employee Engagement and Development
Objective: Build a workplace where people want to grow, not just collect paychecks.
Key Results:
1. Increase eNPS from 28 to 50
2. Increase percentage of employees with active development plans from 30% to 75%
3. Launch internal mobility program with target of 15 internal transfers or promotions this quarter
4. Achieve 80% participation in at least one learning initiative per quarter
The first OKR I ever saw an HR team write was “improve employee engagement.” The key result was “conduct quarterly town halls.” Town halls are an activity, not an outcome. If you run a town hall and engagement scores drop, the town hall didn’t work. You need to measure what changed, not what you did.
The key results above focus on measurable outcomes. eNPS gives you a sentiment pulse. Development plan coverage tells you whether your growth infrastructure is real or just a policy document nobody reads. Internal mobility is a strong signal: if people are moving internally, they see a future at your company. And participation rates tell you if your learning programs are actually reaching people.
Mistakes I keep seeing (and making)
Writing task lists instead of OKRs. “Conduct 12 training sessions” is a task. “Increase training effectiveness score from 60% to 80%” is a key result. Tasks tell you what you did. Key results tell you what changed because of what you did.
Setting too many OKRs. If you have more than 3 or 4 objectives per quarter with 3 to 4 key results each, you have a strategic plan, not OKRs. Pick the 3 things that matter most. Everything else can wait. I once worked with an HR team that had 11 objectives. They hit none of them. The next quarter they tried 3 and hit 2. That’s how it should work.
Using unmeasurable key results. “Improve culture” isn’t measurable. Neither is “build team spirit” or “strengthen communication.” If you can’t put a number on it, either find a proxy metric or pick a different objective.
Copying OKRs from another team. Your recruitment team’s OKRs shouldn’t look like your L&D team’s OKRs. Each function has different outcomes to deliver.
Setting safe targets. If you’re confident you’ll hit 100% on every key result, your OKRs are too easy. Good OKRs should feel achievable but uncomfortable. Hitting 70% should still feel like success.
Forgetting to check in. OKRs aren’t set-and-forget. If you write them in January and look at them again in March, you’re doing it wrong. Bi-weekly check-ins take 15 minutes and keep the team honest about progress.
A template to get started
Copy this format and fill in the brackets for your first OKR.
Quarter: [Q1/Q2/Q3/Q4 202X]
Objective: [One sentence describing what you want to achieve and why it matters]
Key Result 1: [Metric] from [current baseline] to [target] by [date]
Key Result 2: [Metric] from [current baseline] to [target] by [date]
Key Result 3: [Metric] from [current baseline] to [target] by [date]
Owner: [Name]
Check-in cadence: Bi-weekly or weekly
Final thoughts
OKRs aren’t a religion. They’re a tool. If the framework isn’t helping your HR team focus on what matters, change the framework. The point is to have clear, measurable goals that your team can rally around, not to fill out a template that looks impressive in a presentation.
Start with one objective. Three key results. One quarter. See what happens. You’ll learn more from one cycle of trying than you will from reading another article about OKRs.
I know because that’s exactly how I started.
