Generating Okrs

YAML
---
name: generating-okrs
description: Creates aligned Objectives and Key Results with measurement frameworks. Use when developing quarterly or annual goal-setting systems, aligning team objectives with company strategy, or establishing measurable performance targets.
---

# OKR Generation

OBJECTIVE: Improve customer satisfaction and retention
KEY RESULTS:
1. Increase Net Promoter Score from 7.2 to 8.5 (measure: monthly NPS survey)
2. Reduce customer churn rate from 5% to 3% (measure: monthly cohort analysis)
3. Achieve 95% customer support ticket resolution within 24 hours (measure: support system metrics)

Timeline: Q1 2024
Owner: Customer Success Team

1. Define the Objective

   • Start with company/team priorities
   • Create 1 inspiring, qualitative goal
   • Ensure alignment with higher-level OKRs

2. Develop Key Results

   • Create 2-4 measurable outcomes
   • Set baseline and target values
   • Include measurement method for each

3. Validate Alignment

   • Check vertical alignment (supports parent OKR)
   • Check horizontal alignment (no conflicts with peer OKRs)
   • Ensure stretch but achievable targets

4. Establish Measurement Framework

   • Define data sources
   • Set review cadence (weekly/monthly)
   • Assign measurement owners

Example 1 - Product Team: Input: "We need to improve our mobile app" Output:

OBJECTIVE: Deliver exceptional mobile user experience
KEY RESULTS:
1. Increase mobile app store rating from 3.8 to 4.5 stars
2. Reduce app crash rate from 2.1% to <0.5%
3. Achieve 40% mobile user engagement rate (DAU/MAU)

Example 2 - Sales Team: Input: "Grow revenue this quarter" Output:

OBJECTIVE: Accelerate sustainable revenue growth
KEY RESULTS:
1. Generate $2.5M in new bookings (vs $1.8M baseline)
2. Increase average deal size from $25K to $35K
3. Achieve 25% conversion rate from qualified leads

• One Objective per focus area - Avoid objective overload
• Outcomes over outputs - KRs measure impact, not activities
• Stretch targets - Aim for 70% completion as success
• Clear ownership - Every OKR has a single owner
• Regular check-ins - Weekly progress reviews
• Scoring system - Use 0.0-1.0 scale for KR achievement

• Too many objectives - Limit to 3-5 per team/quarter
• Activity-based KRs - "Launch feature X" vs "Increase user adoption by Y%"
• Sandbagging targets - Setting easily achievable goals
• Missing measurement - No clear way to track progress
• Misaligned timing - KRs with different measurement periods
• Binary KRs - Results should be gradual, not yes/no