home / skills / wdavidturner / product-skills / okrs

okrs skill

/skills/okrs

This skill helps teams set focused quarterly objectives and measurable key results, enabling alignment, weekly check-ins, and fast learning.

npx playbooks add skill wdavidturner/product-skills --skill okrs

Review the files below or copy the command above to add this skill to your agents.

Files (17)
SKILL.md
4.7 KB
---
name: okrs
description: Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at Google) creates alignment, focus, and learning cycles. Christina Wodtke's Radical Focus approach emphasizes simplicity and avoiding common pitfalls.
---

# OKRs (Objectives and Key Results)

## What It Is

OKRs are a goal-setting framework that creates focus, alignment, and a learning cycle for teams and organizations. The core insight: **set one ambitious objective per quarter with 2-3 measurable key results, then check in weekly to maintain focus.**

The key shift: Move from tracking activities ("What are we doing?") to tracking outcomes ("What progress are we making toward our goals?").

OKRs are a vitamin, not a medicine. They supercharge companies that already have their fundamentals in place (strategy, empowered teams, psychological safety). They won't fix broken organizations - they'll just reveal what's broken.

**Credit:** Originated by Andy Grove at Intel. Popularized by John Doerr who brought it to Google. Christina Wodtke's *Radical Focus* provides the most practical implementation guidance.

## When to Use It

Use OKRs when you need to:

- **Focus the team** on the single most important thing for the quarter
- **Align the organization** so everyone knows what matters most
- **Create accountability** with measurable outcomes (not just activities)
- **Build a learning cycle** through weekly check-ins and quarterly retrospectives
- **Scale leadership** so founders/executives don't need to micromanage
- **Accelerate progress** by avoiding the "peanut butter" problem of spreading effort too thin

## When Not to Use It

- You don't have a clear strategy (OKRs reveal missing strategy, they don't replace it)
- Your company lacks psychological safety (people will sandbag or game the metrics)
- You want to track ALL the work (OKRs are for priorities, not comprehensive task lists)
- Teams aren't empowered to decide HOW to achieve outcomes

## Patterns

Detailed examples showing how to apply OKRs correctly. Each pattern shows a common mistake and the correct approach.

### Critical (get these wrong and you've wasted your time)

| Pattern | What It Teaches |
|---------|-----------------|
| [key-results-are-tasks](patterns/key-results-are-tasks.md) | Key results must be outcomes, not activities or deliverables |
| [too-many-okrs](patterns/too-many-okrs.md) | One objective per quarter — not five, not ten |
| [missing-strategy](patterns/missing-strategy.md) | OKRs without strategy is just goal theater |
| [boring-objectives](patterns/boring-objectives.md) | Objectives should make you want to get out of bed |
| [no-weekly-checkins](patterns/no-weekly-checkins.md) | Set and forget kills OKRs — the cadence is the system |

### High Impact

| Pattern | What It Teaches |
|---------|-----------------|
| [sandbagging-goals](patterns/sandbagging-goals.md) | Goals should make you uncomfortable but not doomed |
| [fluffy-objectives](patterns/fluffy-objectives.md) | Vague objectives like "improve quality" mean nothing |
| [grading-without-learning](patterns/grading-without-learning.md) | The retrospective matters more than the score |
| [slow-approval-process](patterns/slow-approval-process.md) | Approval cycles that eat weeks defeat the purpose |
| [okrs-for-everything](patterns/okrs-for-everything.md) | Keep-the-lights-on work doesn't belong in OKRs |
| [cascading-trap](patterns/cascading-trap.md) | Alignment doesn't mean every team mirrors company OKRs |

### Medium Impact

| Pattern | What It Teaches |
|---------|-----------------|
| [skipping-celebrations](patterns/skipping-celebrations.md) | Friday celebrations build momentum and morale |
| [perfect-measurement](patterns/perfect-measurement.md) | Don't let measurement precision block progress |
| [annual-okrs](patterns/annual-okrs.md) | Quarterly is the sweet spot for most teams |


## Deep Dives

Read only when you need extra detail.

- `references/okrs-playbook.md`: Expanded framework detail, checklists, and examples.

## Resources

**Books:**
- *Radical Focus* (2nd Edition) by Christina Wodtke — the practical guide
- *Measure What Matters* by John Doerr — the Google story
- *High Output Management* by Andy Grove — where it all started

**Related frameworks:**
- *The Fearless Organization* by Amy Edmondson — psychological safety (required for honest OKR updates)
- *Five Dysfunctions of a Team* by Patrick Lencioni — fixing team issues that block OKR success

**Articles:**
- Christina Wodtke's eleganthack.com — ongoing OKR insights

Overview

This skill helps teams create, refine, and operate OKRs (Objectives and Key Results) to focus priorities, align stakeholders, and measure meaningful outcomes each quarter. It emphasizes one ambitious objective per quarter with 2–3 measurable key results and a weekly cadence of check-ins. The approach draws on practical guidance to avoid common OKR pitfalls and build a learning loop.

How this skill works

The skill guides you through framing a clear objective, converting desired outcomes into measurable key results, and setting a practical cadence for weekly check-ins and quarterly reviews. It flags common mistakes—like using tasks as key results or creating too many objectives—and offers corrective patterns and examples. It also helps assess organizational readiness (strategy clarity, team empowerment, psychological safety) before rolling out OKRs.

When to use it

  • When you need to focus the team on a single, high-impact priority for the quarter
  • When you want alignment across teams so everyone understands top company goals
  • When you need measurable outcomes instead of activity lists
  • When you want to create a predictable learning cycle with weekly check-ins and quarterly retrospectives
  • When leadership needs to scale results without micromanaging

Best practices

  • Set one objective per quarter with 2–3 outcome-focused key results
  • Make objectives motivating and specific; key results must be measurable outcomes, not tasks
  • Run weekly check-ins to surface blockers and update progress, not to re-define goals
  • Use quarterly retrospectives to learn, adjust strategy, and avoid grading without learning
  • Avoid slipping operational maintenance into OKRs — reserve OKRs for priorities that move the needle

Example use cases

  • Quarterly product focus: increase core user activation with measurable lift in activation rate and reduced time-to-first-value
  • Cross-functional alignment: align marketing, product, and sales on a single revenue-driving objective
  • Leadership scaling: give teams clear outcomes so executives can focus on strategy, not task lists
  • Startup planning: force prioritization when resources are limited to avoid the peanut-butter problem
  • Performance learning: run a quarterly experiment objective and use the retrospective to capture learnings

FAQ

How many OKRs should a team have each quarter?

Aim for one objective per team per quarter with 2–3 measurable key results; more objectives dilute focus.

What makes a good key result?

A good key result measures an outcome (e.g., % increase in retention), is time-bound, and is objectively measurable—not a checklist of tasks.