Okr Framework

OKR Framework

Set and achieve ambitious goals using Objectives and Key Results for organizational alignment and measurable progress.

Overview

OKRs (Objectives and Key Results) is a goal-setting framework developed by Andy Grove at Intel and popularized by John Doerr at Google. It helps organizations define ambitious goals (Objectives) and track measurable outcomes (Key Results). This skill covers OKR structure, types, implementation, tracking, and best practices for individual, team, and organizational goal setting.

OKR Structure

Objective

Definition: What is to be achieved - significant, concrete, action-oriented, inspirational

Characteristics:

• Qualitative, not quantitative
• Ambitious yet achievable
• Time-bound (usually quarterly)
• Inspiring and motivating
• Clear direction

Good Objectives:

• "Launch revolutionary mobile experience"
• "Become the most trusted brand in our industry"
• "Build world-class engineering team"
• "Dominate the enterprise market"

Poor Objectives:

• "Increase revenue" (not inspiring, too vague)
• "Fix bugs" (not ambitious)
• "Maintain current performance" (not a stretch)

Key Results

Definition: How progress toward Objective is measured - specific, measurable, verifiable

Characteristics:

• Quantitative and measurable
• Specific and time-bound
• Aggressive yet realistic
• 3-5 per Objective
• Outcome-focused, not activity-focused

Good Key Results:

• "Increase NPS from 45 to 65"
• "Achieve 1M monthly active users"
• "Reduce customer churn from 5% to 2%"
• "Launch in 3 new markets"

Poor Key Results:

• "Improve customer satisfaction" (not measurable)
• "Work on new features" (activity, not outcome)
• "Have more meetings" (not outcome-focused)

Formula

"I will (Objective) as measured by (Key Results)"

Example:

• Objective: Launch revolutionary mobile experience
• Key Results:
  1. Achieve 4.5+ star rating in app stores
  2. Reach 500K downloads in first quarter
  3. Achieve 40% daily active user rate
  4. Reduce app crash rate to <0.1%

Types of OKRs

Committed vs. Aspirational

Committed OKRs:

• Must-dos, expected 100% achievement
• Failure requires explanation and plan
• Typically operational goals
• Example: "Meet regulatory compliance deadline"

Aspirational OKRs (Moonshots):

• Stretch goals, 60-70% achievement is success
• Push boundaries of what's possible
• Encourage innovation
• Example: "10x user growth"

Top-Down vs. Bottom-Up

Top-Down OKRs:

• Set by leadership
• Cascade down organization
• Ensure strategic alignment
• Typically 40-50% of OKRs

Bottom-Up OKRs:

• Proposed by teams and individuals
• Foster creativity and ownership
• Align with top-down goals
• Typically 50-60% of OKRs

Annual vs. Quarterly

Annual OKRs:

• Long-term strategic direction
• Anchor for quarterly OKRs
• 3-5 company-level objectives
• Reviewed quarterly, adjusted if needed

Quarterly OKRs:

• Tactical execution
• More specific and measurable
• Aligned with annual OKRs
• Most common cadence

OKR Levels

Company OKRs

Scope: Entire organization Set by: Executive team Number: 3-5 Objectives Purpose: Strategic direction and alignment

Example:

• Objective: Become market leader in enterprise SaaS
• Key Results:
  1. Achieve $100M ARR
  2. Sign 50 enterprise customers (>$500K contracts)
  3. Achieve 95% customer retention rate

Team OKRs

Scope: Department or team Set by: Team with manager Number: 3-5 Objectives per team Purpose: Support company OKRs, team-specific goals

Example (Engineering Team):

• Objective: Build scalable, reliable platform
• Key Results:
  1. Achieve 99.9% uptime
  2. Reduce page load time to <2 seconds
  3. Deploy to production 20+ times per week
  4. Reduce critical bugs by 50%

Individual OKRs

Scope: Individual contributor Set by: Individual with manager Number: 3-5 Objectives Purpose: Personal development, support team OKRs

Note: Some organizations avoid individual OKRs to prevent micromanagement and encourage team focus.

OKR Implementation

Quarterly OKR Cycle

Week 1-2: Planning

1. Leadership sets company OKRs
2. Teams draft OKRs aligned with company goals
3. Individuals draft OKRs aligned with team goals
4. Review and refine for alignment

Week 3-11: Execution

1. Weekly check-ins on progress
2. Update confidence levels
3. Address blockers
4. Adjust as needed (with justification)

Week 12: Review and Reflect

1. Score OKRs (0.0 to 1.0)
2. Reflect on what worked/didn't
3. Celebrate achievements
4. Learn from misses
5. Feed learnings into next quarter

OKR Planning Process

Step 1: Company OKRs

• Executive team proposes company OKRs
• Share with organization for feedback
• Finalize and communicate

Step 2: Team OKRs

• Teams draft OKRs supporting company goals
• Include team-specific objectives
• Review with leadership for alignment
• Finalize and share

Step 3: Individual OKRs (if used)

• Individuals draft OKRs
• Discuss with manager
• Ensure alignment with team and company
• Finalize

