What is the difference between OKRs and KPIs?

KPIs (Key Performance Indicators) monitor ongoing business health — they tell you how the business is running. OKRs set ambitious goals and align teams around what to change — they tell you what you are trying to improve. KPIs are continuous measurements; OKRs run on quarterly or annual sprints. Both are necessary and serve different purposes.

How many OKRs should a startup team have per quarter?

3–4 objectives per team maximum, each with 2–5 key results. More than that is not focus — it is a wish list. The primary value of OKRs is forcing prioritization: if everything is an OKR, nothing is. Early-stage startups should often limit themselves to 1–2 company-level objectives to stay focused on the one metric that matters most.

Should OKRs be tied to employee compensation?

No — this is one of the most common and damaging OKR mistakes. When OKRs are linked to bonuses, people set conservative, easy-to-hit targets and work defensively rather than ambitiously. OKRs are designed to encourage stretch goals where hitting 60–70% is considered a success. Tying them to pay changes the incentive structure entirely.

What is a good OKR score at the end of the quarter?

OKRs are typically graded 0–1.0. A score of 0.6–0.7 is considered healthy — it means targets were genuinely ambitious. Consistently scoring 1.0 means targets were too conservative. Scores below 0.3 suggest the targets were unrealistic or the team was under-resourced. The honest grading conversation at quarter-end is often more valuable than the score itself.

OKRs — Objectives and Key Results

What Are OKRs?

OKRs (Objectives and Key Results) are a goal-setting framework with two components:

Objective: A qualitative, inspiring description of what you want to achieve
Key Results: 2–5 measurable outcomes that define what “achieving the objective” looks like

Andy Grove developed the system at Intel in the 1970s, drawing on Peter Drucker’s “Management by Objectives.” John Doerr brought OKRs to Google in 1999, where they were adopted company-wide and have since become a standard in the startup world.

The Structure

Objective: [Inspiring qualitative goal]
  ↓
Key Result 1: [Measurable outcome — numbers only]
Key Result 2: [Measurable outcome — numbers only]
Key Result 3: [Measurable outcome — numbers only]

Example:

Objective: Make our customer onboarding genuinely delightful.

KR1: Increase 30-day retention of new users from 42% to 65%
KR2: Reduce time-to-first-value from 14 minutes to under 5 minutes
KR3: Achieve NPS ≥ 50 among users who completed onboarding in the past 30 days

Notice: the objective is aspirational and human. The key results are entirely numeric — no “improve,” “enhance,” or other weasel words.

What Makes a Good OKR

Objectives

Inspirational and meaningful — would motivate someone to get up on Monday
Not a task or a project (“launch feature X” is a task, not an objective)
Qualitative — describes a state of the world, not a metric
Slightly uncomfortable — should require real effort to achieve

Key Results

Measurable and verifiable — at the end of the period, there should be zero ambiguity about whether it was achieved
Outcome-based, not output-based — “Reach 10,000 users” vs. “Ship 5 new features”
Graded 0–1.0 — typically scored at 60–70% for “good” (if you always hit 1.0, your targets are too easy)
3–5 per objective — more than 5 dilutes focus

OKRs vs. KPIs

Dimension	OKRs	KPIs
Purpose	Set ambitious goals and align teams	Monitor ongoing business health
Timeframe	Quarterly or annual sprint	Continuous measurement
Ownership	Specific team or individual	Often whole company
Target	Slightly uncomfortable stretch	Realistic operational target
Graded?	Yes (0–1.0)	Typically no

KPIs tell you how the business is running. OKRs tell you what you’re trying to change about the business. Both are necessary; they serve different purposes.

OKR Cadence

Most companies run OKRs on a quarterly cycle with an annual planning layer:

Cadence	When	What
Annual	Q4 for following year	Company-level objectives for the year
Quarterly	Last 2 weeks of quarter	Team-level OKRs for next quarter
Weekly	Every Monday (check-in)	Progress update: confidence score + blockers
Quarterly review	Last week of quarter	Grade OKRs, run retrospective

Grading should be honest. Consistently scoring 1.0 means your targets are too conservative. 0.3–0.4 might mean they were unrealistic or poorly resourced.

Common OKR Mistakes

1. Turning OKRs into a to-do list

Bad KR: “Launch new onboarding flow” Good KR: “Increase 7-day activation rate from 30% to 50%“

2. Setting too many OKRs

More than 3–4 objectives per team is not focus — it’s a wish list. OKRs force you to choose what matters most.

3. Not separating OKRs from compensation

OKRs should not be directly tied to bonuses. When they are, people set easy targets and work defensively instead of ambitiously.

4. Fire-and-forget OKRs

Setting OKRs and reviewing them only at the end of the quarter misses the point. The weekly check-in keeps teams honest and surfaces blockers early.

5. Activities masquerading as outcomes

“Run 3 customer workshops” is an activity. “Increase customer satisfaction score from 6.2 to 7.5 based on post-workshop surveys” is an outcome.

OKRs for Early-Stage Startups

At pre-seed and seed, OKRs can feel like overhead — and they are if misapplied. But the discipline of writing explicit hypotheses (objectives) and measuring them (key results) maps directly onto the Build-Measure-Learn loop.

For very early-stage teams:

Limit to 1–2 company-level objectives
Run 4-week sprints instead of 12-week quarters
Focus entirely on the metric that proves product-market fit (usually retention or engagement)

Key Takeaway

OKRs are a forcing function for clarity and prioritization. Their real value isn’t the framework itself — it’s the conversations that happen when a team tries to agree on what matters most and how to know when they’ve achieved it. Done well, they replace vague ambition with shared, measurable direction.