Flagship Skill · OKR design

The OKR design skill.

OKRs are accountability infrastructure.

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 difference between sandbagged OKRs (always 100%), aspirational fantasy (always 30%), and stretch OKRs (genuine ambition with quarterly accountability).

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

View the skill on GitHubBrowse the full catalog

What this skill is for

The PM suite, grouped by where work happens.

OKR design sits in strategy and planning: the outcome-target discipline that ladders down from company strategy into team commitments. Distinct from roadmap-planning (which sequences outputs).

Upstream: Discovery & Strategy

Strategy & Planning

  • okr-design (this skill)

    Outcome targets for the quarter.

  • roadmap-planning

    Initiatives sequenced by priority.

  • pm-spec-writing

    Per-piece spec discipline.

Execution

Measurement

The keystone distinction

Three positions. Both extremes are failure modes.

Failure mode

Sandbagged

OKRs designed to hit 100%. Targets at or below current trajectory. No ambition, no learning. Most "OKRs we hit every quarter" sets fall here.

Failure mode

Aspirational fantasy

OKRs nobody can hit. 1000% growth in 90 days. Demoralizing, performative, ignored after week 2.

The discipline

Stretch

Genuine ambition with quarterly accountability. Designed to hit 60-70% on average across KRs. Hits and misses both teach something.

The OKR scorecard

End-of-quarter scoring on the 0.0-1.0 scale.

End of quarter scorecard

Illustrative example. Average score 0.77 (in the stretch zone).

Improve activation for new sign-ups

Obj: 0.72
  • KR1First-week activation rate from 32% to 45% (41%)0.69
  • KR2Median time-to-first-value from 4.2 days to under 2 days (2.6 days)0.73
  • KR3Onboarding flow completion rate to 80% (76%)0.75

Make the support experience deflect predictable issues

Obj: 0.82
  • KR1Reduce ticket volume on top 3 deflection categories by 40% (31%)0.78
  • KR2Self-service resolution rate from 22% to 38% (33%)0.69
  • KR3Maintain CSAT at or above 4.4/5 (4.5/5)1.00

Metrics shown are illustrative.

The framework

Twelve considerations for OKR design.

  1. 01Stretch, not sandbag or fantasy
  2. 02Objectives are outcomes, not outputs
  3. 03Few objectives, well-focused (2-4)
  4. 04Key results are measurable
  5. 05KRs outcome-aligned
  6. 06KRs within team influence
  7. 073-5 KRs per objective
  8. 08Cascading explicit but not over-constrained
  9. 09Scoring honest, not rounded
  10. 10Recalibration rare
  11. 11Weekly + mid-quarter + end-of-quarter cadence
  12. 12OKRs separate from roadmap and metrics

What is in the skill

Twelve sections covered in the body.

  1. 01

    What this skill is for

    Outcomes (results to be achieved). Distinct from roadmap-planning (outputs). Pairs with feature-launch-playbook, product-analytics-setup.

  2. 02

    Sandbagged vs aspirational-fantasy vs stretch

    The keystone framing. 60-70% average score target.

  3. 03

    Objective design

    Outcome-focused, specific to quarter, inspiring without fantasy. Few in number (2-4 per team).

  4. 04

    Key result design

    Measurable, outcome-aligned, within team influence, time-bounded. 3-5 KRs per objective.

  5. 05

    Cascading OKRs across the org

    When to cascade strictly vs loosely. The middle path with explicit ladders.

  6. 06

    Scoring discipline

    0.0-1.0 scale. The 60-70% target. Scoring honesty. The compensation question.

  7. 07

    Mid-quarter recalibration

    When to recalibrate (rarely). When NOT to (uncomfortable, off-track, easier feels achievable).

  8. 08

    The OKR review cadence

    Weekly + mid-quarter + end-of-quarter + quarterly retrospective.

  9. 09

    OKRs vs roadmap items vs metrics

    Three different concepts. OKRs are outcomes; roadmap is outputs; metrics are continuous measurements.

  10. 10

    Common failure modes

    11+ patterns: always 100%, always 30%, output KRs, OKR proliferation, generous scoring, compensation coupling.

  11. 11

    The framework: 12 considerations

    Stretch not sandbag or fantasy, outcome objectives, measurable KRs, cascading explicit, scoring honest, recalibration rare, cadence kept.

  12. 12

    Closing: OKRs are accountability infrastructure

    Quarterly accountability when designed well; ceremony when designed badly.

Reference files

Nine references that go alongside the SKILL.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

    Four characteristics. Strong vs weak KRs. The 3-5 KR rule. Baseline and target setting. Leading vs lagging KRs.

  • references/cascading-okrs-decisions.md

    When to cascade strictly vs loosely. The middle path. Cascading anti-patterns. Honest disclosure about cascading difficulty.

  • references/scoring-discipline.md

    0.0-1.0 scale. The 60-70% target. Scoring honesty. What 100% and 30% mean. The compensation question.

  • references/mid-quarter-recalibration.md

    When to recalibrate vs adapt tactics. Strategic shift vs uncomfortable OKRs. The recalibration discipline.

  • 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

    Three concepts and their relationships. Common conflations. The complete picture across all three.

  • references/okr-anti-patterns.md

    12+ anti-patterns including OKR-as-roadmap, sandbagging, fantasy, vanity metrics, OKR theater, compensation coupling.

  • references/common-okr-failures.md

    15+ failure patterns with diagnoses and cures. The cross-cutting ceremony-vs-accountability pattern.

