OKR Framework

OKRs are the backbone of focus and alignment in fast-moving companies. Without a clear way to set ambitious goals and measure progress, product teams flail — working hard but not moving the needle on what matters. The trap is mistaking activity for impact.

The actual job of OKRs is to create a shared roadmap of outcomes that matter — not just outputs or busywork. If you cannot name what success looks like in numbers, you are flying blind.

This lesson teaches you how to write, use, and evaluate OKRs that keep your product, team, and company moving forward.

Why OKRs matter more than ever

The story I tell PMs is this: Imagine Headless Mike, a chicken in the USA that lived 18 months without a head because his caretakers fed him. Without clear objectives and metrics, your product journey looks like Mike’s life — dependent on external forces, directionless, and short-lived.

OKRs give you the feeding tools — the structure to nourish your product vision and execution.

India’s startup ecosystem is scaling rapidly. Companies like Razorpay, Swiggy, and Meesho use OKRs to stay aligned across fast-growing teams and shifting priorities. Without OKRs, you risk chasing every shiny new idea or stakeholder ask, losing focus on what actually moves the business.

What are OKRs?

OKR stands for Objectives and Key Results.

• Objective: A qualitative, aspirational goal you want to achieve in a set timeframe. It should be inspiring and push the team beyond the status quo.
• Key Results: Quantitative, measurable outcomes that show progress toward the Objective. They should be specific, numeric, and objectively graded.

This is what a good OKR looks like:

The Objective sets the destination. The Key Results are the mile markers.

How OKRs differ from KPIs

Many confuse OKRs with KPIs. Both track performance, but they serve different purposes.

KPIs tell you how the machine is running. OKRs tell you how to improve or grow the machine.

In India, companies often use KPIs for daily operations and OKRs for quarterly strategic alignment.

The anatomy of a good OKR

OKRs have distinct characteristics that make them effective:

• Ambitious but achievable: Stretch goals that push teams but are not impossible.
• Clear and measurable: Key Results are numeric, with no ambiguity.
• Time-bound: Usually set quarterly to keep urgency.
• Outcome-focused: Key Results measure results, not tasks.
• Aligned: OKRs cascade from company to team to individual levels.

A classic mistake is writing Key Results as tasks, e.g., "Ship feature X," instead of outcomes, e.g., "Increase new user sign-ups by 10% due to feature X."

Establishing OKRs in your organization

Setting OKRs is a collaborative process. Here’s what I tell PMs to do:

1. Brainstorm with stakeholders: Identify constraints, dependencies, and what will move the needle next quarter.
2. Pick 3-5 Objectives: Too many dilute focus.
3. Assign 3-5 Key Results per Objective: Enough to measure progress without overcomplicating.
4. Score progress regularly: Usually monthly check-ins.
5. Separate OKRs from performance reviews: OKRs are about learning and stretch, not punishment.

In practice, a well-set OKR with 70% completion is a success. 100% means you probably didn’t stretch enough.

The OKR formula

The formula answers three questions:

• What do you want to accomplish? (Objective)
• How will you accomplish it? (Key Results)
• How will you know you accomplished it? (Measurement)

This formula drives clarity:

Objective: Increase customer retention by Q3
Key Result 1: Reduce churn from 10% to 7%
Key Result 2: Increase weekly active users from 30k to 40k

How to use OKRs effectively

OKRs are not “set it and forget it.” The trap is to write them at the start of the quarter and ignore them until the end.

Instead:

• Hold weekly or biweekly OKR check-ins.
• Adjust Key Results if priorities shift — OKRs are flexible.
• Use OKRs to prioritize work — if a project doesn’t contribute to an OKR, question its value.
• Communicate OKRs transparently across teams.
• Celebrate progress and learn from misses.

Real-world example: Uber’s OKRs for driver growth

Uber’s product and operations teams used OKRs to align on their goal of becoming the most promptly available ride-sharing service.

Objective 1: Increase Drivers in the Uber System
Key Results:

• Increase driver base in each region by 20%
• Increase weekly driver session hours to 26 hours in all active regions

Objective 2: Increase geographical coverage of drivers
Key Results:

• Achieve 100% coverage in San Francisco
• Achieve 75% coverage in all active cities
• Decrease pickup time to less than 10 minutes in peak hours

These OKRs cascaded down to local teams, engineering, and marketing, ensuring every effort contributed to the larger goal.

OKR best practices

Atlassian, a company known for OKRs, shares these best practices:

• Give more preference to customer outcomes.
• Prioritize the most important objectives first.
• Do not skimp on ambition — OKRs should stretch you.
• Tie OKRs tightly to company strategy.
• Keep the number of Objectives and Key Results manageable.
• Assign owners to every Key Result for accountability.
• Evaluate OKRs at the end of the cycle and learn from what worked and what didn’t.

Common OKR pitfalls

• Writing Key Results as tasks instead of measurable outcomes.
• Setting too many Objectives or Key Results, causing dilution.
• Using OKRs as performance review tools, which kills ambition.
• Ignoring OKRs after setting them.
• Misalignment between team and company OKRs.
• Setting vague or unmeasurable Objectives.

SlackChat: OKR check-in at a SaaS startup

FieldExercise: Write your first OKR (15 minutes)

Pick a product or team you are part of. Write down:

1. One Objective — a clear, aspirational goal for the next quarter.
2. Three Key Results — numeric outcomes that will demonstrate progress.
3. Share your OKR with a peer and get feedback on clarity and measurability.

If you struggle, pick a simple goal like increasing user engagement or reducing churn.

JudgmentExercise

MeetingScene: The OKR debate at a scaleup

FromTheField: Why I trust OKRs to align teams

Where to go next

• If you want to deepen your understanding of product metrics: Metrics and KPIs
• If you want to build a strategic product roadmap: Product Vision and Strategy
• If you want to practice user research for better goal-setting: User Research Methods
• If you are preparing for PM interviews and want to master prioritization: PM Interviews