Prompt Library productivity intermediate

ChatGPT Prompts for OKRs: Write Objectives and Key Results That Work

ChatGPT prompts for writing effective OKRs. Quarterly planning frameworks, KR scoring guides, and OKR cascade templates for teams and individual contributors.

Tested on: GPT-4oClaude 4

The Prompt

Act as an OKR coach who has implemented the framework at companies from Series A startups to Fortune 500 divisions.
Write OKRs for:
Team/individual: {team name or role}
Level: {company / department / team / individual contributor}
Time period: {Q3 2026 / H2 2026 / annual}
Company-level priority this quarter: {top company priority that these OKRs should align to}
Key activities or projects for this period: {what will this team/person actually be working on}
Current performance baseline: {where are things now — relevant metrics}
Ambition level: {conservative / ambitious / moonshot}

Output:
1. OKR set (3 Objectives, each with 3-4 Key Results):

For each Objective:
- Objective: [What you want to achieve — inspiring, qualitative, memorable]
- KR1: [Measurable result — numerical, specific, time-bound]
- KR2: [Measurable result]
- KR3: [Measurable result]
- KR4 (optional): [Measurable result]
- How to score at end of quarter (0.0-1.0 scale rubric for each KR)

2. OKR quality check for each:
- Is the Objective inspirational and clear?
- Are KRs outputs (results), not activities (tasks)?
- Is each KR binary-measurable or clearly gradable?
- Does this OKR set ladder up to the stated company priority?

3. Grading rubric: what 0.3 / 0.7 / 1.0 looks like for each KR

Constraints:
- Objectives must be qualitative — no numbers in the objective statement
- KRs must be quantitative — no KR without a number or percentage
- KRs are outcomes, not activities ("Increase NPS to 50" not "Run NPS survey")
- 0.7 should represent strong performance — not just meeting the minimum
- OKRs at 1.0 consistently signal the target was set too conservatively

Variables to fill in

  • {team/individual} Team name or role these OKRs are for
  • {company priority} The top company priority these OKRs should align to
  • {key activities} What will actually be worked on this period
  • {performance baseline} Current state — relevant metrics and where you're starting from

How to use this prompt

  1. Run this at the start of every quarter before team planning sessions
  2. Use the OKR quality check as a review rubric for every OKR set before publishing
  3. Share the grading rubric with your team at the start of the quarter — no surprises at scoring
  4. Review OKR progress at 6-week intervals — not just at the end of the quarter
OKR planning on whiteboard with team members reviewing quarterly objectives
Photo by Alvaro Reyes on Unsplash

Activities are not Key Results

The most common OKR mistake is writing activities as KRs: ‘Launch new onboarding flow’ is an activity. ‘Increase day-30 retention from 45% to 60%’ is a Key Result. The distinction matters because activities can be completed and still fail to produce the desired outcome. KRs are explicitly tied to business impact — completing them means something improved.

0.7 is the target, not the minimum

In the OKR framework, consistently hitting 1.0 means your targets were set too conservatively. The ambition level should produce a score of 0.6-0.8 when teams perform well. This calibration prevents the gaming that happens when teams set safe targets they can easily beat — and signals genuine stretch when 0.7 is achieved.

Company OKRs must cascade or they’re just goals

A team OKR that doesn’t connect to a company-level objective is just a goal — it has no strategic alignment and won’t get resourcing prioritization when things get constrained. The ‘ladder up’ quality check in this prompt forces every OKR set to trace back to at least one company-level priority. If it doesn’t connect, it either shouldn’t be an OKR or the company’s OKRs are incomplete.