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/review-cadence-templates.md

View on GitHub
# Review cadence templates

Weekly check-ins, mid-quarter review, end-of-quarter scoring, quarterly retrospective. Format and time investment per cadence.

OKRs benefit from a structured review rhythm. The cadence produces accountability infrastructure: weekly tactical adjustment, mid-quarter strategic assessment, end-of-quarter scoring, and quarterly practice review. Teams that skip the cadence often watch OKRs decay into year-end reckoning that produces no learning.

---

## Weekly check-ins

The shortest, most frequent review.

**Format.**

- 15-30 minutes per team.
- Team reviews progress on each key result.
- Surfaces blockers, dependencies, signal that the trajectory is off.
- Decides tactical adjustments for the upcoming week.

**Structure.**

- Per KR: current value, trajectory, blockers, planned work for the upcoming week.
- Cross-OKR: any priority shifts, dependencies needing attention.
- Closing: commitments for the week.

**Purpose.**

- Tactical adjustment, not OKR adjustment.
- Surface blockers early so they can be addressed.
- Maintain focus on OKRs across the quarter (without weekly check-ins, OKRs get forgotten in the press of immediate work).

**What this is not for.**

- Adjusting the OKR or its targets. That is mid-quarter or end-of-quarter work.
- Status reports for stakeholders. Status reports may flow from the check-in but are a separate output.
- Detailed work review. The check-in is OKR-focused; other work happens elsewhere.

**Common failures.**

- Becoming status reports. The check-in turns into "here's what I did this week"; OKR-driven decisions get crowded out. Reform the format.
- Becoming OKR adjustment sessions. Teams uncomfortable with OKRs sometimes use weekly check-ins to soften them. Hold to tactical scope.
- Skipping when busy. Weeks where the check-in feels less urgent are exactly when discipline is needed. Skip rarely.

---

## Mid-quarter review

A longer, more strategic review.

**Format.**

- 60-90 minutes per team.
- Roughly week 6 of the quarter (mid-point).
- Honest assessment of trajectory: which KRs are on track, which are off.
- Decision point for any recalibration (rare; should not be the default outcome).
- Surface external dependencies that affect end-of-quarter outcomes.

**Structure.**

- Per OKR: current state vs target, trajectory analysis, on-track or off-track assessment.
- Cross-OKR: priority adjustments, capacity reallocations, blockers requiring escalation.
- Recalibration check: is any OKR a candidate for revision per the strategic-shift / disruption / invalidating-information criteria? (See `mid-quarter-recalibration.md`.)
- Closing: tactical decisions for the second half of the quarter.

**Purpose.**

- Strategic assessment of OKR progress.
- Course correction before end-of-quarter when there is still time.
- Surface OKRs that may need recalibration (with the discipline that recalibration should be rare).

**What this is not for.**

- Routine recalibration. Most mid-quarter reviews end with no recalibration; tactical adjustments are the typical output.
- Scoring. Scoring is end-of-quarter; mid-quarter assesses trajectory toward the score.
- Postmortem. Postmortems are for completed work; mid-quarter is for live work in progress.

**Common failures.**

- Becoming a recalibration session. Teams uncomfortable with stretch use mid-quarter review to lower OKRs. Hold to the rare-recalibration discipline.
- Becoming a status meeting. The session becomes a presentation rather than a decision-making review. Reform format to surface decisions.
- Skipping. Teams that skip mid-quarter review often discover at end of quarter that they could have course-corrected; the missed opportunity is the cost.

---

## End-of-quarter scoring

The OKR-cycle closing review.

**Format.**

- 60-90 minutes per team.
- Last week of the quarter.
- Score each key result honestly.
- Identify what produced the scores: tactical choices, external factors, OKR design decisions.
- Inform next-quarter OKR design with the lessons.

**Structure.**

- Per KR: actual outcome, score (0.0-1.0), context (what produced this score).
- Per objective: average KR score, context.
- Cross-OKR: average score across all OKRs (informs whether the quarter was stretch, sandbag, or fantasy).
- Lessons: what this quarter's scoring reveals about OKR design, team capacity, or strategic clarity.
- Closing: insights to carry into next quarter's OKR setting.

**Purpose.**

- Honest scoring of outcomes.
- Learning from the gap between target and outcome.
- Input to the next quarter's OKR design.

**What this is not for.**

- Compensation discussions. OKRs work best decoupled from compensation; scoring should not feel like a performance evaluation.
- Blame allocation. Misses are informative; the discussion is about what produced the gap, not who failed.
- Setting next quarter's OKRs. That is a separate session.

