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/okr-best-practices.md
View on GitHub# OKR Best Practices Guide
A comprehensive reference for writing, scoring, and managing OKRs using the Radical Focus methodology.
---
## OKR Anatomy
### Objective
A qualitative, inspirational statement of what you want to achieve this quarter.
**Rules:**
- No numbers (metrics belong in key results)
- Time-bound to one quarter
- The team can directly influence it
- It is memorable enough to repeat without looking it up
**Formula:** "[Action verb] [aspirational outcome] [for whom/in what context]"
**Examples:**
| Strong Objective | Why It Works |
|-----------------|-------------|
| Become the fastest way for small teams to ship products | Aspirational, specific audience, clear direction |
| Make our customer support so good that users brag about it | Emotional, measurable through KRs, memorable |
| Establish ourselves as the go-to platform for data teams | Strategic, scoped to a segment, time-pressured |
| Weak Objective | Why It Fails |
|---------------|-------------|
| Increase revenue by 20% | That is a key result, not an objective |
| Improve things | Too vague to act on |
| Launch the mobile app | That is a project milestone, not an outcome |
| Be the best | Not specific enough to know when achieved |
---
## Key Result Examples
### Outcome-Focused (Good)
| Key Result | Metric | Why It Works |
|-----------|--------|-------------|
| Reduce customer onboarding time from 3 days to 4 hours | Hours to first value | Measures user impact, not team activity |
| Increase weekly active users from 10K to 25K | WAU | Measures adoption, not feature count |
| Improve NPS from 32 to 55 | Net Promoter Score | Measures satisfaction, not effort |
| Reduce support ticket volume from 500/week to 200/week | Tickets per week | Measures product quality, not support team size |
### Output-Focused (Bad)
| Key Result | Why It Fails | Better Version |
|-----------|-------------|----------------|
| Launch 5 new features | Measures activity, not impact | "Increase feature adoption rate from 15% to 40%" |
| Hire 3 engineers | Hiring is a means, not an end | "Reduce average PR review time from 48h to 12h" |
| Write 20 blog posts | Content quantity is not content impact | "Increase organic search traffic from 5K to 15K monthly visits" |
| Complete the migration | Completion is binary, not measurable progress | "Migrate 95% of users to the new platform with less than 2% support escalation rate" |
---
## Common OKR Mistakes
### 1. Sandbagging
**Problem:** Setting targets you know you will hit (100% confidence).
**Why it matters:** OKRs are meant to stretch. If you always hit 100%, your targets are too easy.
**Fix:** Aim for 60-70% confidence. Hitting 70% of an ambitious OKR is better than hitting 100% of a safe one.
### 2. Too Many OKRs
**Problem:** Team has 5+ objectives with 15+ key results.
**Why it matters:** OKRs create focus. Too many creates the illusion of focus while spreading effort thin.
**Fix:** One objective is ideal. Two is acceptable. Three is the absolute maximum per team per quarter.
### 3. Confusing OKRs with KPIs
**Problem:** Using OKRs to track business-as-usual metrics.
**Why it matters:** KPIs track health. OKRs drive change. "Maintain 99.9% uptime" is a KPI, not an OKR.
**Fix:** Ask: "Is this something we want to change, or something we want to maintain?" Change = OKR. Maintain = KPI.
### 4. No Weekly Check-In
**Problem:** OKRs are set in January and reviewed in March.
**Why it matters:** Without weekly check-ins, OKRs are forgotten goals. The cadence is the system.
**Fix:** Every Monday, spend 15 minutes asking: "What confidence level are we at for each KR? What will we do this week to move it?"
### 5. Top-Down Only
**Problem:** Leadership dictates all OKRs with no team input.
**Why it matters:** Teams closest to the work often have the best insight into what is achievable and impactful.
**Fix:** Leadership sets company-level objectives. Teams propose their own KRs and supporting objectives.
### 6. Cascading Everything
**Problem:** Every company OKR must cascade to every team.
**Why it matters:** Forced alignment creates artificial connections and busywork.
**Fix:** Teams should align to 1-2 company objectives. Not every team needs to connect to every company goal.
---
## OKR vs KPI vs North Star Metric
### North Star Metric (NSM)
- The single metric that best captures the core value your product delivers to customers.
- It is permanent (changes rarely, if ever).
- Example: Airbnb = "Nights booked." Slack = "Messages sent in channels."
### KPIs (Key Performance Indicators)
- Ongoing health metrics that you monitor continuously.
- They have targets but are not time-bound initiatives.
- Examples: Revenue, churn rate, page load time, customer satisfaction score.
### OKRs (Objectives and Key Results)
- Quarterly ambitious goals designed to drive change.
- They expire at the end of the quarter -- you set new ones.
- They should move your KPIs and ultimately your NSM.
### How They Connect
```
North Star Metric (permanent)
|
v
KPIs (ongoing health)
|
v
OKRs (quarterly change levers)
|
v
Projects / Initiatives (the work you do)
```
**Example flow:**
- NSM: "Weekly users who complete a workflow"
- KPI: "Activation rate" (currently 45%, healthy range 50-70%)
- OKR: "Objective: Make first-time setup so intuitive that help docs become optional"
- KR1: Increase activation rate from 45% to 62%
- KR2: Reduce support tickets related to setup from 120/week to 30/week
- KR3: Achieve average time-to-first-workflow under 10 minutes (currently 35 min)
---
## Scoring and Grading OKRs
### At Quarter End
Score each key result on a 0.0 to 1.0 scale:
| Score | Meaning |
|-------|---------|
| 0.0-0.3 | Failed to make real progress |
| 0.4-0.6 | Made progress but fell short |
| 0.7-0.8 | Strong delivery (this is the sweet spot) |
| 0.9-1.0 | Hit or exceeded -- was the target ambitious enough? |
### Interpreting Scores
- **Consistently 0.9-1.0:** Targets are too easy. Stretch more next quarter.
- **Consistently 0.4-0.6:** Either targets are too aggressive, or execution needs improvement. Investigate which.
- **Consistently 0.0-0.3:** Something is broken -- wrong priorities, wrong metrics, or wrong team focus.
### The Retrospective Questions
After scoring, ask:
1. What did we learn about our customers/product/market?
2. What would we do differently if we could restart the quarter?
3. How should this inform next quarter's OKRs?
---
## OKR Cadence (Quarterly Cycle)
### Week -2 to -1: Drafting
- Review previous quarter's scores and learnings.
- Leadership drafts company-level objectives.
- Teams brainstorm their supporting OKRs.
### Week 0: Alignment
- Teams present draft OKRs to leadership.
- Resolve conflicts and overlaps.
- Finalize and publish OKRs.
### Weeks 1-12: Execution
- **Monday check-in (15 min):** Review confidence levels (green/yellow/red) for each KR. Identify blockers.
- **Mid-quarter review (Week 6):** Are we on track? Do any KRs need adjustment? (Adjusting targets is acceptable if you learned something fundamental.)
### Week 13: Scoring and Retrospective
- Score all KRs (0.0-1.0).
- Run retrospective.
- Feed learnings into next quarter's drafting.
---
## Company to Team Alignment
### Alignment Model
Company objectives set the strategic direction. Team OKRs describe how each team contributes.
```
Company Objective: "Become the market leader in developer tooling"
|
+-- Engineering OKR: "Make our CLI the fastest in the category"
| KR1: Reduce average command execution time from 800ms to 200ms
| KR2: Achieve 95% positive sentiment in developer surveys
| KR3: Reach 10K daily active CLI users (currently 3K)
|
+-- Marketing OKR: "Build developer community that drives organic adoption"
| KR1: Grow community forum from 500 to 5,000 monthly active members
| KR2: Increase organic sign-ups from 20% to 45% of total
| KR3: Achieve 3 community-contributed plugins per month
|
+-- Sales OKR: "Establish enterprise adoption playbook"
KR1: Close 5 enterprise accounts (>$100K ARR each)
KR2: Reduce enterprise sales cycle from 90 to 45 days
KR3: Achieve 90% retention rate in enterprise tier
```
### Alignment Rules
1. Not every team must align to every company objective.
2. Teams should propose their own KRs -- leadership should not dictate them.
3. If two teams have conflicting KRs, resolve before the quarter starts.
4. Shared KRs between teams need a single owner (DRI).
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: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |