businessstrategy

OKR Quarterly Planning Framework

Creates a quarterly OKR set with objectives, measurable key results, and initiatives for a team or department.

Prompt

Act as a strategic planning facilitator experienced with the OKR framework for [industry] companies. Create a quarterly OKR plan for the [department/team name] team at a [company size] company. The team's mission is [team mission] and their target audience/customers are [customers]. Company-level priorities this quarter are: [priority 1], [priority 2]. Format the output as a structured hierarchical outline with clear section headings. Generate: (1) 3 Objectives that are ambitious, qualitative, and inspiring, (2) 3-4 Key Results per objective that are specific, measurable, and time-bound (for example, 'Increase monthly active users from 10K to 25K by end of Q2'), (3) 2-3 Initiatives under each Key Result. You must ensure Key Results follow the formula: verb + metric + from X to Y by [date]. Include a confidence level (low/medium/high) for each Key Result. Avoid vanity metrics. Only focus on outcomes over outputs. Do not create more than 3 Objectives, as focus is critical. Each Initiative should have a clear owner. Keep the tone strategic and action-oriented.

Why this prompt works

The 'verb + metric + from X to Y by [date]' formula on every Key Result is what holds the output up. Without it, models produce KRs that look measurable but aren't ('improve customer satisfaction', 'grow brand awareness'). The formula forces a baseline number, a target, and a deadline, which together make it possible to actually evaluate the quarter at the end of it. The 'no more than 3 Objectives' rule reflects the actual OKR discipline: more than three and the team is doing roadmap-by-list, not strategy. The 'outcomes over outputs' instruction is also doing real work, especially against the model's default tendency to write KRs that are really just project completion ('ship X feature') rather than measurable change.

When to reach for it

You're a new team lead being asked to set OKRs for the first time and want a structured starting set, not a blank doc.
You're running a Q-planning workshop and need a draft set of OKRs to present to the team to react to and refine.
Your existing OKRs feel vague when you read them back, and you want a benchmark for what tighter ones look like.

How to customise it

The team mission and company priorities fields are the load-bearing inputs. If you write 'help customers succeed', the OKRs will be generic; 'reduce time-to-first-value from 14 days to 5 days' produces KRs that reason about the right metrics. Set company size honestly: a 12-person startup and a 1,200-person company need different OKR shapes, and the model will adjust scope accordingly. For early-stage teams, ask for two Objectives instead of three; three Os spreads attention too thin when the team has fewer than 8 people.

What good output looks like

A hierarchical outline with three Objectives, three to four KRs each, two to three Initiatives per KR. Each KR has a confidence rating. Each Initiative has an owner field, often left as 'TBD' for you to fill in. Total length 600 to 1,000 words. The KRs follow the formula tightly; the Initiatives are usually the section needing the most editing because they reflect implementation choices the model can't make for you.

Watch out for

The model sometimes generates KRs that are really output milestones ('launch the new dashboard') rather than outcome metrics ('reduce dashboard load time from 4s to under 1s'). If you see verbs like 'launch', 'ship', 'complete', 'deliver', or 'roll out' in the KR, send it back with 'rewrite this KR as an outcome a customer or analytic could verify'. The confidence levels (low/medium/high) are usually optimistic by default; calibrate against your team's actual track record.

OKRquarterly planningstrategyobjectiveskey resultsChatGPT / Claude