FrameworkTemplateintermediate11 min read

OKR & Goal Setting Prompt Guide

Set ambitious, measurable goals that drive real business outcomes

OKRs (Objectives and Key Results) have powered growth at Google, Intel, and thousands of high-performing companies. But most OKRs fail because they are either too vague to act on or too conservative to inspire.

The problem is not OKRs themselves. The problem is writing them without the right structure. This guide gives you AI prompting frameworks to generate OKRs that actually align teams and drive measurable outcomes.

Insight

Great OKRs answer two questions: “Where do we want to go?” (Objective) and “How will we know we are getting there?” (Key Results).

Anatomy of Great OKRs

Before prompting AI, understand the building blocks. Every OKR system has three layers:

1

Objective

What you want to achieve. Qualitative, inspirational, and time-bound. Should make the team excited to get out of bed.
2

Key Results

How you measure progress. Quantitative, specific, and measurable. Usually 3-5 per objective. No gray area on success.
3

Initiatives

The work you do to move key results. Projects, tasks, and experiments. These are NOT part of the OKR itself but flow from it.
Before
Write some OKRs for our marketing team.
After
Write Q2 OKRs for our B2B SaaS marketing team.

Context:
- Company goal: Grow ARR from $2M to $3M by year end
- Team size: 5 people (2 content, 2 demand gen, 1 brand)
- Current challenges: Low MQL to SQL conversion (12%, target 25%)

Requirements:
- 2-3 objectives maximum
- 3-4 key results per objective
- Key results must be measurable with current tools (HubSpot, GA4)
- Include at least one "health metric" to prevent gaming

The SMART-ER Framework for Key Results

Traditional SMART goals are not ambitious enough for OKRs. Use SMART-ER to ensure your key results stretch the team while staying grounded.

1

Specific

Clear and well-defined. No ambiguity about what success looks like.
2

Measurable

Quantifiable with a number. You can track progress week over week.
3

Ambitious

Stretches the team beyond comfortable. 70% achievement is often the goal.
4

Relevant

Connects to company strategy. Every team member understands why it matters.
5

Time-bound

Has a deadline. Typically quarterly for OKRs.
6

Evaluated

Reviewed regularly (weekly check-ins, quarterly scoring).
7

Revised

Adjusted based on learnings. OKRs are not set in stone.

Pro Tip

Include SMART-ER criteria in your AI prompts to get key results that hit the right balance of ambitious and achievable.

Prompt Templates

Use these templates as starting points. The more context you provide about your business, the better the OKRs.

Company OKRs

Company-level OKRs set the direction for the entire organization. They should be ambitious enough to inspire but clear enough to cascade.

Company OKR Prompt
Write company OKRs for [COMPANY NAME] for [TIME PERIOD].

COMPANY CONTEXT:
- Industry: [YOUR INDUSTRY]
- Stage: [STARTUP/GROWTH/ENTERPRISE]
- Current ARR/Revenue: [AMOUNT]
- Team size: [NUMBER] employees
- Primary business model: [B2B/B2C/MARKETPLACE/etc.]

STRATEGIC PRIORITIES:
1. [TOP PRIORITY - e.g., "Expand into enterprise market"]
2. [SECOND PRIORITY - e.g., "Improve customer retention"]
3. [THIRD PRIORITY - e.g., "Build platform capabilities"]

CURRENT CHALLENGES:
- [CHALLENGE 1]
- [CHALLENGE 2]

REQUIREMENTS:
- 3-4 company-level objectives maximum
- 3-5 measurable key results per objective
- At least one objective focused on team/culture
- Key results should be ambitious (70% achievement = success)
- Include baseline metrics where known

FORMAT:
For each OKR, provide:
- Objective (inspiring, qualitative)
- Key Results (specific, measurable)
- Why this matters (1-2 sentences on strategic importance)

Team OKRs

Team OKRs translate company objectives into functional goals. They should clearly connect to company OKRs while being actionable by the team.

Team OKR Prompt
Write team OKRs for [TEAM NAME] for [TIME PERIOD].

COMPANY OKRS (for alignment):
Objective: [RELEVANT COMPANY OBJECTIVE]
Key Results:
- [KR1]
- [KR2]

TEAM CONTEXT:
- Function: [ENGINEERING/MARKETING/SALES/etc.]
- Team size: [NUMBER]
- Key responsibilities: [LIST 2-3]
- Current performance: [BRIEF SUMMARY]

TEAM-SPECIFIC CHALLENGES:
- [CHALLENGE 1]
- [CHALLENGE 2]

RESOURCES & CONSTRAINTS:
- Budget: [AMOUNT or "No additional budget"]
- Headcount: [CURRENT + PLANNED HIRES]
- Key dependencies: [OTHER TEAMS/SYSTEMS]

