What is the difference between an Objective and a Key Result?

An Objective is a qualitative, inspiring statement of what you want to achieve (the 'Where are we going?'). A Key Result is a quantitative, measurable metric that proves whether you achieved the objective (the 'How will we know we got there?').

Should OKRs be tied to employee compensation or bonuses?

No. Tying OKRs to compensation encourages sandbagging—employees will intentionally set safe, easily achievable goals to guarantee their bonuses. OKRs should be ambitious 'stretch' goals designed to push the product forward.

What is the ideal achievement rate for an OKR?

The ideal achievement rate is around 70%. If a team consistently hits 100% of their Key Results, it means their OKRs are not ambitious enough and they are operating within their comfort zone.

Framework

OKR Framework for Product Teams

TL;DR: Objectives and Key Results (OKRs) are an alignment framework that connects company strategy with product execution. The Objective is qualitative and inspirational; the Key Results are quantitative and measurable. When implemented correctly, OKRs force teams to focus on outcomes (moving metrics) rather than outputs (shipping features).

Key Implementation Rules

Limit Focus: Maximum of 3 Objectives per quarter, with a maximum of 3-5 Key Results per Objective. Any more creates dilutive chaos.
The 70% Rule: The ideal OKR achievement rate is 70%. Hitting 100% means the goals were safe tasks, not ambitious stretch goals.
Bi-Weekly Cadence: OKRs are not "set and forget." They must be updated and graded bi-weekly during sprint planning.

The Anatomy of an OKR

Originally pioneered at Intel and popularized globally by Google, the OKR framework seems simple on paper but is notoriously difficult to implement correctly within high-pressure Indian startup environments.

The Objective (The "What")

The Objective is a qualitative statement of intent. It should be memorable, inspiring, and easily understood by anyone in the company, from the CEO to the junior customer support agent. It should not contain numbers.

Bad Objective: "Increase Q2 revenue." (Boring, lacks direction).
Good Objective: "Dominate the Tier-2 B2B market onboarding experience." (Inspiring, gives clear strategic focus).

The Key Results (The "How we know")

Key Results must be quantifiable. If a Key Result does not contain a number, it is not a Key Result. They measure the outcome of your work. The biggest mistake product teams make is treating Key Results like a feature to-do list.

Bad KR (Output): "Ship the new vernacular onboarding flow." (This is a task/initiative. Shipping a feature doesn't mean it worked).
Good KR (Outcome): "Increase Day-1 Activation rate from 22% to 35% for Hindi-speaking users." (This measures whether the feature you shipped actually solved the problem).

Cascading OKRs in Indian Startups

Indian startups often struggle with OKR bloat. Leadership spends three weeks drafting 15 company-level OKRs, forcing product pods to scramble to align their backlogs. This top-down dictation destroys autonomy.

Proper cascading should be bi-directional. Leadership sets 1 or 2 annual Company OKRs (e.g., "Achieve path to profitability"). The Product Pods then look at that annual goal and draft their own Quarterly OKRs to support it. The pods tell leadership *how* they plan to move the needle, rather than leadership telling the pods *what* features to build.

5 Example Product OKRs by Industry

To move beyond theory, here are fully fleshed-out OKR examples tailored to common Indian tech sectors:

1. Fintech (Wealthtech App)

Objective: Make investing a daily habit, not a monthly chore.

KR1: Increase Weekly Active Users (WAU) from 150k to 250k.
KR2: Increase the percentage of users checking the "Market News" tab daily from 5% to 20%.
KR3 (Counter-measure): Ensure average SIP size does not drop below ₹1,500 (prevents boosting engagement at the cost of portfolio quality).

2. B2B SaaS (HR Platform)

Objective: Prove enterprise readiness to eliminate the "too small for us" sales objection.

KR1: Achieve SOC2 Type II compliance by end of Q2 (Binary: 0 or 100%).
KR2: Decrease 95th percentile dashboard load time for accounts with >5,000 employees from 4.2s to 1.5s.
KR3: Increase Enterprise trial user completion of the "SSO Setup" milestone from 10% to 40%.

3. Consumer (Hyperlocal/Grocery)

Objective: Transform our delivery app from a "weekend luxury" into a "daily necessity."

KR1: Increase frequency of orders per MAU from 2.1 to 3.5 per month.
KR2: Grow the "Morning Essentials" category from 15% to 35% of total GMV.
KR3: Maintain average delivery time under 12 minutes during peak morning hours.

4. EdTech

Objective: Fix our leaky bucket and prove students actually complete our courses.

KR1: Increase Module 1 completion rate from 22% to 60%.
KR2: Reduce the average time taken to submit the first assignment from 14 days to 4 days.
KR3: Achieve an NPS of >40 for the newly launched "Live Doubt Clearing" feature.

5. E-commerce (D2C Brand)

Objective: Eradicate checkout friction to maximize ad spend ROI.

KR1: Reduce cart abandonment rate from 72% to 55%.
KR2: Increase the adoption rate of "One-Click UPI" from 10% to 45% of all transactions.
KR3: Decrease average page load time on mobile web from 3.8s to 1.8s.

Tracking OKRs (Tools)

Do not track OKRs in a forgotten Excel sheet. They must live where the engineering work happens. Modern tools like Linear or Notion allow you to create an "Objective" object and link individual engineering epics directly to it. When an engineer picks up a ticket, they should be able to click exactly one level up to see the Key Result it is supposed to move.

Are Your OKRs Just a Feature Backlog?

If your Key Results are just a list of features to ship, your product team is operating as a feature factory. Let us help you transition to outcome-based quarterly planning.

Hire us →