How many OKRs should a team have?

2-3 objectives, 3-5 KRs each. More than 4 objectives means nothing is a priority.

Should we score OKRs 0-1 or pass/fail?

0-1 with 0.7 as the target. Pass/fail hides partial progress and encourages sandbagging.

Are OKRs still relevant in 2026?

Yes for strategic change management. The 'OKR fatigue' many companies feel comes from using OKRs as KPIs and cascading rigidly — not from the tool itself.

OKRs vs KPIs: When to Use Which (2026)

OKRs and KPIs solve different problems. Confusing them produces the worst of both — bureaucratic goals no one hits, and metrics no one improves.

OKRs vs KPIs: The Distinction Most Startups Get Wrong

OKRs (Objectives and Key Results) are for change — driving a specific transformation over a quarter. KPIs (Key Performance Indicators) are for stability — measuring ongoing health of the business. Most startups conflate them, producing OKRs that are actually just KPIs ('grow ARR to $5M') and KPI dashboards no one looks at because everyone is focused on OKRs.

The core difference

OKRs: time-bound (quarterly usually), aspirational, change-oriented. 'Launch enterprise tier and close 5 pilot customers by end of Q3.' KPIs: continuous, expected performance, health-oriented. 'ARR growth rate, gross margin, NRR, sales cycle length.' Rule of thumb: if the metric was true last quarter and will be true next quarter, it's a KPI. If it represents a specific transformation you're trying to achieve, it's an OKR.

When OKRs are the wrong tool

Business-as-usual metrics: 'Maintain 95% GRR' is not an OKR — it's a KPI. Uncontrollable outcomes: 'Close $10M in new ARR' without specific change initiatives is a sales quota, not an OKR. Too many at once: 5+ OKRs per team means nothing is a priority. Over-quantified: OKRs measured to two decimal places optimize for the number, not the change. If your OKR review meetings feel bureaucratic, you're using OKRs as KPIs.

When KPIs are the wrong tool

Strategic initiatives: 'Enter the mid-market segment' can't be tracked with a single KPI — it needs an OKR with 3-5 KRs across product, sales, and marketing. New capabilities: 'Build sales-led motion' isn't a KPI, it's a company-defining OKR. Cultural changes: 'Improve engineering velocity' requires a set of experiments (OKR), not a single metric.

The healthy combination

Every team has both. KPIs on the always-visible dashboard: ARR, growth rate, gross margin, NRR, cash, headcount, uptime, NPS. OKRs on the quarterly focus doc: 2-4 strategic initiatives with 3-5 measurable KRs each. Review KPIs weekly (health check), review OKRs monthly (are we on track for the transformation), reset OKRs quarterly (what's the next change).

Cascading vs autonomous OKRs

Cascading: company OKRs → team OKRs → individual OKRs. Produces alignment but crushes bottom-up ideas and creates make-work when team OKRs are just repackaged company OKRs. Autonomous: teams write their own OKRs, aligned to company objectives but with their own KRs. Produces more ownership and better ideas but requires strong leadership judgment. Most companies do a hybrid — company objectives cascade, KRs are team-owned.

Common mistakes

Sandbagging OKRs to hit 100%: OKRs are aspirational — 70% is a healthy target, 100% means you set them too low. Tying OKR attainment to comp: destroys the aspiration by making people play safe. No KPIs at all: everything is an OKR, nothing is baseline health. No OKRs at all: everything is KPI maintenance, no strategic initiatives get executed. Both extremes fail.

Frequently asked questions

How many OKRs should a team have?: 2-3 objectives, 3-5 KRs each. More than 4 objectives means nothing is a priority.
Should we score OKRs 0-1 or pass/fail?: 0-1 with 0.7 as the target. Pass/fail hides partial progress and encourages sandbagging.
Are OKRs still relevant in 2026?: Yes for strategic change management. The 'OKR fatigue' many companies feel comes from using OKRs as KPIs and cascading rigidly — not from the tool itself.