Menu
HR & People Operations

OKR (Objectives and Key Results)

What are OKRs?

OKRs, short for objectives and key results, are a goal-setting method in which a team defines a small number of ambitious objectives and attaches a few measurable key results to each. The objective describes what the team wants to achieve, and the key results describe how progress will be measured. They are usually set quarterly and reviewed often.

The method became popular through technology companies and spread widely among startups and growth-stage businesses. It is attractive because it is simple, transparent, and designed to align people around priorities.

How OKRs differ from KPIs

A KPI tracks the ongoing health of something, such as monthly active users or customer satisfaction. Objectives, by contrast, describe a change the team wants to make within a period. An objective might be to become the fastest support team in the market, with key results that measure response time and satisfaction.

The two work well together. KPIs show where you stand, while objectives focus effort on improving the numbers that matter most this quarter. Confusing the two leads to cluttered goals and unclear accountability.

Why OKRs suit distributed teams including India

Distributed teams cannot rely on hallway conversations to stay aligned, so this method provides a shared written reference. When everyone can see the objectives and key results, an India-based engineer and a headquarters-based product manager are working from the same priorities.

The method also reduces the need for constant status meetings. Progress is visible in the tracker, so conversations can focus on obstacles and decisions rather than updates, which is helpful across a large time difference.

Writing good objectives

A good objective is inspiring, qualitative, and time-bound. It should describe a meaningful outcome, not a list of tasks. Weak objectives read like project plans, while strong ones give people a reason to care.

Teams should limit themselves to a few objectives each quarter. Too many dilute focus and make it impossible to judge success. Three to five objectives at the company level, with fewer at team level, is a common pattern.

Writing measurable key results

Key results must be measurable and specific. Each one should have a clear number and a clear way to check it, such as reducing average resolution time from forty hours to twenty. Vague statements like improving quality cannot be scored.

Good key results describe outcomes, not activities. Shipping a feature is an activity, while increasing adoption of the feature is an outcome. Focusing on outcomes keeps the team honest about whether their work actually mattered.

Cadence and the financial year in India

Goals are normally set quarterly, and in India the financial year runs from April to March, so many companies align quarters with that calendar. Aligning goal cycles to the financial year helps connect goals to budgets and appraisals.

Whichever cadence a company chooses, consistency matters. Weekly check-ins, a mid-quarter review, and an end-of-quarter retrospective keep goals alive instead of letting them become a document written once and forgotten.

Scoring and the idea of stretch

In many implementations, teams score key results from zero to one, and a score of around seventy percent is considered healthy for ambitious goals. The idea is that goals should stretch the team, and consistently scoring one hundred percent suggests the goals were too easy.

This philosophy can be difficult to explain. Employees used to targets that must be met may read a seventy percent score as failure, so leaders should explain that stretch goals are different from committed targets.

OKRs and performance reviews

Many companies separate this method from compensation decisions, because tying pay directly to scores encourages people to set safe goals. Using OKRs for alignment and learning, and using other evidence for performance reviews, tends to produce more ambitious and honest goals.

For India-based employees, who may be accustomed to appraisal-linked targets, clarity is important. State explicitly how OKR results relate to reviews, so nobody is surprised.

Common mistakes with OKRs

Frequent mistakes include setting too many objectives, writing key results that are tasks, changing goals mid-quarter without discussion, and treating OKRs as a reporting tool for managers rather than a focus tool for teams.

Another mistake is imposing OKRs from headquarters without involving the India-based team. Teams that help write their own OKRs understand them better and commit more strongly.

Tools and transparency

OKR software, or even a shared spreadsheet, makes goals visible. Visibility is a central feature of the method, since seeing how your work connects to the company's priorities is motivating, and seeing what other teams are doing reduces duplication.

Whatever tool is used, keep it simple. A complicated system that nobody updates defeats the purpose.

Cascading goals from company to team

Alignment happens when company-level objectives translate into team-level ones. A common approach is to set company priorities first, then ask each team to propose goals that contribute, then adjust for conflicts. This two-way process matters. Purely top-down goals feel imposed, while purely bottom-up goals may not add up to the company's direction. For an India-based team, joining this conversation early ensures local constraints are understood and that their work is visibly connected to what leadership cares about. Avoid cascading too far down, since forcing every individual to have a perfectly linked goal creates paperwork without improving results.

Running a useful quarterly review

At the end of each quarter, gather the team and review what happened. Score each key result honestly, discuss what worked and what did not, and capture lessons for the next cycle. Avoid turning the session into a blame exercise. The purpose is learning, and people who fear being punished for missing a stretch goal will stop setting them. Keep the meeting short, circulate the results beforehand, and schedule it at a time that works across time zones. A well-run review takes an hour and saves weeks of confusion in the next quarter.

Handling priorities that change mid-quarter

Business conditions shift, and rigid goals can become irrelevant. When a priority genuinely changes, discuss it openly, update the written goals, and note the reason. Quietly abandoning a goal erodes trust, while transparent changes show maturity. At the same time, avoid changing goals so often that nothing is ever finished. A useful rule is to revisit goals only at planned check-ins unless something major happens. Distributed teams especially benefit from documenting changes in writing so nobody wakes up to a different set of priorities without explanation.

How kaam.work supports teams using OKRs in India

kaam.work provides the employment infrastructure for India-based team members, so companies can focus on aligning them through OKRs. When goals feed into increments or bonuses, kaam.work ensures changes are reflected correctly in contracts and payroll.

Frequently asked questions

What does OKR stand for?
Objectives and key results, a goal-setting method pairing ambitious objectives with measurable key results.
How are OKRs different from KPIs?
KPIs track ongoing health, while OKRs describe a change the team wants to achieve during a specific period.
How many OKRs should a team have?
A small number, commonly three to five objectives with a few key results each.
Should OKRs be tied to pay?
Many companies keep them separate to encourage ambitious goals, but the relationship to reviews should be stated clearly.
How does an Employer of Record support OKRs?
It handles employment, payroll, and compliance so teams can focus on goals, and reflects any OKR-linked pay changes correctly.

Hire and pay talent globally with Kaamwork

Payroll, compliance and benefits handled end to end — so you can hire the best people, anywhere, without the red tape.