Turn a goal into quarterly OKRs
FreeA fill-in-the-blank ChatGPT prompt to write OKRs: it turns one goal into focused quarterly objectives with measurable baseline-to-target key results and the initiatives to hit them.
Get a ready-to-run set of quarterly OKRs from a single goal: 1-3 qualitative objectives, each with measurable key results and their initiatives kept separate.
Your details
saved for every promptThis prompt
You are an OKR coach who has helped founders and team leads turn fuzzy goals into sharp, measurable quarterly OKRs.
Your task: turn the single goal below into a focused set of quarterly OKRs for {{company}} — {{objective_count}} qualitative Objective(s), each with 2-4 quantitative Key Results written as "metric from baseline to target by end of quarter," plus the initiatives that will move them. You've done this well when every Key Result is an outcome with a number, a baseline, and a date, and no Objective reads like a to-do list.
Context:
- Organization: {{company}} ({{industry}})
- Who owns these OKRs: {{team}}
- Quarter: {{quarter}}
Goal to translate:
"""
{{goal}}
"""
Current baseline (metrics and starting point to anchor targets to):
"""
{{baseline_metrics}}
"""
Steps:
1. Restate the goal in one sentence and name the single most important outcome it implies.
2. Write the Objective(s): qualitative, memorable, and directional — the inspiring "what we're going after." Keep each to one sentence and keep metrics out of it.
3. For each Objective, write 2-4 Key Results. Each Key Result moves one metric from its baseline to a target by the end of {{quarter}}. Favor leading indicators you can check weekly, and give each Key Result a single owner role.
4. List the Initiatives separately from the Key Results: the projects and bets you'll actually run to move each Key Result. These are the activities ("ship X," "launch Y," "hire Z"), not the results.
5. Mark each Key Result as Committed (you expect to fully hit it) or Stretch (~70% confidence), so the team knows what a win looks like.
6. Do a quality pass: flag any Key Result that's really a task, any Objective that smuggles in a metric, and any Key Result missing a baseline — then fix them.
7. Add the primary risk for each Objective and a short "not doing this quarter" list of what you're deliberately parking.
If a baseline number isn't in the context above, say so and propose how to measure it this quarter — an early "establish the baseline by week 2" Key Result is valid. Don't invent a number; if you assume one, label it an assumption.
Output format:
- One-line restatement of the goal.
- For each Objective, numbered:
- The Objective statement (one sentence).
- A table of Key Results with columns: Metric | Baseline | Target | Owner | Committed/Stretch.
- Initiatives — a short bulleted list.
- Primary risk — one line, with a mitigation.
- Scoring & cadence: how to grade each Key Result 0.0-1.0 at quarter end, and the weekly check-in rhythm.
- Not doing this quarter: a short bulleted list.
Constraints:
- Objectives are qualitative; Key Results are quantitative. Never put a raw number in an Objective, and never leave a Key Result without one.
- Every Key Result names both a baseline and a target — even if the baseline is "unknown, establish by week 2."
- Key Results measure outcomes. "Ship," "launch," "hire," and "build" belong in Initiatives, not Key Results.
- Keep it to at most {{objective_count}} Objectives and 4 Key Results each — focus beats coverage.
- Base every target on the baseline and context given; label anything you assume.10 fields still empty — the {{like_this}} slots fill in as you type.
See it in action
What this prompt produces with example details filled in:
**Goal, restated:** In Q3 2026, Northwind Analytics wants finance teams to reach for it first — measured by whether more of them activate, stay, and recommend it. **Objective 1 — Turn new finance-team signups into activated, sticky accounts.** | Metric | Baseline | Target | Owner | Type | |---|---|---|---|---| | Activated new accounts / month (first shared report in ≤7 days) | 38 | 70 | Head of Product | Stretch | | Monthly logo churn | 4.1% | 3.0% | Head of CS | Committed | | % of new accounts with ≥3 seats active by day 30 | unknown — establish by week 2 | 50% | Head of Product | Stretch | Initiatives (the work, not the result): - Rebuild onboarding around a "first shared report in 10 minutes" path - Ship finance-specific templates (board pack, cash flow, budget-vs-actual) - Launch a 30-day activation checklist (in-app + email) Primary risk: the onboarding rebuild slips — mitigate by shipping the template library first, since it moves activation independently of the flow rebuild. **Objective 2 — Make finance teams want to recommend us to their peers.** | Metric | Baseline | Target | Owner | Type | |---|---|---|---|---| | NPS among finance-team admins | 22 | 40 | VP Marketing | Stretch | | Published named case studies | 3 | 8 | VP Marketing | Committed | | % of new accounts sourced from referral / word-of-mouth | unknown — instrument by week 3 | 20% | VP Marketing | Stretch | Initiatives: - Stand up a "refer a peer" flow with a two-sided incentive - Interview 15 power users; publish 5 named case studies - Close the top 10 detractor complaints from Q2 support tickets Primary risk: referral attribution isn't instrumented in time — treat "instrument referral tracking" as the week-3 gating task before the target counts. **Scoring & cadence:** At quarter end, grade each Key Result 0.0-1.0 (actual movement ÷ targeted movement from baseline). A 0.7 on a Stretch KR is a win; a wall of 1.0s means next quarter's targets were too soft. Check in every Friday — update each KR's current number and a green/yellow/red confidence flag. If a KR is red two weeks running, fix the initiative or re-scope the target now, don't wait for quarter end. **Not doing this quarter (so the above can win):** enterprise SSO, a second pricing tier, and net-new integrations — all parked until activation and retention move.
Tips
- Feed it real baseline numbers (current MRR, churn, signups). Key results are only as sharp as the baseline they move from — without one, the model guesses at targets.
- Run one goal per pass. OKRs work through focus; if you have three goals, generate each separately, then cut the whole set down to three objectives total.
- After the draft, ask it to "challenge every Key Result: is this an outcome or a task?" to catch initiatives disguised as key results.
- Label each KR Committed (must-hit) vs Stretch (~70% confidence) so the team knows what actually counts as a win at quarter end.
Built by Web Innoventix
Want the work done, not just prompted? We design, build and rank websites that get found on Google and cited by AI.
Get a free quoteMore prompts
Browse all →Pressure-test your business idea before you build
Stress-test any business idea across demand, moat, unit economics, its riskiest assumption, and the cheapest test to run this week — and get an honest build/refine/kill verdict, not a pep talk.
Nail your positioning statement and value proposition
A paste-and-go ChatGPT prompt that interviews you, then writes a specific, differentiated positioning statement and value proposition your best-fit buyer instantly recognizes as built for them.
Design a pricing page: tiers, plan names, and anchoring
A ChatGPT prompt for a pricing page that interviews you about your product, then designs the whole thing — the value metric, three to four named and charm-priced tiers, the "most popular" anchoring, CTA copy, and what to test first.
Write a one-page executive summary from a long report
The prompt to write an executive summary from a long report: it produces a one-page brief with the bottom line up front, the numbers that matter, and prioritized next steps for your specific reader.
Turn messy meeting notes into decisions and action items
Paste raw, disorganized meeting notes and get back a decision-ready record where every decision is stated plainly and every action item has an owner and a due date.
Turn a feature idea into a developer-ready PRD
A ChatGPT prompt that writes a PRD: it interviews you about your feature idea one question at a time, then produces a developer-ready product requirements document with user stories, testable requirements, and success metrics.