Browse all reference files on GitHub

Pairs with these platforms

Three platforms with OKR-relevant infrastructure.

The skill is platform-agnostic. These platforms ship workflows that fit OKR programs: Notion (OKR tracking docs and review templates), Mixpanel (KR measurement and tracking), BigQuery (KR data pipelines for harder-to-measure outcomes).

Bridges to other PM-suite skills

Five sister skills that compose with OKR design.

  • Outputs scope

    roadmap-planning

    Roadmap is outputs (features and initiatives sequenced); OKRs are outcomes. Same quarter has both; they answer different questions.

  • Post-ship execution

    feature-launch-playbook

    Launch discipline; OKRs may include KRs about post-launch outcomes. The two compose for major launches.

  • Measurement infrastructure

    product-analytics-setup

    Analytics provide the metrics KRs depend on. OKRs cannot be measured if metrics are not instrumented.

  • Quantitative validation

    experiment-design

    Experiments validate that specific initiatives produce OKR outcomes. The two compose for outcome-driven testing.

  • Cross-team orchestration

    integration-orchestrator

    Cross-team OKRs require coordination. Integration orchestration handles the dependencies and handoffs.

Direction 7 closes

The third of five PM skills closing Direction 7.

OKR design is the third of five PM skills shipped together in Direction 7 Dispatch B. Together with discovery-research-synthesis, jtbd-framing, beta-program-management, and user-feedback-aggregation, plus the Tier 2 content suite (Dispatch A), Direction 7 closes with 9 new skills total.

The catalog now carries 86 flagships across creative direction, content, design, SEO, project management, marketing, and operations.

Open source under MIT

Read the SKILL.md on GitHub.

The skill source lives in the rampstackco/claude-skills repository. MIT licensed.

View SKILL.mdBrowse the full catalog

Frequently asked questions.

What does 'sandbagged vs aspirational fantasy vs stretch' mean?
Sandbagged: OKRs designed to hit 100%. Targets at or below current trajectory. No ambition, no learning, no signal. Aspirational fantasy: OKRs nobody can hit. 1000% growth in 90 days. Demoralizing, ignored after week 2. Stretch: genuine ambition with quarterly accountability. Designed to hit 60-70% on average across KRs. Hits and misses both teach something. The litmus test: track average score over multiple quarters. 95%+ signals sandbagging; below 30% signals fantasy; 50-75% range is stretch territory.
What makes a key result strong?
Four characteristics: measurable (specific number or testable threshold), outcome-aligned (achieving the KR moves the objective forward), within team influence (the team can affect it through their work), time-bounded (measurement window is the quarter). 3-5 KRs per objective is the sweet spot. Single KR is fragile; 6+ dilute focus. Each KR has a baseline (current value) and target (where the team commits to reach). Use the historical-trajectory test: targets should be meaningfully above where the metric would land without focused effort.
How is okr-design different from roadmap-planning?
OKRs are outcomes (results to be achieved). Roadmap items are outputs (features and initiatives sequenced). Same quarter often has both; they answer different questions. The OKR is 'improve activation for new sign-ups so more reach value-realization in week one.' The roadmap items contributing are 'onboarding redesign, welcome email sequence revision, activation triage automation.' Common conflation: treating OKRs as roadmap commitments. Mid-quarter tactical changes feel like broken promises if stakeholders interpret OKRs as output commitments.
When should OKRs be recalibrated mid-quarter?
The default is OKRs hold for the quarter. Tactics adapt; OKRs do not. Recalibration is the exception, not the rule. Three conditions warrant it: strategic shift (company strategy changed materially), major external disruption (market change, regulatory event, significant outage), or invalidating information (the metric does not actually represent the outcome). NOT triggers for recalibration: the team is not on track (the miss is the signal), the OKR is uncomfortable (stretch is uncomfortable by design), easier OKRs would feel achievable (sandbagging in slow motion).
Should OKRs be tied to compensation?
OKRs work best when not directly tied to compensation. When OKRs determine bonuses, sandbagging incentives become severe. Teams set OKRs they know they can hit. The 60-70% target collapses to 95% target because nobody wants to risk their bonus on stretch. Most healthy OKR cultures separate goal-setting from compensation. Compensation flows through performance reviews informed by many inputs (manager assessment, peer feedback, role expectations); OKR scores may be one input but should not be dominant.
What review cadence works for OKRs?
Four cadences compose. Weekly check-ins (15-30 min): tactical adjustment, surface blockers, not for adjusting OKRs. Mid-quarter review (60-90 min, week 6): honest trajectory assessment, decision point for any rare recalibration. End-of-quarter scoring (60-90 min): score honestly using the 0.0-1.0 scale; document context. Quarterly retrospective: review the practice itself; what worked, what did not, what should change. Skipping cadences is the failure mode; teams that skip weekly check-ins often discover at end of quarter that they could have course-corrected.