Create well-structured Objectives and Key Results (OKRs) that drive focus, alignment, and measurable outcomes. Ensures objectives are inspiring and key results are specific, measurable, and ambitious.

Core principle: Objectives describe where you want to go. Key Results tell you if you're getting there.

When to Use

Output Format

yaml

okr_set:
  period: "[Q1 2026 | FY2026]"
  owner: "[Team or Individual]"
  parent_okr: "[Company/Department OKR this supports]"
  
  objectives:
    - id: "O1"
      objective: "[Qualitative, inspiring goal]"
      rationale: "[Why this matters now]"
      
      key_results:
        - id: "KR1.1"
          key_result: "[Specific, measurable outcome]"
          metric: "[What we're measuring]"
          baseline: "[Current value]"
          target: "[Target value]"
          stretch_target: "[Aspirational value]"
          measurement_method: "[How we'll measure]"
          tracking_frequency: "[Weekly | Monthly]"
          owner: "[Person responsible]"
          confidence: "[High | Medium | Low]"
          initiatives: ["[Related project or effort]"]
        
        - id: "KR1.2"
          key_result: "[Another measurable outcome]"
          # ... same structure
      
      dependencies:
        - "[What must be true for success]"
      
      risks:
        - risk: "[What could prevent achievement]"
          mitigation: "[How we'll address]"
  
  initiatives:
    - id: "INIT-01"
      name: "[Project/effort name]"
      supports: ["KR1.1", "KR2.3"]
      owner: "[Owner]"
      timeline: "[Start - End]"
  
  grading_criteria:
    score_definitions:
      "0.0": "No progress"
      "0.3": "Made some progress"
      "0.5": "Achieved about half"
      "0.7": "Achieved target"
      "1.0": "Achieved stretch target"

OKR Structure

Objectives: The Qualitative Goal

Attribute	Description	Example
Inspirational	Makes people want to achieve it	"Delight enterprise customers"
Qualitative	Direction, not number	Not "Increase NPS to 50"
Action-oriented	Implies movement	"Build", "Create", "Transform"
Timebound	Achievable in period	Not a multi-year vision

Key Results: The Measurable Outcomes

Attribute	Description	Example
Specific	Clear what success looks like	"Reduce p95 latency to <100ms"
Measurable	Quantifiable with data	"Increase conversion from 5% to 8%"
Achievable	Possible but ambitious	70% probability of success
Relevant	Proves objective progress	Tied to objective intent
Timebound	Deliverable in period	End of quarter

code

Increase/Decrease [metric] from [X] to [Y]
Achieve [milestone] by [date]
Launch [capability] with [success criteria]
[X]% of [population] does [action]

OKR Quality Checklist

Objective Quality

Key Result Quality

Cascade Structure

code

Company Objective: "Become the market leader in our space"
    │
    ├── Company KR: "Increase market share from 15% to 25%"
    │         │
    │         ├── Sales O: "Dominate enterprise segment"
    │         │      └── Sales KR: "Close 15 enterprise deals >$500K"
    │         │
    │         └── Product O: "Build unmatched product capability"
    │                └── Product KR: "Launch 3 industry-first features"
    │
    └── Company KR: "Achieve #1 analyst ranking"
              │
              └── Marketing O: "Establish thought leadership"
                     └── Marketing KR: "10 executive speaking slots at tier-1 events"

Scoring and Grading

Score Methodology

Expected Score Distribution

Common Mistakes

Mistake	Problem	Fix
KRs are tasks	"Launch feature X"	Focus on outcome of launch
Too many OKRs	Loss of focus	3-5 objectives, 2-5 KRs each
No baseline	Can't measure progress	Always state "from X to Y"
Sandbagging	Easy targets don't inspire	70% confidence = right difficulty
Binary KRs	"Ship project" (0 or 1)	Add quality dimension
Business as usual	Not driving change	OKRs are for improvement
No owner	Diffused responsibility	Single DRI per KR

OKR vs KPI

Use OKRs for: What you want to improve Use KPIs for: What you want to maintain

Review Cadence

OKR Template Examples

Product Team

yaml

objectives:
  - id: "O1"
    objective: "Deliver an onboarding experience users love"
    key_results:
      - key_result: "Increase onboarding completion from 45% to 75%"
      - key_result: "Reduce time-to-first-value from 7 days to 1 day"
      - key_result: "Achieve onboarding NPS of 60 (up from 35)"

Engineering Team

yaml

objectives:
  - id: "O1"
    objective: "Build a platform that scales with confidence"
    key_results:
      - key_result: "Reduce p99 API latency from 800ms to 200ms"
      - key_result: "Achieve 99.95% uptime (up from 99.5%)"
      - key_result: "Zero critical incidents caused by deployments"

Sales Team

yaml

objectives:
  - id: "O1"
    objective: "Establish dominance in the enterprise segment"
    key_results:
      - key_result: "Close 10 enterprise deals >$500K (up from 3)"
      - key_result: "Reduce enterprise sales cycle from 120 to 60 days"
      - key_result: "Achieve 85% enterprise renewal rate"

Score	Meaning	Interpretation
0.0 - 0.3	Red	Significant miss, requires retrospective
0.4 - 0.6	Yellow	Partial achievement, learning opportunity
0.7 - 0.9	Green	Achieved target, well executed
1.0	Blue	Exceeded stretch, exceptional performance

Aspect	OKR	KPI
Purpose	Drive change	Monitor health
Timeframe	Quarterly/Annual	Ongoing
Ambition	Stretch (70% achievable)	Realistic
Example	"Increase NPS from 32 to 50"	"Maintain NPS >30"

Cadence	Activity
Weekly	Check-in on progress, surface blockers
Monthly	Score KRs, assess trajectory
End of period	Final scoring, retrospective
Start of period	Set new OKRs, cascade alignment

okr-definition-assistant

OKR Definition Assistant

Overview

When to Use

Output Format

OKR Structure

Objectives: The Qualitative Goal

Key Results: The Measurable Outcomes

OKR Quality Checklist

Objective Quality

Key Result Quality

Cascade Structure

Scoring and Grading

Score Methodology

Expected Score Distribution

Common Mistakes

OKR vs KPI

Review Cadence

OKR Template Examples

Product Team

Engineering Team

Sales Team

Review Checklist