Step 4: Alignment Check

• Verify all OKRs ladder up to company goals
• Identify gaps or conflicts
• Adjust as needed
• Publish all OKRs transparently

Tracking and Scoring

Weekly Check-ins

Format:

• 15-30 minutes per team
• Review each Key Result
• Update progress and confidence
• Identify blockers
• Adjust priorities if needed

Confidence Levels:

• Green (On Track): 70%+ confidence of achieving
• Yellow (At Risk): 40-70% confidence
• Red (Off Track): <40% confidence

Scoring OKRs

Scale: 0.0 to 1.0

Scoring Guide:

• 0.0-0.3: Failed, significant issues
• 0.4-0.6: Made progress, fell short
• 0.7-0.9: Delivered, met expectations (for aspirational)
• 1.0: Fully achieved (expected for committed, exceptional for aspirational)

Example Scoring:

• KR: "Increase NPS from 45 to 65"
• Actual: NPS reached 58
• Score: (58-45)/(65-45) = 13/20 = 0.65

Google's Approach:

• Average of 0.6-0.7 is ideal for aspirational OKRs
• 1.0 consistently means not ambitious enough
• 0.3 or below means too ambitious or execution issues

What to Do with Scores

High Scores (0.9-1.0 consistently):

• Set more ambitious goals next quarter
• May be sandbagging
• Challenge team to stretch

Medium Scores (0.6-0.8):

• Ideal for aspirational OKRs
• Good balance of ambition and achievement
• Continue approach

Low Scores (<0.5):

• Analyze why: too ambitious, poor execution, external factors?
• Adjust ambition level or improve execution
• Learn and adapt

Best Practices

Writing Effective OKRs

Objectives:

• Start with verb (Launch, Build, Create, Achieve)
• Inspire and motivate
• Qualitative, not numbers
• Clear and concise
• Ambitious but achievable

Key Results:

• Start with verb (Increase, Reduce, Achieve, Launch)
• Include numbers and targets
• Outcome, not output
• Measurable and verifiable
• Time-bound

Alignment and Transparency

Transparency:

• All OKRs visible to entire organization
• Promotes accountability
• Enables collaboration
• Prevents duplicate efforts

Alignment:

• Team OKRs support company OKRs
• Individual OKRs support team OKRs
• Horizontal alignment across teams
• Regular alignment checks

Separation from Performance Reviews

Why Separate:

• Prevents sandbagging (setting easy goals)
• Encourages ambitious goal-setting
• Reduces fear of failure
• Promotes learning and experimentation

How to Separate:

• OKRs inform but don't determine performance ratings
• Evaluate on effort, learning, and impact
• Consider context and external factors
• Focus on growth and development

Common Mistakes

Mistake 1: Business-as-Usual OKRs

Problem: OKRs that just reflect current work, no stretch

Example: "Continue maintaining 99% uptime" (already doing this)

Solution: Set goals that require new efforts or improvements

Mistake 2: Sandbagging

Problem: Setting easy-to-achieve goals to look good

Solution: Separate OKRs from performance reviews, encourage ambition

Mistake 3: Low-Value Objectives

Problem: Achieving objective doesn't significantly benefit organization

Solution: Ensure all objectives tie to strategic priorities

Mistake 4: Insufficient Key Results

Problem: Not enough KRs to fully measure objective achievement

Solution: 3-5 KRs per objective, covering all critical dimensions

Mistake 5: Set and Forget

Problem: Writing OKRs but not reviewing or updating

Solution: Weekly check-ins, regular updates, continuous engagement

Mistake 6: Outputs vs. Outcomes

Problem: KRs focus on activities, not results

Bad: "Conduct 10 customer interviews" Good: "Increase customer satisfaction score from 7.5 to 8.5"

Mistake 7: Too Many OKRs

Problem: 10+ objectives, diluted focus

Solution: Limit to 3-5 objectives, ruthless prioritization

OKR Tools

Software Platforms

Dedicated OKR Tools:

• Weekdone: Simple, visual, good for small teams
• Perdoo: Comprehensive, strategy execution
• Gtmhub: Enterprise-grade, advanced analytics
• Ally.io: Integration-rich, real-time tracking
• Workboard: OKRs + business reviews

General Tools:

• Asana: Goals feature for OKRs
• Monday.com: Customizable for OKRs
• Jira Align: For scaled agile + OKRs
• Google Sheets: Simple, free, flexible

Spreadsheet Template

Columns:

• Objective
• Key Result
• Owner
• Start Value
• Target Value
• Current Value
• Progress %
• Confidence
• Last Updated

Using the Reference Files

When to Read Each Reference

/references/okr-examples.md — Read when writing OKRs for different functions, seeking inspiration, or understanding good vs. bad examples.

/references/implementation-guide.md — Read when rolling out OKRs organization-wide, establishing processes, or training teams on OKR methodology.

/references/tracking-and-scoring.md — Read when establishing check-in processes, scoring methodologies, or creating OKR dashboards and reports.

/references/advanced-practices.md — Read when scaling OKRs across large organizations, integrating with other frameworks, or optimizing mature OKR programs.