Skip to content

rampstackco/claude-skills / skills/okr-design

okr-design

Verified

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.

references/key-result-design-patterns.md

View on GitHub
# Key result design patterns

Measurable, outcome-aligned, within-influence, time-bounded characteristics. Strong vs weak key results. The 3-5 KR rule. Worked examples.

Key results are where the OKR practice succeeds or fails operationally. Objectives can be inspiring without measurable; key results have to be measurable. Most OKR failure at the operational level shows up in the key result design.

---

## The four characteristics of strong key results

**Measurable.** A specific number, percentage, or testable threshold.

- "Increase first-week activation rate from 32% to 45%."
- "Reduce median time-to-first-value from 4.2 days to under 2 days."
- "Reach 80% completion rate on onboarding flow (up from 64%)."

**Outcome-aligned.** Achieving the key result actually moves the objective forward.

- For the activation objective, the key results above are aligned: they all measure aspects of activation.
- A key result like "ship the onboarding redesign" is not outcome-aligned; it measures the work, not the activation outcome.

**Within team influence.** The team can affect the key result through their work.

- "First-week activation rate" is influenced by onboarding design, welcome email content, in-product guidance. The team can affect it.
- "Total signups" depends primarily on marketing acquisition; the activation team's onboarding work affects it weakly. Not a strong key result for the activation team.

**Time-bounded.** The measurement window is the quarter (or appropriate sub-window).

- "Increase first-week activation rate from 32% to 45% by end of Q3."
- "Reach 80% completion rate by week 10 of the quarter."

The four characteristics together produce key results the team can commit to credibly and measure honestly.

---

## Strong key result examples by objective

**Objective: "Improve activation for new sign-ups so more reach value-realization in week one."**

Strong KRs:

- "Increase first-week activation rate from 32% to 45%."
- "Reduce median time-to-first-value from 4.2 days to under 2 days."
- "Reach 80% completion rate on onboarding flow (up from 64%)."
- "Reduce signup-to-first-key-action time from 8 minutes to under 4 minutes."

Each measures an aspect of activation. The team can influence each through their work. Each has a baseline and target.

**Objective: "Make support experience deflect predictable issues."**

Strong KRs:

- "Reduce ticket volume on the top 3 deflection-eligible categories by 40%."
- "Increase self-service resolution rate from 22% to 38%."
- "Maintain CSAT at or above 4.4/5 (no degradation while deflecting)."

The third KR matters: deflecting tickets without protecting CSAT could damage the experience; the KR keeps both in scope.

**Objective: "Establish enterprise-readiness foundations."**

Strong KRs:

- "Pass SOC 2 Type II audit with zero high-severity findings."
- "Complete admin role and permissions overhaul; reach 95% of enterprise-prospect compliance checklist items."
- "Onboard 3 design partners from the enterprise segment to the alpha enterprise build."

Each measures a foundation outcome the enterprise readiness depends on.

---

## Weak key result examples

**Vague.**

- "Improve activation significantly."
- "Reduce ticket volume."

No specific number; cannot be scored honestly.

**Output disguised as outcome.**

- "Ship 5 onboarding redesign initiatives."
- "Run 12 customer interviews."

Counts work done, not outcomes produced. The team can hit these by doing work without producing the outcome the objective targets.

**Outside influence.**

- "Increase total signups by 50%."
- "Maintain market share."

Total signups are upstream of activation work; market share depends on competitive dynamics largely outside the team's control.

**Vanity.**

- "Reach 1M users."
- "Reach 10K NPS responses."

Impressive numbers; not directly tied to the outcome the objective targets.

**Single-data-point dependent.**

- "Have one customer reference our product publicly."

Fragile; a single data point may not represent progress.

---

## The 3-5 key results rule

Most objectives benefit from 3-5 key results.

**Why not 1.** Single key results are fragile. If the metric does not move for reasons outside the team's tactical choices, the team has no way to show progress on the objective. Multiple KRs triangulate.

**Why not 6+.** Too many KRs dilute focus. The team scatters attention across many metrics; trade-offs across KRs become impossible because all are claimed as priority.

**The 3-5 sweet spot.**

- Enough KRs to triangulate the outcome.
- Few enough that the team can pay attention to each.
- Allows for KRs that protect against unintended degradation (e.g., deflect tickets while protecting CSAT).

**The KR composition.**

- 1-2 KRs measure the primary outcome.
- 1-2 KRs measure secondary aspects of the outcome.
- 0-1 KRs protect against unintended consequences.

---

## Baseline and target setting

Each KR needs a baseline and target.

