---
title: "OKR Examples by Team (Marketing, IT and More) + AI Template"
url: "https://goremy.ai/blog/articles/write-okrs-with-ai"
author: Luis Chavez-Mattos
editor: Luis Chavez-Mattos
editor_title: Director, Product
published: "2026-11-14T15:00:10.044Z"
updated: "2026-11-14T15:00:10.044Z"
topic: Strategy and Planning Templates
description: Copy-ready OKR examples for marketing, IT, customer success, product and more, plus a fill-in template and an AI prompt that drafts your OKRs.
---

# OKR Examples by Team (Marketing, IT and More) + AI Template

> Copy-ready OKR examples for marketing, IT, customer success, product and more, plus a fill-in template and an AI prompt that drafts your OKRs.

Edited by Luis Chavez-Mattos, Director, Product · Published 2026-11-14

## What are good OKR examples?

A good OKR has one Objective (a short, plain sentence describing where you want to be at the end of the quarter) and two to five Key Results (measurable outcomes that prove you got there). The objective should make people want to work on it. Each key result should have a number, a starting point and a deadline. Example: "Objective: Make onboarding painless for new customers. KR1: Cut median time to first value from 21 days to 10. KR2: Raise onboarding survey score from 3.6 to 4.2 out of 5." Below you will find a template, a prompt, and examples by team.

## TL;DR

- An OKR is **one inspiring objective plus two to five measurable key results**, set for a quarter or a year.
- Key results measure **outcomes (what changed), not activities (what you did)**. "Publish 12 blog posts" is a task. "Grow organic sign-ups from 400 to 650 a month" is a key result.
- AI is good at **drafting, tightening wording and spotting weak key results**. It cannot know your baseline numbers or what your company can realistically do.
- Always give the AI your **real baselines, constraints and company goals**, or it will invent plausible-sounding targets.
- Every example below uses placeholder numbers. **Replace them with your own baselines** before you commit to anything.
- Score OKRs weekly or biweekly, and write down what you are **deliberately not doing** this quarter.

## What is the OKR template to copy?

Paste this into a doc, a spreadsheet or your planning tool. Fill in one block per objective. Most teams need two to four objectives per quarter, and fewer is better.

```
OKR BLOCK

Quarter / period: [Q1 2026, for example]
Team: [team name]
Owner: [one named person, not a team]

OBJECTIVE
[One sentence. Qualitative, specific, something people care about.
Starts with a verb. No numbers in it.]

WHY THIS, WHY NOW
[One or two sentences. What company goal does it serve? What
happens if we ignore it?]

KEY RESULTS
KR1: [Verb] [metric] from [baseline] to [target] by [date]
     Data source: [where the number comes from]
     Confidence at start (0 to 10): [ ]
KR2: [Verb] [metric] from [baseline] to [target] by [date]
     Data source: [ ]
     Confidence at start (0 to 10): [ ]
KR3: [optional]

INITIATIVES (the work we think will move the KRs)
- [Project or task]
- [Project or task]

NOT DOING THIS QUARTER
- [Something reasonable we are choosing to leave out]

DEPENDENCIES AND RISKS
- [Team or system we need, and what could go wrong]

CHECK-IN CADENCE
[Weekly or biweekly. Who updates the numbers. Where.]

END-OF-QUARTER SCORE
KR1: [ ]%   KR2: [ ]%   KR3: [ ]%
What we learned: [ ]
```

Three rules make this template work:

1. **Every key result needs a baseline.** If you do not know where you are today, your first key result is to measure it, and you should say so.
2. **Initiatives are not key results.** "Launch the new help center" is an initiative. "Reduce tickets about account setup by 30%" is the result you want from it.
3. **One owner per OKR.** A shared owner usually means no owner.

## How do you write OKRs with AI?

AI works best as a drafting partner and an editor. You supply the facts. It supplies structure, wording and a sharp critique. Follow these steps.

