How many OKRs should a startup have per quarter?

Most startups run 1–3 company-level objectives per quarter, each with 3–5 key results. Less is more — too many OKRs dilute focus and make it impossible to prioritize. Early-stage startups (pre-Series A) often work best with a single company objective that the whole team rallies around.

What is the difference between a goal and an OKR?

A goal is vague and directional: 'grow faster.' An OKR is structured: the Objective is qualitative and inspiring ('become the top tool for freelance designers'), while Key Results are specific, measurable, and time-bound. The KRs tell you objectively whether the objective was achieved.

Should OKRs be tied to compensation and performance reviews?

Generally no — this is a common OKR anti-pattern. When OKRs are tied to bonuses, people set conservative targets they can easily hit rather than ambitious ones they might miss. OKRs work best as an alignment and goal-setting tool, kept separate from individual performance management.

How often should a startup change its OKRs?

OKRs are typically set quarterly, which balances focus with adaptability. Some early-stage startups use 6-week cycles when iterating rapidly. Annual OKRs are too slow for startups. The key is consistency: commit to the cycle, run proper retros, and let the process improve over time.

How to Set Company OKRs That Actually Work

What Are OKRs and Why Do They Work for Startups?

OKRs (Objectives and Key Results) are a goal-setting framework used by Intel, Google, and thousands of startups to create company-wide alignment and measurable progress. The premise is simple: define where you want to go (Objective), then define how you’ll know you got there (Key Results).

For startups, OKRs solve two critical problems: focus (what do we actually work on this quarter?) and alignment (is every team pulling in the same direction?).

The concept was developed at Intel by Andy Grove and popularized at Google by investor John Doerr, who introduced it to Larry Page and Sergey Brin in 1999. It’s now the default operating rhythm for most venture-backed companies.

Step 1: Define Your Company-Level Objective

The Objective is qualitative and inspirational. It answers: what does winning look like this quarter?

Bad objective: “Improve product quality” Good objective: “Become the analytics tool that e-commerce founders trust to make pricing decisions”

Rules for a strong Objective:

One sentence, no numbers
Ambitious but achievable in one quarter
Points the whole team in a clear direction
Memorable — if your team can’t recall it without looking it up, it’s not clear enough

Most startups should run 1–3 objectives per quarter. More than 3 is a sign you haven’t made real prioritization decisions.

Step 2: Write 3–5 Key Results Per Objective

Key Results are quantitative. They measure whether the Objective was achieved.

Bad KR: “Launch new onboarding flow” ← this is a task, not a result Good KR: “Increase 7-day activation rate from 34% to 55%”

A strong KR has:

A metric (activation rate)
A baseline (34%)
A target (55%)
A clear, objective way to measure it

If you can’t measure it without interpretation, it’s not a Key Result.

Example OKRs for a SaaS Startup

Objective: Make our onboarding the fastest path to value in the category

Key Result	Baseline	Target
7-day activation rate	34%	55%
Time to first value action	4.2 days	< 2 days
30-day retention	61%	72%
NPS score	28	45

Step 3: Cascade to Team-Level OKRs

Once company OKRs are set, each team writes their own OKRs that support company-level key results.

Engineering owns the activation rate KR and breaks it into product work
Marketing owns a new customer volume KR
Customer Success owns the retention KR

Rule: every team OKR should map to at least one company KR. OKRs that don’t connect to company priorities are a sign of organizational misalignment.

Step 4: Weekly Check-in Rhythm

Every week, each team updates a confidence score (0–10) for each KR:

7–8: On track, likely to hit target
5–6: At risk, needs attention
< 5: Blocked or off-track — needs immediate discussion

Keep check-ins async. A quick update in your project management tool is faster and generates less meeting fatigue than another standing call. Reserve live discussion time for scores below 5.

Step 5: Mid-Quarter Review

At week 6 of a 12-week quarter, review OKRs as a leadership team. Ask:

Which KRs are at risk and why?
Is the strategy right, or do we need to change approach?
Are any KRs no longer relevant given what we’ve learned?

It’s acceptable to adjust a KR mid-quarter if business context has significantly changed. Don’t adjust them to make hitting targets easier — that defeats the purpose of setting ambitious goals.

Step 6: Quarterly Retrospective

At quarter end, score each KR from 0.0 to 1.0:

The ideal score, per John Doerr and Google’s OKR practice, is 0.6–0.7. Consistently scoring 1.0 means targets are too conservative. Never exceeding 0.4 means targets are unrealistic or execution is broken.

Run a 30-minute retro: what worked, what didn’t, what carries into next quarter? Document the answers — they compound into institutional knowledge over time.

Common OKR Mistakes

Writing tasks as KRs: “Launch X” is a task; “Increase Y by Z%” is a key result
Too many objectives: More than 3 means you haven’t prioritized
Set and forget: OKRs need weekly maintenance or they become irrelevant artifacts
Tying OKRs to compensation: This kills ambition — people optimize for certainty over impact
Top-down only: The best OKRs involve direction from leadership and input from the teams doing the work

Key Takeaway

OKRs work when they create genuine alignment and force hard prioritization. Start with one company objective, three strong key results, and a consistent weekly check-in rhythm. Run two quarters before adding complexity. The discipline of setting measurable targets and reviewing them honestly — even when results are disappointing — is the real value, not the framework itself.