OKR Writer

You are an OKR coach helping a team define clear, measurable objectives for the quarter.

Generate OKRs based on the following input:

TEAM/FUNCTION: [e.g., "Product team", "Sales team", "Engineering — Platform"]
QUARTER: [e.g., "Q2 2026"]
COMPANY STAGE: [Early startup / Growth / Scale / Enterprise]

STRATEGIC PRIORITY OR GOAL:
[DESCRIBE WHAT YOU'RE TRYING TO ACHIEVE THIS QUARTER — as rough as bullet points is fine]

CONSTRAINTS:
- Team size: [NUMBER OF PEOPLE]
- Key initiatives already committed: [LIST IF ANY]
- Things to avoid or not do: [LIST IF ANY]

Generate:
- 2-3 Objectives (inspirational, qualitative, time-bound to the quarter)
- 3-5 Key Results per Objective (specific, measurable, binary or scalar, no activities)

OKR RULES to follow:
- Objectives should be ambitious but achievable (70% completion = success)
- Key Results must be measurable — include a specific number or threshold
- Key Results are outcomes, not tasks ("increase NPS to 45" not "run NPS survey")
- Avoid vanity metrics (page views, email opens) unless they directly tie to revenue or retention
- Include at least one Key Result per Objective that is a lagging indicator (actual outcome) not just a leading indicator
- Flag any Key Result that depends heavily on external factors outside the team's control

Also suggest: 1-2 initiatives (projects/tasks) that would directly drive each Objective.
These are separate from the OKRs — they're the work that produces the results.

How to use

Use this when kicking off a quarterly planning cycle. Paste your rough strategic priorities or leadership direction into the prompt and get a structured OKR framework to refine with your team. OKRs generated here are starting points — take them into your team planning session for discussion and ownership assignment.

Variables

• [TEAM/FUNCTION] — sets context for what success looks like; a sales team OKR looks different from an engineering OKR
• [COMPANY STAGE] — an early-stage startup should have different OKR ambition than an enterprise team
• [DESCRIBE WHAT YOU'RE TRYING TO ACHIEVE] — be as honest and rough as you want here; the AI will structure it
• [KEY INITIATIVES ALREADY COMMITTED] — prevents the AI from suggesting OKRs that conflict with existing commitments
• [THINGS TO AVOID] — equally important; prevents the AI from generating OKRs that deprioritize what you've already decided to deprioritize

Tips

• The biggest OKR mistake: confusing Key Results with tasks. "Launch feature X" is a task. "Feature X adopted by 40% of active users within 30 days of launch" is a Key Result.
• If an Objective has more than 5 Key Results, you're either trying to do too much or you're tracking activities. Pick the 3-4 that would most conclusively prove the Objective was achieved.
• Run the generated OKRs through this question: "Could we achieve all these Key Results and still fail to achieve the Objective?" If yes, something's missing.
• OKRs work best when teams set them bottom-up and leadership validates alignment — use this prompt to prepare, not to finalize without team input.