What it is
OKRs pair a qualitative Objective — an ambitious, memorable statement of what you want to achieve — with a small set of quantitative Key Results that define what success looks like. For example: Objective — “Make onboarding effortless for new teams.” Key Results — “Reduce time-to-first-value from 6 days to 2 days,” “Increase week-1 activation rate from 38% to 55%,” “Cut onboarding support tickets by 30%.”
The objective gives direction and motivation; the key results make progress measurable and remove ambiguity about whether the goal was actually hit. Popularized by Andy Grove at Intel and later at Google, OKRs are typically set on a quarterly or annual cadence.
When to use it
OKRs work well when a team or company needs a shared, time-boxed way to align on priorities across multiple groups — they’re most effective when key results are genuinely outcome-based (a change in user or business behavior) rather than a checklist of shipped features. They’re less useful for pure day-to-day execution tracking, which is better handled by a regular task or sprint board.
Common pitfalls
- Key results that are really just a task list. “Ship feature X” is an output, not a result — a proper key result measures the effect that shipping X was supposed to have.
- Setting too many OKRs. More than 3–5 objectives per team dilutes focus and turns OKRs into a restatement of the entire roadmap.
- Treating 100% completion as the goal. Google’s own guidance treats 60–70% average attainment on ambitious OKRs as healthy — hitting 100% every quarter usually means the targets were sandbagged.
- Disconnecting OKRs from the roadmap. If OKRs live in a separate document nobody references during planning, they become a quarterly ritual instead of a real prioritization tool.