1. **Gather your inputs.** Write down your company or department goals for the period, last quarter's results, your current baselines for the metrics you care about, and any hard constraints (headcount, budget, a launch date you cannot move).
2. **Paste the prompt below.** Fill in the brackets. Do not skip the baselines. This is the single biggest factor in whether the output is usable.
3. **Let the AI ask questions first.** The prompt tells it to ask what it is missing. Answer honestly.
4. **Ask for two or three alternative objectives.** Pick the one your team would be proud to hit, then ask for key results only on that one.
5. **Run the critique pass.** Ask the AI to rate each key result against the checklist further down and rewrite the weak ones.
6. **Edit by hand.** Change the wording to sound like your team. Check each number against its real source.
7. **Share it with the people who own the work** before you publish. An OKR written without them is a wish list.

### The prompt to paste

```
You are an experienced operations and strategy coach who helps teams
write OKRs (Objectives and Key Results).

Context
- My team: [team name and what it does]
- Company or department goals this period: [paste them]
- Period: [quarter or year]
- Last period's results: [paste, or say "none"]
- Current baselines I know: [metric: number, one per line]
- Constraints: [headcount, budget, fixed dates, tools]
- Things we are NOT able to change: [e.g., pricing, product roadmap]

Task
1. Before writing anything, ask me up to 5 questions about anything
   you need that I have not given you. Wait for my answers.
2. Then propose 3 candidate objectives. Each is one sentence, has no
   numbers in it, starts with a verb, and links to a company goal.
3. After I choose one, write 3 key results for it using this format:
   "[Verb] [metric] from [baseline] to [target] by [date]".
4. Rules:
   - Key results measure outcomes, not activities or deliverables.
   - Use only baselines I gave you. If a baseline is missing, write
     "BASELINE NEEDED" instead of inventing a number.
   - Mark each target as "committed" (we expect to hit it) or
     "stretch" (we expect to hit about 70%).
   - List the 3 to 5 initiatives that would likely drive the results.
   - List one thing we should explicitly NOT do this period.
5. Finish by critiquing your own key results: which one is easiest to
   game, which one depends on another team, and which one we cannot
   measure with the data I described.
```

### What to check in the answer

- **Every number.** If a baseline or target is not one you supplied or agreed, it is a guess. Remove it or verify it.
- **Outcome or activity?** If you can finish it by doing a task ("ship," "launch," "run"), it is probably an activity.
- **Can you measure it this quarter?** A metric that updates once a year cannot be tracked in a quarter.
- **Can you influence it?** If the result depends mostly on another team or on the market, either share the OKR or pick a different metric.
- **Could it be gamed?** "Reduce average ticket time" can be hit by closing tickets early. Pair it with a quality measure.

## How should you fill in the template? A worked example

Say you manage a customer support team of eight at a software company. The company goal this year is to improve retention. Here is a filled-in block.

```
Quarter: Q3
Team: Customer Support
Owner: Dana (Support Manager)

OBJECTIVE
Make getting help fast and painless for every customer.

WHY THIS, WHY NOW
Exit surveys last quarter named slow answers as a top reason for
cancelling. Retention is the company's main goal this year.

KEY RESULTS
KR1: Reduce median first response time from 9 hours to 3 hours by Sept 30
     Data source: help desk report
     Confidence: 7
KR2: Raise customer satisfaction on resolved tickets from 82% to 88% by Sept 30
     Data source: post-ticket survey
     Confidence: 6
KR3: Cut repeat contacts about the same issue within 7 days from 14% to 9%
     Data source: help desk report, tagged by issue
     Confidence: 5

INITIATIVES
- Write answers for the 20 most common questions and add them to the help center
- Set up routing so billing questions go straight to the billing specialist
- Weekly review of the 10 lowest-rated tickets

NOT DOING THIS QUARTER
- Launching phone support

DEPENDENCIES AND RISKS
- Needs product team to fix the confusing export screen (drives many tickets)
- Two open hires; if they slip, KR1 is at risk

CHECK-IN CADENCE
Biweekly. Dana updates the numbers every other Monday in the team doc.
```