**Common failures.**

- Generous scoring. Scores rounded up; the team protects feelings; honest signal lost. Hold the discipline.
- Skipping context. Scores published without explanation of what produced them. Lessons get lost.
- Treating scores as performance. Compensation coupling produces sandbagging in subsequent quarters.
- Not informing next quarter. Scores reviewed but lessons do not influence the next OKR setting. The cycle does not learn.

---

## Quarterly retrospective

A separate review focused on the OKR practice itself.

**Format.**

- 60-90 minutes per team or org.
- After end-of-quarter scoring.
- Reviews the OKR practice, not the OKR outcomes.
- Often combined with the next-quarter OKR setting session.

**Structure.**

- What worked in this quarter's OKR practice (cadence, format, design)?
- What did not work?
- What should change in the next cycle?
- What patterns are emerging across multiple quarters?

**Purpose.**

- Improve the OKR practice itself.
- Surface decay or drift in OKR discipline.
- Inform process changes for the next cycle.

**What this is not for.**

- Scoring or recalibrating current OKRs. That is end-of-quarter work.
- Setting next quarter's OKRs. That is a separate session that uses the retrospective's inputs.

**Common patterns surfaced.**

- Sandbagging or fantasy drift. Average score patterns over multiple quarters reveal practice decay.
- Cadence breakdown. Weekly check-ins becoming status reports; mid-quarter reviews becoming recalibration sessions.
- Cascading misalignment. Teams setting OKRs that do not ladder; cross-team coordination failing.
- Compensation coupling. OKRs becoming performance theater because they are tied to bonuses.

**Common retrospective failures.**

- Skipping the retrospective. The OKR practice does not improve; decay accumulates.
- Conflating with next-quarter OKR setting. Both can happen in one session, but the retrospective lens (process review) should be distinct from the OKR design lens (setting).
- Producing recommendations without follow-through. Retrospectives surface improvements; the team must implement them in the next cycle for the retrospective to matter.

---

## The cadence as a system

The four cadences compose.

**The system.**

- Weekly check-ins maintain tactical focus and surface blockers.
- Mid-quarter review provides strategic assessment and rare recalibration opportunity.
- End-of-quarter scoring produces honest signal on outcomes.
- Quarterly retrospective improves the practice over time.

**The reinforcement.**

- Weekly check-ins make mid-quarter assessment honest (the team has been tracking trajectory all along).
- Mid-quarter review surfaces issues end-of-quarter scoring will face.
- End-of-quarter scoring informs the retrospective.
- The retrospective informs the next cycle's design.

**The skip risk.** Teams that skip cadences often skip several. Weekly check-ins falter; mid-quarter review becomes ad-hoc; end-of-quarter scoring becomes generous because the team has not been tracking honestly all along; the retrospective never happens.

---

## Cadence ownership

Each cadence has a clear owner.

**Weekly check-ins.** Owned by the team lead (manager, PM, engineering lead). Facilitates the meeting; ensures it stays tactical.

**Mid-quarter review.** Owned by the team lead, often with cross-functional partners attending. Surfaces strategic decisions.

**End-of-quarter scoring.** Owned by the team lead. Ensures honest scoring; documents context.

**Quarterly retrospective.** Owned by the team lead or by a process-focused role (chief of staff, ops lead). Often facilitated by someone slightly outside the team to bring fresh perspective.

**Cross-team coordination.** When multiple teams have OKRs that compose, coordination across teams happens at the cadence boundaries (typically mid-quarter review).

---

## Common cadence failures

**Skipping cadences.** Weekly check-ins falter; mid-quarter review becomes ad-hoc; the system breaks.

**Cadence merging.** Mid-quarter review and end-of-quarter scoring combined into one session. Loses the distinct purposes.

**Status-report drift.** Weekly check-ins become status reports; tactical decisions get displaced.

**Recalibration drift.** Mid-quarter review becomes a recalibration session; OKRs lose accountability.

**Generous-scoring drift.** End-of-quarter scoring rounds up; honest signal lost.

**Retrospective skipping.** OKR practice does not improve; decay accumulates.

---

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

The four cadence formats. Time investment per cadence. Structure and purpose per cadence. The cadence-as-system reinforcement. Ownership. Common failures.

## Implementation choices that stay internal

Specific meeting templates. Specific OKR-tracking tools that support each cadence. Specific facilitation conventions. Specific cross-team coordination formats. The team's own conventions for cadence cadence (no pun intended). 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: 323kUpdated 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