Convert the strategic goal below into one objective + three key results. Rules:
1. Objective: a measurable outcome stated as a state-of-the-world, not an activity. 'Power users feel the product gets meaningfully more useful over time' - not 'Improve power-user retention.'
2. Key results: exactly three. Each must:
- Be independently measurable (no compound KRs).
- Have a starting baseline and a target ('from X to Y'). If the baseline is unknown, write 'baseline TBD - need {{measurement_owner}} to pull'.
- Name the metric source explicitly: dashboard ID, query, survey instrument, or report. Without a named source, the KR is unverifiable.
3. End with a one-line note describing the mix of leading vs. lagging indicators - and why you picked that mix.
No activities as KRs ('Run 5 customer interviews' is a task, not a KR).
The strategic goal:
{{strategic_goal}}
OKR draft from a strategic goal
Add to PromptPaste
Download PromptPaste for MacDownload PromptPaste for iPhoneDownload PromptPaste for iPadDownload PromptPaste for Mac & iPhone
the prompt
Example output
Strategic goal input: 'We need to fix retention for power users this quarter.'
Objective: Power users feel the product gets meaningfully more useful the longer they use it.
Key result 1: Reduce 60-day churn rate among power users (>10 sessions/month) from 14% to 10%.
Metric source: Amplitude cohort dashboard 'Power user retention v3' (ID 4471). Measured at end of quarter.
Key result 2: 40% of power users have at least one personalized artifact (saved filter, custom shortcut, or imported pack) within their first 14 days.
Metric source: BigQuery custom event 'first_personalization' joined with user_cohort. Pulled weekly via the analytics pipeline.
Key result 3: Net Promoter Score among power users (single-question in-app survey, sampled 1/20 sessions) reaches +35 (current: +22).
Metric source: NPS survey responses logged in Mixpanel project 'PromptPaste-mobile'. Reported monthly.
Notes: Two of three KRs are leading indicators (personalization rate, NPS); one is the lagging outcome (churn). Picked deliberately so we can course-correct mid-quarter.
Common mistakes
Don't write a key result that's an activity ('Run 5 customer interviews this quarter'). Activities are not key results - they're tasks. The KR is the outcome the activity drives. Also: do not skip the metric source. 'Reduce churn' without a source is unactionable; the team will spend weeks debating which dashboard to look at. Third mistake: 5+ key results. Three is the cap. If you have 5, you don't have OKRs - you have a to-do list with metrics.
More from AI Prompts for Product Managers
PRD draft from a one-line problem
Act as a senior product manager. I'm going to give you a one-line problem statement. Before drafting any PRD, do this: 1. State the…
Customer interview synthesis
Read the raw customer interview transcripts below. Produce: 1. The top 5 themes ranked by frequency (number of interviews where the theme…
Stakeholder weekly update
Convert my raw bullets below into a weekly stakeholder update. Use exactly three sections: 1. Shipped: each item with a one-line outcome,…
Why it works
OKRs are the artifact PMs are most likely to write badly under deadline. The mistake is taking a strategic goal and listing 4-5 vague aspirations as key results. This prompt enforces the discipline: one objective stated as a measurable outcome (not an activity), three key results that are independently measurable, and a named metric source per KR (so you can't fake the measurement later). The 'metric source' line is the differentiator - 'Reduce churn by 5%' is hopeful; 'Reduce 30-day power-user churn by 5% (source: Amplitude cohort dashboard ID 4471)' is auditable. PMs who use this prompt produce OKRs their teams can actually hit because the success conditions are unambiguous. Tested cleanest on Claude Opus 4.7.