Notice the pairing: KR1 pushes for speed, KR2 protects quality. The "not doing" line is what lets the team say no when someone proposes phone support in week four.

## What are good marketing OKR examples?

Marketing OKRs go wrong when they count output (posts, emails, campaigns). Aim at what the output is supposed to change: pipeline, sign-ups, search visibility, brand awareness among a defined audience. All numbers below are placeholders.

**Example 1: Demand generation**
- Objective: Fill the pipeline with buyers who fit our best customers.
- KR1: Increase marketing-sourced qualified leads from 300 to 450 per quarter.
- KR2: Raise lead-to-opportunity conversion from 12% to 16%.
- KR3: Lower cost per qualified lead from $180 to $140.

**Example 2: Content and search**
- Objective: Become the first place buyers look when researching our category.
- KR1: Grow organic search sessions from 20,000 to 30,000 a month.
- KR2: Move 10 priority keywords from page two to the first page.
- KR3: Grow newsletter subscribers from 5,000 to 7,000 with an open rate above 40%.

**Example 3: Product launch**
- Objective: Land the new product with the customers most likely to use it.
- KR1: Reach 500 sign-ups for the beta from existing customers by launch day.
- KR2: Get 25% of beta users to complete setup within 7 days.
- KR3: Secure 5 customer references willing to speak publicly.

Notice that none of these says "publish" or "run." The campaigns are initiatives underneath.

## What are good IT department OKR examples?

IT teams often hide behind uptime and ticket counts. Better OKRs tie IT work to what the business feels: speed, reliability, security and employee experience. Placeholders again.

**Example 1: Reliability**
- Objective: Keep the systems people depend on running so they stop thinking about them.
- KR1: Raise uptime of the top five internal systems from 99.5% to 99.9%.
- KR2: Cut the number of high-severity incidents from 9 to 4 per quarter.
- KR3: Reduce median time to restore service from 90 minutes to 45.

**Example 2: Security**
- Objective: Make the company a hard target without slowing people down.
- KR1: Raise multi-factor authentication coverage from 78% to 100% of employee accounts.
- KR2: Reduce the share of laptops more than 30 days behind on security updates from 18% to 5%.
- KR3: Lower the click rate on simulated phishing tests from 11% to 6%.

**Example 3: Employee experience**
- Objective: Make getting tech help fast and easy for every employee.
- KR1: Raise the IT satisfaction score from 3.8 to 4.4 out of 5.
- KR2: Resolve 40% of requests through self-service instead of tickets, up from 15%.
- KR3: Cut new-hire equipment setup time from 5 days to 2.

**Example 4: Cost and consolidation**
- Objective: Spend only on tools people actually use.
- KR1: Reduce unused software licenses from 22% to under 10% of total.
- KR2: Retire 8 overlapping tools.
- KR3: Hold total software spend flat while headcount grows.

## What do OKRs look like for other teams?

### Customer Success
- Objective: Help customers get lasting value, not just a successful onboarding.
- KR1: Raise net revenue retention from 98% to 104%.
- KR2: Increase the share of accounts using three or more core features from 35% to 50%.
- KR3: Cut time to first value from 21 days to 10.

### Product
- Objective: Ship the improvements customers keep asking for.
- KR1: Raise weekly active usage of the core workflow from 40% to 50% of accounts.
- KR2: Reduce the top three support-driving bugs by 60%.
- KR3: Move task completion rate in the redesigned setup flow from 61% to 75%.

### Sales
- Objective: Win more of the deals we should win.
- KR1: Raise win rate on qualified opportunities from 22% to 27%.
- KR2: Shorten average sales cycle from 74 days to 60.
- KR3: Grow average deal size from $18,000 to $21,000.