REQUIREMENTS:
- 2-3 objectives that clearly ladder to company OKRs
- 3-4 key results per objective
- Include leading indicators (early signals) and lagging outcomes
- At least one key result focused on quality/health metrics
- All key results must be measurable by the team directly

Warning

Team OKRs should not just be company OKRs divided by headcount. Each team needs objectives that reflect their unique contribution to company success.

Individual OKRs

Individual OKRs help team members see how their work contributes to bigger goals. Keep them focused: 1-2 objectives maximum.

Individual OKR Prompt
Write individual OKRs for a [ROLE TITLE] for [TIME PERIOD].

TEAM OKRS (for alignment):
Objective: [TEAM OBJECTIVE]
Key Results:
- [KR1]
- [KR2]

INDIVIDUAL CONTEXT:
- Role: [TITLE]
- Experience level: [JUNIOR/MID/SENIOR]
- Key responsibilities: [LIST 2-3]
- Development goals: [WHAT THEY WANT TO GROW IN]

CURRENT PROJECTS:
- [PROJECT 1]: [BRIEF DESCRIPTION]
- [PROJECT 2]: [BRIEF DESCRIPTION]

REQUIREMENTS:
- 1-2 objectives maximum (focus is key)
- 2-3 key results per objective
- Key results should be within individual's control
- Include at least one growth/learning key result
- Balance output metrics with quality metrics

Key Results Brainstorming

Already have an objective but struggling with key results? Use this prompt to generate options.

Key Results Brainstorming Prompt
Generate 8-10 potential key results for this objective:

OBJECTIVE: [YOUR OBJECTIVE]

CONTEXT:
- Team/Level: [COMPANY/TEAM/INDIVIDUAL]
- Time period: [QUARTER/HALF/YEAR]
- Current baseline metrics (if known):
  - [METRIC 1]: [CURRENT VALUE]
  - [METRIC 2]: [CURRENT VALUE]

REQUIREMENTS FOR KEY RESULTS:
- Must be measurable with a specific number
- Mix of leading indicators and lagging outcomes
- Include at least one "health metric" to prevent gaming
- Range from conservative (80% confident) to ambitious (40% confident)

FORMAT:
For each key result, provide:
- The key result statement
- Current baseline (if known) vs target
- Confidence level (how likely to achieve if we execute well)
- How we would measure it

OKR Examples by Function

Reference these examples when prompting for function-specific OKRs. Adapt the metrics to your business context.

Objective: Deliver a rock-solid platform that customers can depend on

  • Achieve 99.95% uptime (up from 99.7%)
  • Reduce P1 incidents from 4/month to 1/month
  • Decrease mean time to recovery from 45 min to 15 min
  • Ship 0 critical bugs to production (health metric)

Objective: Accelerate delivery without sacrificing quality

  • Reduce deployment lead time from 2 weeks to 3 days
  • Increase deployment frequency from weekly to daily
  • Maintain test coverage above 80%
  • Reduce escaped defects by 50%

Objective: Build a demand generation engine that fuels predictable growth

  • Generate 500 MQLs per month (up from 300)
  • Improve MQL to SQL conversion from 12% to 25%
  • Reduce cost per MQL from $150 to $100
  • Maintain lead quality score above 7/10 (health metric)

Objective: Establish thought leadership in our category

  • Grow organic traffic from 10K to 25K monthly visitors
  • Achieve 3 tier-1 media mentions
  • Launch podcast with 1,000+ monthly downloads
  • Increase branded search volume by 40%

Objective: Crush our revenue targets while building a repeatable process

  • Close $1.5M in new ARR (up from $1M target)
  • Improve win rate from 20% to 30%
  • Reduce average sales cycle from 45 to 30 days
  • Maintain customer NPS above 50 for new deals (health metric)

Objective: Expand our footprint in existing accounts

  • Grow expansion revenue to 30% of total bookings
  • Increase average deal size from $15K to $25K
  • Achieve 120% net revenue retention
  • Complete QBRs with 100% of enterprise accounts

Objective: Deliver features that customers love and actually use

  • Achieve 40% adoption of new features within 30 days of launch
  • Improve product NPS from 35 to 50
  • Reduce feature request backlog by 25%
  • Maintain DAU/MAU ratio above 40% (health metric)

Objective: Become the obvious choice for enterprise customers

  • Ship SSO and SCIM provisioning with 3 design partners
  • Achieve SOC 2 Type II certification
  • Reduce enterprise onboarding time from 6 weeks to 2 weeks
  • Win 2 competitive deals against [COMPETITOR]

Common OKR Mistakes

