okr-frameworks_skill

Overview

This skill writes effective OKRs using Christina Wodtke's best practices and Google's OKR methodology. It helps product and cross-functional teams craft inspiring objectives and measurable key results. Use it to set quarterly goals, align teams, and build clear measurement frameworks.

How this skill works

The skill generates objectives that are qualitative and motivating, then produces 3–5 measurable, outcome-focused key results per objective. It runs OKR quality checks for inspiration, time-boundedness, and ambition, and formats quarterly OKR templates and weekly check-in prompts. It also enforces measurable targets with clear baselines and finish lines.

When to use it

• Setting quarterly team or company objectives
• Aligning multiple teams around shared outcomes
• Creating measurement frameworks for product initiatives
• Converting projects or initiatives into outcome-based KRs
• Running weekly check-ins and end-of-quarter reviews

Best practices

• Write objectives that inspire and are time-bound, not task lists
• Limit to 3–5 KRs per objective and keep KRs outcome-focused, numeric, and specific
• Aim for ambitious but realistic targets (roughly 60–70% confidence)
• Prefer outcome metrics (activation, retention, revenue) over output metrics (tasks completed)
• Hold weekly check-ins: current state, blockers, and help needed

Example use cases

• Product team: define OKRs to improve onboarding speed and activation rates
• Growth team: set measurable KRs for acquisition and conversion lifts
• Engineering & design: align on delivery with outcome-based KRs rather than feature lists
• Leadership: cascade company objectives into team-level OKRs for transparency
• PMs: convert roadmap initiatives into measurable quarterly goals and create check-in cadence