### HR and People
- Objective: Hire great people quickly and keep them engaged.
- KR1: Cut average time to fill open roles from 58 days to 42.
- KR2: Raise offer acceptance rate from 71% to 82%.
- KR3: Raise the "I see a future here" survey score from 3.7 to 4.1.

### Finance
- Objective: Give leaders numbers they can trust, sooner.
- KR1: Close the books in 6 working days instead of 10.
- KR2: Reduce forecast error on quarterly revenue from 9% to 5%.
- KR3: Cut manual journal entries by 40%.

### Executives and department heads
- Objective: Focus the whole company on a few things that matter this year.
- KR1: Hit the revenue target set in the annual plan.
- KR2: Raise customer retention from 88% to 91%.
- KR3: Cut the company-level priority list from 11 items to 4, with each one owned by a named leader.

## Where should you not trust AI with OKRs?

- **Baselines and targets.** AI does not know your numbers. Given nothing, it will produce numbers that look reasonable. Treat any figure you did not provide as fiction.
- **Ambition level.** Whether 5% growth or 50% growth is right depends on your resources, history and politics. That is your judgment.
- **Dependencies on other teams.** The AI cannot know that the data team is out for the quarter. You can.
- **Confidential data.** Check your company's AI policy before pasting revenue figures, customer names or unreleased plans into a public chatbot. Use an approved tool, or replace sensitive numbers with ratios and placeholders.
- **Alignment.** An OKR is also a conversation. If AI writes it and nobody on your team debates it, you lose the benefit.

Use AI for the second draft and the critique. Use people for the first conversation and the final call.

## How do you score and review OKRs during the quarter?

Update key results on a fixed schedule, weekly or every other week, in the same place each time. For each one, record the current number, a confidence score from 0 to 10, and one sentence on what is blocking it. A confidence score that drops two weeks in a row is your early warning.

At the end of the quarter, score each key result as a percentage of the way from baseline to target. Many teams treat committed targets as expected to hit fully and stretch targets as healthy at around 70%. Then write down what you learned. The next quarter's draft starts from that note, and you can paste it into the AI prompt under "Last period's results."

If a key result turns out to be wrong halfway through (the metric is broken, or the priority changed), say so and replace it openly. Quietly dropping it hides the lesson.

## Where do you track OKRs once they are written?

Most teams start in a spreadsheet and then lose track of who updated what. If you want something shaped to how your team works, you can describe a small OKR tracker to [Remy](https://goremy.ai) in plain English: objectives, key results with baseline and target, an owner for each, a weekly check-in form with a confidence score, and a dashboard showing progress by team. Remy builds it as a full-stack app with sign-in and role-based access, then deploys it to a live URL. You own the spec and the code, and you are not paying per seat for a planning tool you use once a week.

## Frequently Asked Questions

### How many OKRs should a team have?

Two to four objectives per quarter, each with two to five key results. Beyond that, nothing gets real attention. If everything is a priority, the OKRs become a to-do list.

### What is the difference between a KPI and a key result?

A KPI is a number you monitor all the time to keep the business healthy, such as monthly churn. A key result is a number you are deliberately trying to move this quarter. A KPI can become a key result when you decide to improve it, but you keep tracking many KPIs that never become OKRs.

### Should OKRs be tied to performance reviews or bonuses?

Most OKR guidance advises against linking them directly. If missing a target costs people money, they set safe targets and hide risk. Use OKRs to focus the team and learn, and judge performance on the broader picture of results, behavior and context.

### How ambitious should my targets be?

Split them into committed and stretch. Committed targets are ones you expect to hit. Stretch targets should feel uncomfortable, where reaching about 70% still counts as a good result. Base both on your history and your real capacity, not on what looks impressive in a slide.

### Can AI write my whole set of OKRs?

It can produce a solid draft in minutes, but it cannot know your baselines, your politics or your capacity. Give it real numbers, make it ask questions first, and edit its output with your team. The draft is the easy part. Agreeing on what matters is the work.
