borghei/Claude-Skills / project-management/execution/brainstorm-okrs
brainstorm-okrs
VerifiedDraft and score quarterly OKRs: a qualitative objective, measurable key results and a counter-metric. Use when setting or reviewing a team's OKRs before they are committed, or when KRs read like a task list.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| assets/okr_template.md | markdown | 1.9 KB |
| assets/sample_okrs.json | config | 1.9 KB |
| assets/sample_okrs_clean.json | config | 1.5 KB |
| examples/q3-okrs-shared-dashboards-launch.md | markdown | 8.8 KB |
| references/okr-best-practices.md | markdown | 8.4 KB |
| references/okr-workflow-and-examples.md | markdown | 8.8 KB |
| references/red-flags.md | markdown | 12.9 KB |
| scripts/okr_validator.py | script | 16.1 KB |
references/red-flags.md
View on GitHub# Red Flags: Brainstorm OKRs
> Common ways this skill's output goes wrong — concrete examples, why they're bad, and how to fix them.
## How to use this document
Scan a draft OKR set before committing to the quarter. Each red flag shows the *bad* version next to the *good* version, anchored to Christina Wodtke's Radical Focus framework.
---
## Red Flag 1: Output disguised as Key Result
**Symptom.** A KR reads "Launch the mobile app" or "Ship 12 blog posts".
**Why it's bad.** OKRs measure *outcomes* (what changed for customers / the business), not activities (what the team did). Output KRs let the team mark "done" while moving no business metric. The Objective gets credit; the company gets nothing.
**Bad example:**
> "Objective: Become the fastest-growing product in our category.
> KR1: Launch the new mobile app by August 31.
> KR2: Ship 12 blog posts on growth themes.
> KR3: Run 4 customer interviews per week."
**Good example:**
> "Objective: Become the fastest-growing product in our category.
> KR1: Increase weekly active accounts from 28k to 45k.
> KR2: Lift mobile-originated signups from 12% to 30% of total.
> KR3 (counter): Maintain D30 retention above 62% (don't trade quality for growth)."
**How to catch it.** For each KR, ask "could we hit this and have zero impact on a business metric?" If yes, it's output.
---
## Red Flag 2: Sandbagging — 100% confidence
**Symptom.** Team commits to KR targets they are 95-100% certain to hit. Quarter ends; every KR is green.
**Why it's bad.** Wodtke's discipline targets 60-70% confidence on commitment. 100% confidence means the OKR captures work the team would do anyway — it does not focus or stretch. The team learns nothing about its capacity.
**Bad example:**
> "Current MRR: $480k. KR1 target: $500k MRR by Q3 end (a 4% lift the team would hit on autopilot)."
**Good example:**
> "Current MRR: $480k. KR1 target: $650k MRR by Q3 end (a 35% lift, requiring an activation experiment + a pricing change). Team confidence: 65%. If we hit this, we have learned to ship at this rate; if we miss at 0.6, we have learned where the constraint is."
**How to catch it.** Ask the team "what is your confidence percentage?" If above 80% on every KR, the bar is too low.
---
## Red Flag 3: OKR drift mid-quarter
**Symptom.** It's week 8 of a 12-week quarter. KR1 looks behind. The team "updates" the KR target downward and calls it red-to-yellow.
**Why it's bad.** Mid-quarter target changes erase the learning signal. The reason confidence is 60-70% is precisely so half the time the team misses — and the miss teaches what the constraint is. Moving the goal post turns OKRs into theater.
**Bad example:**
> "Week 8 check-in: KR1 was 'Increase MRR by 35%'. We're on track for 18%. Updating KR1 target to 20% to reflect current reality. Now green."
**Good example:**
> "Week 8 check-in: KR1 was 'Increase MRR by 35%'. We're on track for 18%. Status: red. Discussion: the activation experiment underperformed; pricing change is held by legal. Decision: do not move the target. Run the diagnostic: what would unlock the remaining 17%? If nothing realistic, we miss the KR and document why in the retrospective. The miss is signal, not failure."
**How to catch it.** Compare week-1 KR targets to week-8 KR targets. Any downward shift is a red flag.
---
## Red Flag 4: Five+ Objectives per team per quarter
**Symptom.** The team's OKR doc has 5 Objectives, each with 3 KRs. Total: 15 KRs.
**Why it's bad.** Radical Focus is in the name — Wodtke's framework demands 1 Objective per team per quarter (2 max). Five objectives equals no focus. The team will do scattered work and feel busy; nothing strategic moves.
**Bad example:**
> "Q3 OKRs:
> Obj 1: Improve onboarding.
> Obj 2: Reduce churn.
> Obj 3: Launch enterprise tier.
> Obj 4: Improve performance.
> Obj 5: Expand to APAC."
**Good example:**
> "Q3 OKR (single): 'Make our enterprise pricing the obvious choice for mid-market buyers.' KR1: 8 mid-market net-new logos. KR2: enterprise tier ARR from $1.2M to $2.4M. KR3 (counter): SMB churn stays under 4%. The other initiatives (onboarding, performance, APAC) remain on the roadmap but are not Q3 OKRs."
**How to catch it.** Count Objectives. > 2 is a flag. The conversation is then "which Objective are we actually committing to?"
---
## Red Flag 5: Missing counter-metric
**Symptom.** OKR set has KR1 and KR2 both pulling toward the same direction. No counter-metric.
**Why it's bad.** Without a counter, the team can game the KRs by doing something harmful. KR1 "increase signups" with no counter on activation means the team lowers the signup bar; numbers go up, business value goes down.
**Bad example:**
> "Objective: Grow the funnel top.
> KR1: Signups from 8k/mo to 16k/mo.
> KR2: Trial starts from 5k/mo to 10k/mo."
**Good example:**
> "Objective: Grow the funnel top with intent.
> KR1: Signups from 8k to 16k/mo.
> KR2: Trial starts from 5k to 10k/mo.
> KR3 (counter): Day-7 activation rate stays above 38% (no growth at the cost of low-intent users)."
**How to catch it.** For each KR pair, ask: "Could we hit these by doing something stupid?" If yes, the counter is missing.
---
## Red Flag 6: Numbers in the Objective
**Symptom.** Objective reads "Reach 50k weekly active users by Q3 end".
**Why it's bad.** Objectives are qualitative and inspirational. They describe the destination, not the speedometer. Numbers belong in Key Results. An Objective with numbers fuses the two and removes the room for KRs to *prove* progress against the Objective.
**Bad example:**
> "Objective: Reach 50k weekly active users by Q3 end."
**Good example:**
> "Objective: Become the product teams can't imagine leaving.
> KR1: Weekly active users from 32k to 50k.
> KR2: D30 retention from 58% to 70%.
> KR3 (counter): NPS stays above 45."
**How to catch it.** Read the Objective. If it contains a number, a date, or a percentage, rewrite.
---
## Red Flag 7: Activity metrics dressed as KRs
**Symptom.** KR reads "Publish 12 blog posts" or "Run 8 user interviews".
**Why it's bad.** Activity ≠ outcome. The team can do 12 posts that nobody reads. The KR validates effort but not impact. (Same root cause as Red Flag 1 but a more subtle phrasing — quantified activities feel measurable.)
**Bad example:**
> "KR1: Publish 12 blog posts on growth themes.
> KR2: Run 8 customer interviews."
**Good example:**
> "KR1: Increase organic traffic to growth-themed pages from 4k/mo to 10k/mo (so the blog work is judged by outcome, not output).
> KR2: Identify 3 prioritized opportunity areas from customer research (so the interview work is judged by what it produces, not by count of meetings)."
**How to catch it.** Read each KR. Strip the unit. If "12 posts" becomes "12 X" and the X is any activity unit, it's an activity KR.
---
## Red Flag 8: Top-down only, no bottom-up
**Symptom.** Leadership sets OKRs and hands them to the team. The team had no input.
**Why it's bad.** OKRs work best when combined top-down (strategic direction) with bottom-up (team insight). Pure top-down OKRs reduce team ownership; the team becomes execution-only and silently disengages.
**Bad example:**
> "VP of Product email: 'Here are the Q3 OKRs for your team. Please confirm by Friday.'"
**Good example:**
> "Q3 OKR process: (1) Leadership shares strategic priorities and constraints (top-down). (2) Each team drafts 2-3 candidate OKR sets aligned to those priorities (bottom-up). (3) Joint review: team defends, leadership challenges, single OKR set committed. (4) Both sides sign the OKR doc."
**How to catch it.** Ask the team: "did you write this, or did leadership?" If pure top-down, ownership is weak.
---
## Red Flag 9: KRs that all hit 100% — every quarter
**Symptom.** Team completes 100% of KRs three quarters in a row.
**Why it's bad.** Sustained 100% completion is sandbagging at the team level. Wodtke's frame: confidence at 60-70%, so on average teams hit roughly 70% of KRs. Three quarters at 100% means targets were locked at 100% confidence — the OKR is not stretching the team.
**Bad example:**
> "Q1: 3/3 KRs hit. Q2: 3/3. Q3: 3/3. Team celebrated for consistent delivery."
**Good example:**
> "Q1: 2/3 KRs hit (KR3 missed at 75%). Q2: 3/3 hit. Q3: 1/3 hit (an experiment failed and we learned why). Retrospective: hit-rate of 6/9 (67%) — close to Wodtke target of 60-70%. Team is genuinely stretched. The Q3 miss is the most-discussed item in the retro because it taught us the most."
**How to catch it.** Look at last 3 quarters of KR hit-rates. > 90% sustained is sandbagging; < 30% is demoralizing. 60-70% is healthy.
---
## Red Flag 10: Set-and-forget
**Symptom.** OKRs are set at quarter start. The next time the team reviews them is at quarter end.
**Why it's bad.** OKRs without weekly check-ins drift. Teams forget the focus; work fills with non-OKR activities; the quarter ends in surprise. Weekly confidence reviews surface a drifting KR while there is still time to act on it.
**Bad example:**
> "OKR doc created Apr 1. Next review: Jun 25. (Mid-quarter activity: team works on roadmap items, some aligned with OKR, some not.)"
**Good example:**
> "Weekly check-in cadence (every Monday, 15 min): per KR, team rates confidence red/yellow/green and notes the leading indicator. Red KRs require a 1-week action to either unblock or accept the miss. Confidence trend reviewed monthly with the manager. Quarter end is calibration, not surprise."
**How to catch it.** Open the calendar. If there is no recurring OKR check-in, the OKRs will drift.
---
## Red Flag 11: Validator passes but strategy is wrong
**Symptom.** `okr_validator.py` scores the OKR set 92/100. The OKR is structurally perfect. But the team is solving the wrong problem.
**Why it's bad.** The validator grades form (qualitative Objective, measurable KRs, counter-metric present). It cannot grade strategic substance. A 92/100 OKR can still be the wrong commitment for the company.
**Bad example:**
> "OKR scored 92/100. Objective: 'Become the most loved customer-support tool.' KRs measurable, counter present. (Problem: the company strategy this quarter is enterprise expansion, not SMB support tooling. The OKR is aligned to the team's preference, not company strategy.)"
**Good example:**
> "OKR scored 92/100 + alignment review: Q3 company priorities are enterprise expansion. This OKR is SMB-tooling-focused. Conflict. Discussion with VP Product: re-scope the Objective to 'Win the enterprise support buyer in Q3'. Validator re-runs; new score 88/100. Less polished structurally but strategically correct."
**How to catch it.** Ask: "How does this OKR align with company-level priorities for the quarter?" If the answer is hand-wavy, the OKR is locally optimized.
---
## Red Flag 12: OKR = roadmap
**Symptom.** The Q3 OKR doc lists every roadmap item the team plans to ship.
**Why it's bad.** OKRs are not a roadmap. The roadmap is the menu; the OKR is the chosen dish. An OKR that lists every initiative is a backlog disguised as goal-setting. The team has not made a focus choice.
**Bad example:**
> "Q3 OKR:
> KR1: Ship the dashboard redesign.
> KR2: Ship mobile push notifications.
> KR3: Ship the Slack integration.
> KR4: Ship enterprise SSO.
> KR5: Ship the new pricing page."
**Good example:**
> "Q3 OKR: 'Make mid-market the most natural buyer for our product.'
> KR1: Mid-market signups (200-1000 employees) from 4% of total to 12%.
> KR2: Mid-market trial-to-paid conversion from 18% to 30%.
> KR3 (counter): SMB conversion does not drop below 22%.
> Initiatives that support this OKR: pricing page redesign, mid-market case studies, sales enablement. (The dashboard redesign and Slack integration are on the roadmap but are not Q3 OKR-driving work.)"
**How to catch it.** Count KRs. > 4 per Objective is a flag — the team is listing roadmap items, not committing to outcomes.
---
## Red Flag Quick Reference
| # | Anti-pattern | One-line check |
|---|---|---|
| 1 | Output disguised as KR | Could we hit this and have zero business impact? |
| 2 | Sandbagging at 100% confidence | What is the team's confidence percentage? |
| 3 | OKR drift mid-quarter | Did week-8 targets shift from week-1 targets? |
| 4 | 5+ Objectives per team | Count Objectives. |
| 5 | Missing counter-metric | Could the team hit these by doing something harmful? |
| 6 | Numbers in the Objective | Read the Objective. Does it contain a number? |
| 7 | Activity metrics dressed as KRs | Is the KR unit an activity count? |
| 8 | Top-down only | Did the team write the OKR, or just receive it? |
| 9 | 100% hit-rate sustained | 3-quarter hit-rate. > 90%? |
| 10 | Set and forget | Is there a recurring weekly check-in? |
| 11 | Validator passes but strategy wrong | How does this align with company priorities? |
| 12 | OKR = roadmap | > 4 KRs per Objective? |
## Related Reading
- SKILL.md Troubleshooting
- references/okr-best-practices.md
- `north-star-metric/` (KRs should move input metrics for the NSM)
- `outcome-roadmap/` (initiatives that support the OKR live here, not in the OKR)
- Christina Wodtke, *Radical Focus* (2nd ed., 2021)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |