Write Okrs

---
name: write-okrs
description: Use when setting quarterly or annual goals for a team, department, or company to align effort with strategy
source: John Doerr "Measure What Matters" (2018); Google OKR methodology (re-OKR guide)
tags: [okrs, goal-setting, alignment, performance, planning]
related: [apply-management-by-objectives, apply-smart-goals, apply-goodharts-law]
verified: true
---

# Write OKRs

Create Objectives and Key Results that focus a team on outcomes that matter, not activity that feels busy.

## Why This Is Best Practice

**Adopted by:** Google (since 1999), Intel, LinkedIn, Spotify, and thousands of companies via Doerr's framework
**Impact:** Google attributes much of its early hyper-growth to OKR discipline; teams using OKRs show 22% higher goal attainment than KPI-only teams (Perdoo 2023 study)

**Why best:** OKRs force the distinction between aspiration (Objective) and evidence of success (Key Result). Unlike traditional MBOs, they are public, time-boxed, and graded — creating accountability without micromanagement.

## Steps

1. **Draft the Objective** — Write one sentence describing a qualitative, inspiring outcome. It should answer "Where do we want to go?" and be achievable in one quarter. Use strong verbs: "Establish," "Become," "Deliver," "Win."
2. **Write 2–5 Key Results** — Each KR must be measurable, binary-passable (yes/no or a number), and directly prove the Objective was met. Format: "[Verb] [metric] from [baseline] to [target] by [date]."
3. **Stress-test each KR** — Ask: "If we hit this number but the Objective clearly failed, is the KR wrong?" If yes, revise. KRs must collectively prove the Objective.
4. **Set ambitious targets** — OKR targets should feel like 70% achievement is a strong result. If 100% feels easy, the target is a task list, not an OKR.
5. **Align vertically and horizontally** — Check that team OKRs ladder up to company OKRs. Check peer teams' OKRs for conflicts or missing dependencies.
6. **Assign owners** — Each KR has one accountable owner. Teams can contribute, but one person drives measurement and reporting.
7. **Establish check-in cadence** — Schedule weekly or bi-weekly confidence scores (0–10) and a written blocker. At quarter end, grade each KR 0.0–1.0.

## Rules

- One Objective per quarter per team. Two maximum in exceptional circumstances.
- Key Results measure outcomes, not outputs. "Launch feature X" is a task; "Reduce churn from 5% to 3%" is a KR.
- OKRs are public within the organization — hiding them defeats alignment.
- Do not tie OKRs directly to compensation; it incentivizes sandbagging targets.
- Grade every OKR at quarter end — ungraded OKRs destroy the culture of accountability.

## Examples

**Objective:** Become the fastest-activating product in our category.
**KR1:** Reduce time-to-first-value from 14 days to 3 days by March 31.
**KR2:** Achieve 60% of new signups completing the core workflow within 24 hours (up from 31%).
**KR3:** Score 8+ on activation satisfaction in post-onboarding NPS (currently 5.2).

## Common Mistakes

- **Task-list KRs** — "Complete three customer interviews" is an output, not an outcome; it will be hit even if nothing improves.
- **Too many OKRs** — More than five KRs per Objective splits focus; teams optimize for easy wins.
- **Set-and-forget** — OKRs without weekly check-ins decay into decoration on a slide deck.

## When NOT to Use

- Do not write OKRs for a team in crisis mode (incident recovery, emergency pivot, leadership transition) where the priority changes week-to-week and locking to a quarterly target creates misaligned incentives.
- Do not apply OKRs to compliance, legal, or safety obligations that must be 100% met regardless of ambition — these belong in a separate baseline commitments list, not in stretch OKRs where 70% attainment is celebrated.
- Do not use OKRs as a substitute for strategy; if the team does not yet have clarity on what problem they are solving or who they serve, writing OKRs will lock in the wrong direction before the strategy is validated.