Include these anti-patterns in your prompts to help AI avoid common pitfalls.

  • Too many objectives: More than 3-5 objectives dilutes focus. If everything is a priority, nothing is.
  • Key results as tasks: “Launch new website” is a task. “Increase conversion rate from 2% to 4%” is a key result.
  • Sandbagging: Setting easy targets to guarantee success defeats the purpose. Aim for 70% achievement.
  • No baseline: You cannot improve what you do not measure. Always include current state.
  • Vanity metrics: Page views and downloads are vanity metrics. Revenue and retention are outcomes.
  • No health metrics: Without guardrails, teams game the numbers. Always include quality metrics.

Warning

When prompting AI, explicitly state: “Avoid these common mistakes: [list].” This produces significantly better results.

Cascading OKRs Across the Organization

The real power of OKRs comes from alignment. Use this prompt to ensure team and individual OKRs ladder up to company goals.

OKR Alignment Review Prompt
Review these OKRs for alignment and suggest improvements.

COMPANY OKR:
Objective: [COMPANY OBJECTIVE]
Key Results:
- [KR1]
- [KR2]
- [KR3]

TEAM OKRS TO REVIEW:
[TEAM 1 NAME]:
Objective: [OBJECTIVE]
Key Results: [LIST]

[TEAM 2 NAME]:
Objective: [OBJECTIVE]
Key Results: [LIST]

REVIEW CRITERIA:
1. Does each team OKR clearly contribute to a company key result?
2. Are there gaps? (Company KRs not covered by any team)
3. Are there overlaps? (Multiple teams owning the same outcome)
4. Do the team targets sum up to company targets?

PROVIDE:
- Alignment score (1-10) with explanation
- Specific gaps and how to address them
- Suggested rewrites for misaligned OKRs
- Recommendations for cross-team dependencies

Success

OKR alignment is not just top-down. Teams should also influence company OKRs bottom-up based on what they know is achievable.

Review and Adjustment Prompts

OKRs are not set-and-forget. Use these prompts for regular check-ins and quarterly reviews.

Mid-Quarter Check-in Prompt
Generate a mid-quarter OKR check-in analysis.

OKR:
Objective: [OBJECTIVE]
Key Results:
- KR1: [TARGET] | Current: [ACTUAL] | On track: [YES/NO]
- KR2: [TARGET] | Current: [ACTUAL] | On track: [YES/NO]
- KR3: [TARGET] | Current: [ACTUAL] | On track: [YES/NO]

CONTEXT:
- Time elapsed: [X weeks of Y total]
- Major initiatives completed: [LIST]
- Blockers encountered: [LIST]
- Resources used vs planned: [COMPARISON]

PROVIDE:
1. Trajectory analysis: At current pace, where will we land?
2. Risk assessment: What needs to change to hit targets?
3. Recommendations:
   - Quick wins to accelerate progress
   - KRs that may need to be adjusted (and why that is okay)
   - Resources or support needed
4. Talking points for the team check-in meeting
Quarterly Retrospective Prompt
Generate an end-of-quarter OKR retrospective.

OKR RESULTS:
Objective: [OBJECTIVE]
Key Results:
- KR1: Target [X] | Achieved [Y] | Score: [0.0-1.0]
- KR2: Target [X] | Achieved [Y] | Score: [0.0-1.0]
- KR3: Target [X] | Achieved [Y] | Score: [0.0-1.0]

Overall Score: [AVERAGE]

CONTEXT:
- What went well: [LIST]
- What did not go well: [LIST]
- Surprises (good and bad): [LIST]
- External factors that impacted results: [LIST]

PROVIDE:
1. Summary: 3-sentence narrative of the quarter
2. Analysis:
   - Which KRs were well-calibrated vs too easy/hard?
   - What would we do differently?
   - What did we learn about our capabilities?
3. Implications for next quarter:
   - Should this objective continue?
   - How should we adjust targets?
   - What new objectives should we consider?

Next Steps

You now have the frameworks to generate OKRs that align teams and drive outcomes. The key is providing enough context about your business, current performance, and strategic priorities.

Generate your OKRs with guided questions

Instead of filling in templates manually, answer a few questions about your company, team, and goals. AskSmarter builds a comprehensive OKR prompt tailored to your situation.

Start building free

How many OKRs should we have?

Company level: 3-5 objectives with 3-5 key results each. Team level: 2-3 objectives. Individual level: 1-2 objectives. Less is more.

Should OKRs be tied to compensation?

Most OKR experts recommend against it. Tying OKRs to compensation encourages sandbagging and discourages ambitious goals. Keep OKRs separate from performance reviews.

What is a good OKR score?

70% achievement (0.7) is typically considered success for ambitious OKRs. If you are hitting 100% every quarter, your targets are not ambitious enough.

How often should we review OKRs?

Weekly team check-ins on progress, monthly deeper reviews, and quarterly scoring and retrospectives. OKRs are living documents, not annual goals.