**Baseline.** The current value of the metric. Pulled from analytics or recent measurement; should be honest, not aspirational.

**Target.** The value the team commits to reaching by end of quarter.

**Setting the target.**

- Stretch: target a value that requires real work to reach. Should hit 60-70% of the time on average across KRs.
- Not sandbagged: target should not be where the team would land without focused effort.
- Not fantasy: target should be reachable through realistic effort paths the team can identify.

**The historical-trajectory test.** Look at the metric over the past 4 quarters. Where would the metric be at end of next quarter on its current trajectory? The target should be meaningfully above that trajectory; otherwise, the OKR is sandbagged.

**The effort-path test.** Can the team identify specific initiatives that would produce the target? If yes, the target is reachable. If the team cannot identify any path, the target is fantasy.

---

## Leading vs lagging key results

Key results can measure leading indicators (early signals) or lagging indicators (final outcomes).

**Lagging.** The outcome the team ultimately wants. "First-week activation rate" measures the activation outcome.

**Leading.** Early signals that the lagging outcome will move. "Onboarding flow completion rate" leads first-week activation rate.

**The blend.**

- Some KRs measure leading indicators (so the team has signal early in the quarter).
- Some KRs measure lagging indicators (so the team is accountable to the actual outcome).
- A blend produces both early signal and end-of-quarter accountability.

**The lagging-only failure.** OKRs that only measure lagging indicators produce no mid-quarter signal. The team cannot tell if they are on track until end of quarter.

**The leading-only failure.** OKRs that only measure leading indicators produce no end-of-quarter accountability. Leading indicators can move without lagging indicators following.

---

## When binary KRs are appropriate

Most KRs are quantitative (a number to reach). Some are binary (a milestone to achieve).

**When binary works.**

- Audit-pass milestones: "Pass SOC 2 Type II with zero high-severity findings."
- Foundational milestones: "Complete admin role overhaul."
- Launch milestones: "Ship the activation redesign to all users."

**When binary fails.**

- Used for KRs that should be quantitative. "Successfully implement activation improvements" is binary disguised as outcome; should be quantitative.
- Used to dodge measurement. Binary KRs that are not actually milestones become "we did it" claims without underlying outcome verification.

**The discipline.** Use binary KRs sparingly and only when the milestone genuinely is the outcome. Most outcome KRs benefit from quantitative measurement.

---

## KRs across teams

When multiple teams contribute to the same outcome, KRs need careful design.

**The split-KR pattern.** Each team has KRs that contribute to the cross-team outcome.

- Product team KR: "Increase first-week activation rate from 32% to 45%."
- Engineering team KR: "Ship onboarding redesign by week 6 of the quarter."
- Customer success team KR: "Reduce activation-related support ticket volume by 30%."

Each team is accountable for its contribution; the cross-team outcome benefits from all.

**The single-owner pattern.** One team owns the outcome KR; other teams support without explicit KRs on the same metric.

- Product team owns the activation KR.
- Engineering and CS support without separate KRs.
- Cross-team coordination happens outside the OKR structure.

**The discipline.** Pick a pattern. Hybrid approaches (sometimes shared KRs, sometimes single-owner) produce confusion about accountability.

---

## Common KR design failures

**Output KRs.** Counts of work shipped instead of outcomes produced. Cure: rewrite.

**Vague KRs.** Lack measurable targets. Cure: specify number and threshold.

**Out-of-influence KRs.** Depend on factors the team cannot affect. Cure: rewrite to what the team can move.

**Vanity KRs.** Impressive numbers not tied to outcome. Cure: tie to the actual outcome.

**Too few KRs.** Single KR fragility. Cure: 3-5 KRs per objective.

**Too many KRs.** 6+ KRs dilute focus. Cure: cap at 5.

**No baseline.** "Reach X" without naming current value. Cure: include baseline.

**Sandbagged targets.** Targets at or below current trajectory. Cure: stretch beyond what the team would do without focus.

**Fantasy targets.** Targets with no realistic effort path. Cure: validate against effort-path test.

**Lagging-only.** No leading indicators. Cure: add leading-indicator KRs.

---

## Methodology-level choices that stay in the public skill

The four characteristics. Strong and weak KR examples. The 3-5 KR rule. Baseline and target setting. Leading vs lagging KRs. Binary KRs when appropriate. Cross-team KR patterns. Common failures.

## Implementation choices that stay internal

Specific KR templates. Specific metrics tooling and dashboards. Specific historical-trajectory analysis. Specific KR scorecards. The team's own conventions for KR wording. These vary by team and tooling.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall