Draft OKRs From a Team Mission Statement
Translates a team mission statement into 2-3 objectives and 3-4 key results each. Built for PMs and team leads starting a new quarter and needing a first draft to iterate on.
When to use this prompt
Use this at the start of a quarter when you need to draft OKRs for your team but the mission statement has not yet been turned into concrete goals. You will need the mission statement, any company-level OKRs you need to ladder up to, and a sense of your team's capacity. The prompt produces a first draft, not a final version; expect to iterate with your team over 2-3 rounds. It is deliberately strict about key result quality because vague KRs are the single most common OKR failure mode. If the mission is itself vague, the prompt will ask for clarification rather than guess.
The Prompt
You are a product manager drafting OKRs for the next quarter from a team mission statement. The output must follow the John Doerr framework: 2-3 qualitative objectives, each with 3 measurable key results. Team mission: {{team_mission}} Company OKRs this quarter: {{company_okrs}} Team capacity: {{team_capacity}} Strategic priorities: {{priorities}} Produce the OKRs in this structure: 1. OBJECTIVE 1 (qualitative, aspirational, memorable) - Why this matters (2 sentences connecting to the mission) - KR 1.1: [metric] from [baseline] to [target] by [date] - KR 1.2: [metric] from [baseline] to [target] by [date] - KR 1.3: [metric] from [baseline] to [target] by [date] 2. OBJECTIVE 2 â same structure. 3. OBJECTIVE 3 (optional, only if needed) â same structure. KR quality rules: - Every KR must be numeric with a baseline, target, and deadline. - KRs must be outcomes, not activities. "Launch feature X" is an activity; "50 percent of users adopt feature X" is an outcome. - At least 50 percent of KRs should be "stretch" (probability of hitting roughly 60-70 percent). Playing it safe defeats the purpose. - No more than 9 KRs total across all objectives. If you need more, your team is too unfocused. After the OKRs, produce: LADDER-UP CHECK â For each objective, explain how it connects to one of the company OKRs. If any objective does not ladder up, flag it. RISK WATCH â Name the 1-2 OKRs most likely to miss and the reason. Proactively identifying miss risk is more valuable than celebrating commitments. If the mission is too vague to produce clear objectives, ask one specific clarifying question instead of guessing.
Example Output
Mission: Make billing admins confident in every number they see. OBJECTIVE 1: Make the invoices dashboard the trusted source of truth for overdue status. Why: Currently admins build personal spreadsheets because they do not trust our numbers. This wastes 20 minutes daily and erodes trust. - KR 1.1: Reduce spreadsheet-export events by billing admins from 1200/week to under 400/week by end of quarter. - KR 1.2: Increase NPS for billing admins from 32 to 50. - KR 1.3: Cut median days-to-collection from 18 to 12 in active accounts. OBJECTIVE 2: Ship the bulk invite flow that mid-market customers have been asking for. Why: Our current single-invite flow is the top-cited blocker in lost deals above 100 seats. - KR 2.1: Launch bulk invite CSV import to general availability by sprint 14. - KR 2.2: Reach 75 percent bulk adoption among accounts with 20+ users. - KR 2.3: Close 5 deals that previously stalled on invite friction. LADDER-UP CHECK - Objective 1 ladders to company OKR "Improve gross retention by 3 points." - Objective 2 ladders to company OKR "Win 15 new mid-market logos." RISK WATCH - KR 1.1 depends on a behavioral change that may lag the feature launch. If admins cling to spreadsheets out of habit, we may hit 600/week instead of 400. - KR 2.3 depends on sales team follow-up with stalled deals, which is outside the product team's control.
Recommended Tools
Notion projects and Coda both render OKR tables with inline baselines, targets, and progress tracking so the quarterly review is streamlined. Airtable is the right choice when your org runs a central OKR database across multiple teams and needs cross-team visibility. Use Notion or Coda for team-level OKRs and Airtable when OKRs are a company-wide ritual.
Frequently Asked Questions
When should I use this prompt?
Use it at the start of a quarter, 2-3 weeks before the official OKR commit date, to generate a first draft you will iterate on with your team. Do not use the output as-is; OKRs must be owned by the team, not the PM. Run the draft through a team workshop to refine. Also do not use it if your company does not actually use OKRs as a planning tool; writing OKRs that no one reads is worse than not writing them at all. Use the 8 core filters first to decide whether OKRs are the right format for your team's planning rhythm.
What if my team has no baselines for the KRs?
Two options. First, spend the first 2 weeks of the quarter gathering baselines via analytics work, then commit to targets. This is the honest path but delays your OKR commit. Second, set the quarter's first KR as 'establish baseline and commit to a target by week 3.' This is a legitimate KR for a team that has not instrumented its work before. Never set targets without baselines; you will either sandbag or overcommit, and either way you will not learn anything from the outcome.