Write Quarterly OKRs for a Team
Generate outcome-focused quarterly OKRs with confidence scores and risk notes.
This prompt acts as an OKR coach to produce a full quarter's worth of objectives and key results tailored to a specific team, company stage, and focus area. It deliberately steers toward outcome-based key results (impact you want) over output-based ones (work you'll do), which is the most common failure mode in real OKR setting. The added confidence score and per-objective risk note turn a static goal list into something you can actually pressure-test in a planning meeting.
You are an OKR coach. Write a set of quarterly OKRs for a [TEAM TYPE] team at a [COMPANY STAGE] company focused on [FOCUS AREA]. Provide 2-3 Objectives, each with 3-4 Key Results. Key Results must be: specific, measurable, time-bound, and ambitious but attainable. Avoid output-based KRs — focus on outcomes. Add a 'confidence score' (1-10) and a note on the biggest risk for each objective. CONTEXT: [DESCRIBE TEAM AND GOALS]
What you can expect back
Objective 1: Make new customers successful fast enough that they stay. - KR1: Reduce time-to-first-value from 21 to 7 days for new accounts. - KR2: Lift 90-day activation rate from 55% to 75%. - KR3: Achieve 90% onboarding-completion among accounts signed this quarter. Confidence: 6/10 Biggest risk: Without a defined onboarding flow yet, KRs depend on shipping it in month one. Objective 2: Catch at-risk accounts before they churn. - KR1: Cut monthly logo churn from 6% to 4%. - KR2: Achieve 80% health-score coverage across the active book. - KR3: Recover 30% of accounts flagged 'red' via intervention. Confidence: 5/10 Biggest risk: Health-score accuracy is unproven; early signals may misfire.
Illustrative example — your results will vary by tool and inputs.
Get sharper results
- 01Give real baseline numbers in the context block, because a KR like 'reduce churn from 6% to 4%' is far more useful than the model inventing a starting point.
- 02Push back on any KR that describes activity ('run 10 webinars') and ask the model to restate it as the outcome that activity should drive.
- 03Use the confidence scores to calibrate ambition: if everything is 8+, the OKRs are probably too safe; if everything is 3, they're likely unrealistic.
- 04Ask the model to identify dependencies between objectives so you can sequence work instead of treating them as parallel.
- 05Limit yourself to 2 objectives if the team is small; more than that usually means nothing gets the focus to actually move.
Adapt it for your case
Set the team type to 'executive/company' and ask for cross-functional objectives that each department's OKRs should ladder up to.
Reframe for one person's quarter and ask for KRs scoped to what a single contributor can directly influence.
Paste your existing OKRs with current progress and ask the coach to grade each KR and recommend what to drop or double down on.
Common questions
What's the difference between outcome and output KRs?
Output KRs measure work done ('publish 12 case studies'); outcome KRs measure the result that work should cause ('increase trial-to-paid conversion to 25%'). This prompt favors outcomes.
How many objectives should I actually keep?
Two to three is the prompt's range, but most teams execute best with two. Fewer, sharper objectives beat a long list nobody can prioritize.
Are the confidence scores meaningful?
They're the model's estimate, not a measurement. Use them as a conversation starter in planning to debate whether each objective is appropriately ambitious.
You may also need
Draft OKRs That Cascade From Company Goal to Team
Drafts outcome-based OKRs that ladder up to the company goal and weeds out tasks masquerading as key results.
Vendor and Tool Comparison With a Weighted Scorecard
Screens tools against must-haves then ranks survivors on a weighted scorecard with a clear pick.
Business Case for a Project With ROI and Payback
Frames a project as an investment with quantified benefits, a transparent ROI and payback calculation.
Summarize Meeting Notes Into Action Items
Turn messy meeting notes into a clean summary with decisions, owners, and follow-ups.