rampstackco/claude-skills / skills/okr-design
okr-design
VerifiedOKR 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 351 B |
| SKILL.md | skill md | 21.9 KB |
| references/cascading-okrs-decisions.md | markdown | 9.0 KB |
| references/common-okr-failures.md | markdown | 9.6 KB |
| references/key-result-design-patterns.md | markdown | 9.9 KB |
| references/mid-quarter-recalibration.md | markdown | 9.8 KB |
| references/objective-design-patterns.md | markdown | 9.3 KB |
| references/okr-anti-patterns.md | markdown | 10.5 KB |
| references/okrs-vs-roadmap-vs-metrics.md | markdown | 8.8 KB |
| references/review-cadence-templates.md | markdown | 9.7 KB |
| references/scoring-discipline.md | markdown | 9.4 KB |
references/common-okr-failures.md
View on GitHub# Common OKR failures
Eleven-plus failure patterns with diagnoses and cures. Cross-references the OKR anti-patterns reference; this file covers operational failures that arise during the OKR cycle.
The cross-cutting pattern: most OKR failures share a single root, which is treating OKRs as ceremony rather than as accountability infrastructure.
---
## Failure 1: Our OKRs are always 100% and produce no signal
**Symptom.** End-of-quarter scoring shows the team hitting 95%+ on every KR. The OKR practice feels positive but does not produce learning.
**Diagnosis.** Sandbagging. Targets set at or below the team's natural trajectory. The OKR practice has decayed into "what we know we can hit."
**Cure.** Set targets above the historical trajectory. Use the historical-trajectory test: where would the metric land without focused effort? The target should be meaningfully above that.
**Prevention.** Track the average score over multiple quarters. Drift toward 0.85+ is a sandbagging signal; intervene before the practice fully decays.
---
## Failure 2: Our OKRs are always 30% and demoralizing
**Symptom.** End-of-quarter scoring shows the team consistently missing OKRs. Team disengages from OKRs by mid-quarter.
**Diagnosis.** Aspirational fantasy. Targets have no realistic effort path. The OKR practice has decayed into "inspirational numbers nobody believes."
**Cure.** Recalibrate to genuine stretch. Validate against the effort-path test: can the team identify specific initiatives that would produce the target?
**Prevention.** During OKR setting, require effort-path reasoning. If the team cannot articulate what work would produce the target, the target is fantasy.
---
## Failure 3: Our key results measure work, not outcomes
**Symptom.** KRs read as roadmap items. "Ship X by Y." "Run Z interviews."
**Diagnosis.** Output-disguised-as-outcome. The team is committing to work, not to results.
**Cure.** Rewrite each output KR to measure the outcome the output is meant to produce. The output itself lives in the roadmap.
**Prevention.** During KR drafting, apply the outcome test: is this measuring a result, or counting work?
---
## Failure 4: We have 12 OKRs and the team is working on 47 things
**Symptom.** Quarterly OKRs span many objectives and KRs; the team's work is scattered across many priorities.
**Diagnosis.** OKR proliferation. Too many objectives produces no focus.
**Cure.** Cap at 2-4 objectives, 3-5 KRs each. Surface deferred work explicitly so the team can see what they are choosing not to commit to.
**Prevention.** Cap OKRs at the start of the cycle. Adding "just one more" OKR is a recurring pressure that should be resisted.
---
## Failure 5: Our OKRs are vague
**Symptom.** Objectives like "improve user experience" or KRs like "make activation better." Cannot be scored honestly.
**Diagnosis.** Lack of measurable specificity.
**Cure.** Rewrite KRs with specific numbers, baselines, and targets. "Increase first-week activation rate from 32% to 45%" instead of "improve activation."
**Prevention.** During KR review, apply the specificity test: could two reasonable people disagree on whether this KR was hit at end of quarter? If yes, it is too vague.
---
## Failure 6: Our cascading produces team OKRs that do not match team work
**Symptom.** Team OKRs cascade to company OKRs but the team's actual capacity and mandate produce different work.
**Diagnosis.** Strict cascading mismatched to team mandate.
**Cure.** Loosen cascading; allow team-specific OKRs that do not directly ladder. Or change team mandate if it does not match strategy.
**Prevention.** Use the middle path on cascading. Surface team-specific OKRs explicitly.
---
## Failure 7: We never recalibrate even when the strategy shifts
**Symptom.** The org's strategy changed mid-quarter. Team OKRs no longer reflect strategy. The team holds them anyway.
**Diagnosis.** Recalibration too tightly avoided.
**Cure.** Surface the strategic shift; recalibrate the affected OKRs explicitly. Document the trigger.
**Prevention.** Make strategic-shift criteria for recalibration explicit. The team should know when recalibration is appropriate.
---
## Failure 8: We recalibrate every quarter
**Symptom.** OKRs get revised mid-quarter routinely. The team uses recalibration to soften uncomfortable OKRs.
**Diagnosis.** Recalibration too easy. OKR design is failing or stretch ambition is being avoided.
**Cure.** Hold OKRs absent the recalibration triggers (strategic shift, major disruption, invalidating information). Investigate why frequent recalibration is happening.
**Prevention.** Track recalibration frequency. Drift toward "every quarter recalibrates" is a signal to intervene.
---
## Failure 9: Our weekly check-ins became status reports
**Symptom.** Weekly OKR check-ins lost their tactical decision focus; they became "here's what I did this week" updates.
**Diagnosis.** Check-in format drift. The session is no longer producing tactical adjustments.
**Cure.** Reform the format. Per KR: trajectory, blockers, planned work for the upcoming week. End with explicit commitments.
**Prevention.** The team lead facilitates the check-in's tactical scope. Status reports happen elsewhere.
---
## Failure 10: Our scoring rounds up
**Symptom.** End-of-quarter scoring shows 0.85 average. Closer inspection shows scores were rounded up across most KRs.
**Diagnosis.** Generous scoring. Honesty has decayed.
**Cure.** Commit to honest scoring. A 0.55 KR scores 0.55, not 0.6. Document context; the context surfaces what produced the actual outcome regardless of the number.
**Prevention.** Surface the rounding pattern explicitly. The team should know that rounding up is the failure mode.
---
## Failure 11: OKRs and bonuses are tied; people sandbag
**Symptom.** OKR scores directly determine bonuses. Targets set conservatively; scoring round up; stretch ambition gone.
**Diagnosis.** Compensation coupling.
**Cure.** Decouple OKRs from compensation. Compensation flows through performance reviews informed by many inputs.
**Prevention.** Establish from the start that OKRs are accountability infrastructure, not performance management. Compensation tied loosely or not at all.
---
## Failure 12: OKRs were set but never referenced
**Symptom.** OKRs documented at start of quarter. Mid-quarter prioritization debates ignore them. End-of-quarter scoring is generous because nobody tracked rigorously.
**Diagnosis.** OKR theater. The practice produces overhead without value.
**Cure.** Reform the cadence. Weekly check-ins reference OKRs explicitly. Mid-quarter review uses OKRs as the assessment lens. Scoring informs next quarter.
**Prevention.** Tie OKRs to specific decisions. If OKRs are not load-bearing for prioritization, surface the disconnect and reform or abandon.
---
## Failure 13: KRs depend on factors outside team influence
**Symptom.** KRs miss because of external factors the team could not affect (market conditions, sales execution, infrastructure issues). The team cannot credibly own the KR.
**Diagnosis.** KR design failure. Targets set on outcomes the team cannot meaningfully drive.
**Cure.** Rewrite to focus on what the team can move. The team's contribution to a larger outcome may be the right KR, not the larger outcome itself.
**Prevention.** During KR design, validate that the team can identify how their work moves the KR.
---
## Failure 14: Cross-team OKRs produce coordination failures
**Symptom.** Multiple teams have KRs aimed at the same outcome. Teams pursue independently; the outcome lags because nobody owns the integration.
**Diagnosis.** Cross-team coordination missing. Either single ownership should have been assigned, or split KRs need stronger coordination.
**Cure.** Establish single ownership for outcome OKRs that span multiple teams. Or use split-KR pattern where each team's KR is their specific contribution.
**Prevention.** During OKR design, surface cross-team dependencies. Decide single-owner or split-KR explicitly.
---
## Failure 15: OKRs are roadmap commitments to stakeholders
**Symptom.** Stakeholders treat OKRs as commitments to specific work. Mid-quarter tactical adjustments feel like broken promises.
**Diagnosis.** OKR-as-roadmap conflation. Stakeholders interpret outcomes as outputs.
**Cure.** Distinguish between OKRs (outcomes the team commits to pursue) and roadmap (work the team plans to do). Both are visible; the OKR is the accountability; the roadmap is the team's current best guess at what work will produce the outcome.
**Prevention.** When communicating OKRs to stakeholders, explicitly surface the distinction. Use different vocabulary.
---
## The cross-cutting pattern
Most OKR failures share a single root: treating OKRs as ceremony rather than as accountability infrastructure.
Ceremony focuses on the appearance of OKR practice: documents produced, meetings held, scores generated. Accountability focuses on the work the practice is meant to support: stretch goal-setting, mid-quarter learning, end-of-quarter scoring honesty, next-quarter improvement.
The fix for almost any OKR failure starts with the same question: what decision is this OKR practice supposed to inform? When the answer is clear, the practice becomes load-bearing. When the answer is "we should follow the OKR process," the practice becomes ceremony.
---
## Methodology-level choices that stay in the public skill
The fifteen failure patterns with diagnoses and cures. The cross-cutting ceremony-vs-accountability pattern.
## Implementation choices that stay internal
Specific failure-pattern detection. Specific reviewer training. Specific intervention patterns. The team's own conventions for catching failures early. These vary by team.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |