OKRs and goal-setting
skills employers want

OKRs — objectives and key results — are a method for focusing and aligning work. What Matters, the site founded by John Doerr, describes the objective as what is to be achieved and the key results as how you'll measure getting there.¹ Strong OKR practice includes choosing a few important objectives, writing key results as measurable outcomes, aligning team OKRs with company priorities through dialogue, running regular check-ins, scoring honestly at the end of a cycle and reflecting on what was learned. Linking goals to performance management is a skill in itself: done badly it encourages sandbagging, done well it supports growth conversations.

Focus is the point. Pendo found that 12% of features generate 80% of daily usage,² which shows how much effort can scatter across low-value work. A product north star, as Amplitude describes, often becomes the anchor for product OKRs.³ Goal-setting skills feature in strategy and people roles. In India, AmbitionBox lists strategy managers at a typical ₹26.7–29.6 lakh⁴ and HR business partners at ₹13.2–14.6 lakh.⁵

Objectives per team per cycle (common practice)

1–3

Key results per objective

3–5

Typical strategy manager pay in India (AmbitionBox)

₹26.7–29.6 lakh

Typical HR business partner pay in India (AmbitionBox)

₹13.2–14.6 lakh

Table: How OKR skills are assessed (editorial summary)

Table: Rewriting task key results as outcomes (illustrative)

Table: How OKRs developed (editorial summary)

• A set of OKRs you wrote with outcome key results
• Alignment to company priorities
• A check-in cadence you ran
• End-of-cycle scoring and reflection
• A changed priority because of OKRs
• A verified OKRs certificate

Show focus and results: "Reset company OKRs from 480 key results to 9 outcome measures; net revenue retention rose over two quarters."

"Write an OKR for improving customer support."

Objective: "Customers get help fast and leave happy." KRs: first response time, resolution time, satisfaction score targets.

"What's wrong with task-based key results?"

They measure activity, not impact; you can complete them without changing anything that matters.

"How do you align OKRs across teams?"

Share company OKRs first, let teams propose how they contribute and resolve gaps and overlaps together.

"Should every key result reach 100%?"

Ambitious key results often land around 0.6–0.7; always hitting 100% suggests goals are too easy.

"How do OKRs relate to KPIs?"

KPIs monitor ongoing health; OKRs focus effort on changes for a period.

• "How are OKRs set here?" — top-down or collaborative.
• "Are OKRs tied to compensation?" — incentives.
• "How often are they reviewed?" — cadence.
• "Which OKR changed the company's direction?" — real use.

Table: Roles using OKRs and typical pay in India (AmbitionBox, October 2026; indicative)

Table: Common OKR tools (editorial guidance)

• Team member — contributes to team OKRs.
• Team lead / manager — writes team OKRs.
• Strategy or ops manager — runs the OKR process.
• Head of strategy / COO — company goals.
• CEO — sets direction.

1. Week 1: Write — Draft OKRs for a team you know; rewrite tasks as outcomes.
2. Week 2: Align and prove — Link to company goals; take the OKRs Certification.

Related: Product Strategy, Performance Management and Strategic Decision-Making. Guides: product strategy, performance management and strategic decisions.

• Planning — quarterly drafting.
• Check-ins — weekly progress and blockers.
• Prioritising — saying no to off-goal work.
• Reporting — progress to leadership.
• Scoring — end-of-cycle reflection.
• Coaching — helping teams write better goals.

"Committed vs aspirational OKRs?"

Committed ones must be met; aspirational ones are stretch goals where partial success is expected.

"How long should an OKR cycle be?"

Often quarterly for teams, with annual company objectives.

Table: A first-90-days plan (editorial guidance)

Start by understanding existing goals and whether the data exists to measure outcomes. Help leaders choose a few objectives, then coach teams to write outcome key results. Establish weekly check-ins and end the first cycle with honest scoring and a retrospective.

AI tools can draft OKRs from strategy documents, suggest measurable key results and summarise weekly progress from dashboards and updates. That reduces admin and helps teams write more consistent goals. The danger is generic OKRs that sound right but don't reflect real priorities, or progress summaries that hide problems.

Leaders still need to choose what matters and have honest conversations about trade-offs. AI-assisted performance tools also raise fairness and privacy questions when goals feed into reviews. In interviews, show how you'd use AI to make the OKR process lighter while protecting focus, honesty and fairness.

Keep check-ins short — fifteen to twenty minutes. For each key result, the owner shares current value, confidence of reaching the target (for example, on a 1–10 scale) and any blockers. Focus discussion on key results where confidence dropped and decide actions. Avoid turning it into a status report of tasks. Record changes in confidence over time; falling confidence early in a cycle is valuable information that lets the team change course while there's still time.

Use OKRs as one input into performance conversations, not a formula. Discuss how the person contributed, the quality of their decisions, what they learned and how they helped others — especially for ambitious key results that landed at 0.6. Separate committed goals, which should usually be met, from aspirational ones. This keeps people setting bold goals instead of safe ones.

"OKRs are a to-do list." They describe outcomes; tasks belong in plans and backlogs.

"Everyone needs individual OKRs." Team OKRs usually work better and encourage collaboration.

"Scoring 1.0 is the goal." For ambitious OKRs, consistently scoring 1.0 suggests goals are too safe.

"OKRs replace KPIs." KPIs track ongoing health; OKRs focus effort on change. Most organisations need both.

• Too many OKRs.
• Task lists as key results.
• Rigid top-down cascades.
• Set and forget.
• Bonuses tied mechanically to scores.

OKR definitions come from What Matters; feature usage from Pendo; north star guidance from Amplitude; and India pay from AmbitionBox (read October 2026). The examples, check-in guidance and history are editorial. Science of Apps publishes the free test linked here. Last reviewed October 2026.

• Objective — a qualitative description of what you want to achieve.
• Key result — a measurable outcome showing progress.
• Alignment — connecting team goals to company goals.
• Check-in — a regular review of progress and confidence.
• Aspirational OKR — a stretch goal with partial success expected.