After 28 OKR cycles, this founder shares the Claude Skill he uses to review team OKRs
lukeharries · x · 2026-10-01
lukeharries shares the full Claude Skill he refined over 7 years (28 OKR cycles) to review and improve team OKR plans.
Key rules in the skill:
- OKRs should form a metric tree flowing down from company KPIs, with MECE objectives and covered critical drivers
- Max 4-5 objectives per team (never more than headcount), each person in one objective, max 3-4 KRs per objective, always assessable — no vague "improve X"
- Product eng teams should center on what they want to ship; growth teams need a mix of output metrics and input actions with SMART goals (e.g. launch an AI landing-page system and ship 20 pages by end of November, lifting signup conversion from 3.1% to 4%)
- Think in systems and agentically, building compounding systems; teams should own what they directly control; keep hiring out of OKRs unless it's a critical bottleneck
More from coding & agent
- Ethan Mollick: agent swarms self-organize, solving Navier-Stokes in 88 hours — no human managers needed — One Useful Thing (Ethan Mollick) · 2026-10-01
- 10 GitHub repos to level up Claude Code: skills for planning, testing and security — Shruti_0810 · 2026-10-01
- Dev predicts SaaS cycle will repeat, this time built for agents — brianmichel · 2026-10-01
- Hands-on GPT-6 Astra evals: big agentic gains, but ARC-AGI-3 scores swing wildly by harness — No-Soil-5789 · 2026-10-01
- After another Claude ban, dev ditches Anthropic for local models orchestrated by Codex — lxfater · 2026-10-01
- Developer: after two days of all-in coding, Devin is the agent I trust most to finish tasks — jonathan_wilke · 2026-10-01