What Are OKRs?
OKRs — Objectives and Key Results — are a goal-setting framework used by companies of all sizes to align teams around ambitious, measurable outcomes. The structure is simple:
- Objective: A qualitative, inspiring statement of what you want to achieve. It answers "Where do we want to go?"
- Key Results: 2–5 specific, measurable outcomes that define what success looks like. They answer "How will we know we got there?"
OKRs work at the company level, team level, and individual level — and when cascaded properly, they align everyone's daily work with the organization's most important priorities.
The Difference Between OKRs and KPIs
This is one of the most common points of confusion. KPIs (Key Performance Indicators) measure ongoing health — they're the dials on your business dashboard. OKRs are about change — moving from where you are to somewhere meaningfully better. You might monitor a KPI every week as a health metric while setting an OKR to dramatically improve it over a quarter.
What a Good OKR Looks Like
Here's an example of a weak vs. strong OKR for an operations team:
| Weak OKR | Strong OKR | |
|---|---|---|
| Objective | Improve our processes | Build an operations foundation that scales with a doubling of headcount |
| KR 1 | Document some workflows | Document and publish SOPs for the 10 highest-frequency workflows by end of quarter |
| KR 2 | Reduce onboarding time | Reduce average new-hire time-to-productivity from 6 weeks to 3 weeks |
| KR 3 | Use better tools | Evaluate and select a project management platform, with 80% team adoption within 30 days of launch |
How to Write OKRs That Drive Action
For Objectives:
- Make them inspirational but realistic — a good objective creates momentum
- Use active language: "Build," "Establish," "Transform," "Become"
- Keep to 3–5 objectives per level (company, team, individual) per quarter
- Each objective should matter enough that achieving it would genuinely move the business forward
For Key Results:
- Every KR must be measurable — if you can't score it 0–1.0, rewrite it
- Focus on outcomes, not activities (not "hold 5 training sessions" but "increase team proficiency score from 60% to 85%")
- If all KRs are easily achievable, the objective isn't ambitious enough
- Aim for 60–70% achievement as the "success" threshold — if you're hitting 100% every time, your targets are too conservative
The OKR Cycle: Quarterly Rhythm
OKRs work best on a quarterly cadence with a simple rhythm:
- Week 1 of quarter: Set and socialize OKRs at all levels
- Every 2–4 weeks: Brief check-in to score progress and surface blockers
- End of quarter: Final scoring, honest retrospective, learnings fed into next quarter's planning
The retrospective is critical. Score each KR (0.0–1.0), discuss what drove results and what didn't, and use those insights to write better OKRs next cycle.
Why OKR Programs Fail — and How to Avoid It
- Too many OKRs: If everything is a priority, nothing is. Keep it focused.
- Set-and-forget: OKRs need a regular check-in cadence — otherwise they're just aspirations in a document.
- Top-down only: The best OKR programs involve teams in crafting their own key results, not just receiving mandates from leadership.
- Tying OKRs to performance reviews: This kills ambition. People play it safe when their job security depends on hitting targets. Keep OKRs separate from compensation reviews.
OKRs are a tool for focus and alignment, not a performance management system. Used correctly, they give every person in your organization a clear line of sight between their daily work and the company's most important goals.