# Okr Design

> OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition with quarterly accountability). Triggers on OKR design, OKR setting, key result design, OKR scoring, mid-quarter recalibration, OKR cascading, outcomes vs outputs, quarterly planning, goal setting. Also triggers when a team's OKRs are always hit and producing no learning, when OKRs are demoralizing because they were set as fantasy, or when the team uses OKR vocabulary but the practice has decayed.

- Skill: `slipcast-dev/okr-design` (Agent Skill)
- Install (CLI): `npx get-skill add slipcast-dev/okr-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/slipcast-dev/okr-design/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: Slipcast-dev (https://skillmd.com/u/slipcast-dev)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/slipcast-dev/okr-design

---


# OKR Design

A senior product leader's playbook for OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the practical disciplines that distinguish OKRs from quarterly to-do lists or impossible-fantasy goal-setting.

OKRs are accountability infrastructure. When designed well, they produce a quarterly rhythm of ambitious goal-setting, mid-quarter learning, end-of-quarter scoring, and adjustment for the next quarter. When designed badly, they become a tax on the team that produces no signal: sandbagged OKRs that always hit 100% (no ambition, no learning), aspirational fantasy OKRs that nobody can hit (demoralizing, ignored after week 2), or vague OKRs that the team scores generously regardless of outcome.

This skill is OKR design as practical methodology. The teams that benefit from OKRs are the ones that hold the discipline: outcomes over outputs, key results that actually measure the outcome, scoring honestly even when uncomfortable, recalibrating mid-quarter when warranted, and using the OKR review cadence to drive learning rather than performance theater.

The voice is the senior product leader who has run OKRs in healthy organizations and watched the practice decay in others. Concrete, opinionated about what actually works, willing to call out the failure modes that conference talks gloss over.

When to use this skill: designing OKRs for the next quarter, auditing why current OKRs are not driving decisions, recalibrating an OKR practice that has decayed, or onboarding a team to OKRs that has never used them.

---

## What this skill is for

This skill spans OKR design and the operational rhythm around them. The PM-skill distinction:

- **`okr-design` (this skill)** is outcomes (results to be achieved).
- `roadmap-planning` is outputs (features and initiatives sequenced).
- `feature-launch-playbook` is post-ship execution.
- `product-analytics-setup` is measurement infrastructure (the metrics that key results depend on).
- `experiment-design` is the discipline for testing whether specific initiatives produce outcomes.
- `discovery-research-synthesis` informs which outcomes to pursue.

The audience: senior PMs, product directors, engineering leaders, executives setting org-wide OKRs, in-house teams operating in OKR-driven cultures.

What is not in scope: the broader strategic planning that decides which outcomes matter (other strategy frameworks); the execution of specific initiatives toward OKRs (covered by roadmap-planning, pm-spec-writing, feature-launch-playbook); the analytics infrastructure (covered by product-analytics-setup, analytics-strategy).

---

## If required data is unavailable

This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.

---

## Reference files

- [`references/objective-design-patterns.md`](references/objective-design-patterns.md) - Outcome-vs-output distinction. Strong vs weak objective characteristics. Worked examples across domains. The few-objectives discipline.
- [`references/key-result-design-patterns.md`](references/key-result-design-patterns.md) - Measurable, outcome-aligned, within-influence, time-bounded characteristics. Strong vs weak key results. The 3-5 KR rule. Worked examples.
- [`references/cascading-okrs-decisions.md`](references/cascading-okrs-decisions.md) - When to cascade strictly vs loosely. The middle path. Cascading anti-patterns. The honest disclosure about cascading difficulty.
- [`references/scoring-discipline.md`](references/scoring-discipline.md) - The 0.0-1.0 scale. The 60-70% target. Scoring honesty. What 100% and 30% mean. The compensation question.
- [`references/mid-quarter-recalibration.md`](references/mid-quarter-recalibration.md) - When to recalibrate vs adapt tactics. Strategic shift vs uncomfortable OKRs. The recalibration discipline.
- [`references/review-cadence-templates.md`](references/review-cadence-templates.md) - Weekly check-ins, mid-quarter review, end-of-quarter scoring, quarterly retrospective. Format and time investment per cadence.
- [`references/okrs-vs-roadmap-vs-metrics.md`](references/okrs-vs-roadmap-vs-metrics.md) - The three concepts and their relationships. Common conflations. The complete picture across all three.
- [`references/okr-anti-patterns.md`](references/okr-anti-patterns.md) - 8+ anti-patterns including OKR-as-roadmap, sandbagging, fantasy, vanity metrics, OKR theater, compensation coupling.
- [`references/common-okr-failures.md`](references/common-okr-failures.md) - 11+ failure patterns with diagnoses and cures.

---


## Conditional methods

Before applying a method below, read its linked section. For a narrow task select only relevant methods; for a full audit/design use the framework and relevant failure patterns. Existing references remain available for deeper details.

- Sandbagged vs aspirational-fantasy vs stretch: [method](references/domain-guide.md#sandbagged-vs-aspirational-fantasy-vs-stretch).
- Objective design: [method](references/domain-guide.md#objective-design).
- Key result design: [method](references/domain-guide.md#key-result-design).
- Cascading OKRs across the org: [method](references/domain-guide.md#cascading-okrs-across-the-org).
- Scoring discipline: [method](references/domain-guide.md#scoring-discipline).
- Mid-quarter recalibration: [method](references/domain-guide.md#mid-quarter-recalibration).
- The OKR review cadence: [method](references/domain-guide.md#the-okr-review-cadence).
- OKRs vs roadmap items vs metrics: [method](references/domain-guide.md#okrs-vs-roadmap-items-vs-metrics).
- Common failure modes: [method](references/domain-guide.md#common-failure-modes).
- The framework: 12 considerations for OKR design: [method](references/domain-guide.md#the-framework-12-considerations-for-okr-design).
- Closing: OKRs are accountability infrastructure: [method](references/domain-guide.md#closing-okrs-are-accountability-infrastructure).

