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/mid-quarter-recalibration.md
View on GitHub# Mid-quarter recalibration
When OKRs should change vs when teams should adapt. Strategic shift vs uncomfortable OKRs. The recalibration discipline.
The default is that OKRs hold for the quarter. Teams adapt their tactics; OKRs do not change to match what the team is doing. Recalibration is the exception, not the rule. Recalibrating frequently signals OKR design failure.
---
## The default: OKRs hold
OKRs are quarterly commitments. The team commits at the start of the quarter and works toward them through the quarter regardless of whether progress feels comfortable.
**Why holding matters.**
- OKRs are accountability infrastructure. Changing them mid-quarter weakens the accountability.
- Stretch OKRs are uncomfortable by design. The discomfort is the work.
- Teams that recalibrate when uncomfortable train themselves to recalibrate as a coping mechanism.
**Adapting tactics, not OKRs.**
- The OKR target stays.
- The team's tactics for reaching the target adapt as they learn what works.
- New initiatives may be launched; existing ones may be scrapped; the OKR remains the destination.
---
## When to recalibrate
Three conditions warrant recalibration.
### Strategic shift
The company's strategy changed materially mid-quarter. OKRs that no longer reflect the strategy are no longer the right targets.
**Examples.**
- The company pivoted to a new market segment; OKRs aimed at the prior segment are no longer strategic.
- A major acquisition or restructure changed the team's mandate.
- Leadership announced a new strategic priority that supersedes the quarter's OKRs.
**The handling.** Recalibrate explicitly. Document what changed strategically and how OKRs are revised. Communicate to stakeholders so the recalibration is visible and intentional.
### Major external disruption
A market change, regulatory event, or significant outage warrants resetting the quarter's targets.
**Examples.**
- A major outage consumed weeks of engineering capacity that was meant for OKR work.
- Regulatory changes required compliance work that displaced planned OKRs.
- Market conditions shifted dramatically (recession, supply chain disruption) and the OKRs no longer reflect realistic ambition for the new conditions.
**The handling.** Recalibrate explicitly. Surface the disruption and its impact. Set new targets that reflect the post-disruption reality.
### Information that invalidates the OKR
The team learned mid-quarter that the metric they were targeting does not actually represent the outcome.
**Examples.**
- Analytics work revealed that the activation metric the team was targeting is not the right measure of activation success; a better metric exists.
- Customer research revealed that the user segment the team was prioritizing is smaller or less important than expected.
- Technical investigation revealed that the planned approach to an OKR has fatal limitations that were not visible at planning time.
**The handling.** Recalibrate explicitly. Document what was learned. Set new OKRs reflecting the new understanding.
---
## When NOT to recalibrate
Three patterns that look like recalibration triggers but are not.
### The team is not on track
OKRs that the team is missing should remain as set; the miss is the signal.
**Why.** Stretch OKRs are designed to miss sometimes. Hitting 60-70% on average means roughly 30-40% of KRs miss the target. The miss is informative; lowering the target to match the trajectory eliminates the signal.
**The cure.** Hold the OKR. Score honestly at end of quarter. Use the miss to inform next quarter's design.
### The OKR is uncomfortable
Teams uncomfortable with stretch OKRs sometimes want to recalibrate to feel better.
**Why.** Stretch is uncomfortable by design. Teams that learn to lower OKRs when uncomfortable lose the stretch discipline; OKRs drift toward sandbagging quarter over quarter.
**The cure.** Hold the OKR. Acknowledge the discomfort. Surface what the team would need to push toward the target. Use the discomfort productively rather than recalibrating it away.
### Easier OKRs would feel achievable
The temptation to swap hard OKRs for easy ones is sandbagging in slow motion.
**Why.** Hard OKRs are the point. Swapping for easier ones removes the accountability infrastructure stretch OKRs provide.
**The cure.** Hold the OKR. If the original was genuinely fantasy (no realistic effort path), recalibrate per the strategic-shift pattern. If the original was genuine stretch but uncomfortable, hold.
---
## The recalibration discipline
When recalibration is warranted, the discipline matters.
**Surface the trigger.** What changed? Strategic shift, external disruption, or invalidating information. Be specific.
**Document the original target and the revised target.** The history of recalibration is part of the OKR record. Future audits should be able to see what changed.
**Explain the new target.** Why this revised target? What effort path produces it? How does it reflect the new reality?
**Communicate to stakeholders.** Recalibration is visible. Stakeholders who expected the original target should know it changed and why.
**Score against the revised target at end of quarter.** The recalibrated OKR is the OKR for scoring purposes. Do not score against the original.
---
## Frequency of recalibration
Recalibration should be rare.
**Healthy frequency.** 1-2 quarters out of 8 may include recalibration on at least one OKR. Most quarters should have no recalibrations.
**Concerning frequency.** Every quarter includes recalibration on some OKR. This signals either:
- The OKR design is consistently aggressive (fantasy targets).
- The strategy is shifting too frequently (lack of strategic stability).
- The team has learned to recalibrate as a coping mechanism for stretch.
**The diagnosis.** Frequent recalibration is a signal to investigate, not a feature to lean into. The investigation surfaces whether the issue is OKR design, strategic stability, or team behavior.
---
## Recalibration as honest tool vs avoidance
The line between honest recalibration and avoidance.
**Honest recalibration.**
- The trigger is specific and external (strategic shift, disruption, invalidating information).
- The revised target reflects the new reality, not the team's preference.
- The recalibration is documented and visible.
**Avoidance dressed as recalibration.**
- The trigger is vague ("things changed").
- The revised target is conveniently achievable.
- The recalibration happens when the OKR is uncomfortable, not when external conditions warrant it.
**The honest test.** If a stakeholder asked the team to defend the recalibration, could the team point to a specific external trigger? If the answer is "we just thought the target was too ambitious," the recalibration is avoidance.
---
## Recalibration in the OKR system
How recalibration affects the broader OKR practice.
**Trust effects.**
- Recalibration that is rare and well-justified preserves trust in OKRs.
- Recalibration that is frequent or poorly justified erodes trust; stakeholders learn to expect targets to slide.
**Org-wide signaling.**
- One team's recalibration affects how other teams perceive recalibration norms.
- Leaders that recalibrate strict targets signal to teams that recalibration is acceptable; teams take the cue.
- Leaders that hold targets even when uncomfortable signal that stretch is real; teams take that cue.
**The practice's calibration over time.** Recalibration norms accumulate. Healthy practices stay disciplined; decaying practices loosen. The annual review of OKR practice should look at recalibration frequency as one signal of practice health.
---
## Communicating recalibration
When recalibration happens, communication matters.
**To the team.**
- Surface the trigger before the recalibration is decided. The team should understand what changed.
- Discuss the revised target before committing. The team should be able to commit credibly to the new target.
- Document the change in the OKR system.
**To stakeholders.**
- Notify stakeholders explicitly. Do not let recalibration appear as a quiet edit.
- Explain the trigger and the revised target.
- Invite questions; stakeholder concerns may surface issues with the recalibration that warrant further discussion.
**To the org.**
- Recalibration patterns inform org-wide OKR discussion. If multiple teams recalibrate in the same quarter, surface the pattern; the strategic clarity may be lacking.
---
## Common recalibration failures
**Recalibration as the default.** Teams routinely revise OKRs mid-quarter. The OKR system collapses into rolling targets that always reflect current state.
**Recalibration to avoid stretch discomfort.** Teams revise when OKRs feel uncomfortable; targets drift toward sandbagging.
**Recalibration without trigger documentation.** OKRs change without surfaced reason; the change becomes invisible to stakeholders.
**Refusal to recalibrate when warranted.** Teams hold OKRs even when strategy genuinely shifted; quarter ends with OKRs disconnected from strategy.
**Recalibration to avoid scoring low.** Teams revise targets in the last weeks of the quarter to make the score look better. Scoring loses honesty.
**Org-wide recalibration cascade.** One team's recalibration triggers others; the whole quarter resets; the OKR system loses meaning.
---
## Methodology-level choices that stay in the public skill
The default-to-hold principle. When to recalibrate (strategic shift, major disruption, invalidating information). When not to recalibrate (uncomfortable, off-track, easier-feels-better). The recalibration discipline. Frequency norms. Honest vs avoidance recalibration. Communication. Common failures.
## Implementation choices that stay internal
Specific OKR-tracking tools that capture recalibration history. Specific approval workflows for recalibration. The team's own conventions for recalibration communication. These vary by org.
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 |