Prompt Notebook

OKRs · Goal setting · Templates

OKR examples for small teams, and how to write your own

By T. Krause

OKRs give a small team two or three goals for the quarter and a number to measure each one. Here are OKR examples for four kinds of small team, how to tell a key result from a task, how many to set, how to score them and a full quarter for an invented six-person shop.

OKRs, short for objectives and key results, are a way to set a few goals for a quarter and measure how far you got. The objective says in plain words what you want to change. Each key result is a number with a start value and a target, so at the end of the quarter you can score it. A small team usually needs two or three objectives with two to four key results each, updated once a week and scored when the quarter ends.

Below are OKR examples for four kinds of small team. After them, the guide covers how to write each part, how many to set and how to score them, then follows one quarter at an invented online shop from the first draft to the final scores. If you want a page with the columns already set up, copy our free OKR template.

OKR examples for small teams

These teams and numbers are invented to show the shape. Each objective has two or three key results, and every key result has a start value and a target.

A three-person marketing team

Objective: More of the right people find us without paid ads.

  • Organic visits to the pricing page from 1,200 to 2,000 a month
  • Newsletter sign-ups from 150 to 300 a month
  • Trial sign-ups from organic search from 40 to 70 a month

A two-person customer support team

Objective: Customers get an answer the same day they write.

  • Median first reply time from 9 hours to 3 hours
  • Tickets closed by a help article, with no reply needed, from 10% to 25%

A five-person product and engineering team

Objective: New users finish their first project without asking for help.

  • New accounts that finish a project in their first week from 22% to 35%
  • Support tickets from users in their first week from 80 to 40 a month
  • Crash-free sessions from 98.5% to 99.5%

A four-person design agency

Objective: Every project we take on makes money.

  • Projects finished within budget from 5 in 10 to 8 in 10
  • Days from final invoice to payment from 45 to 25 on average
  • Billable hours from 60% to 70% of hours worked

What an objective is

An objective is the goal in words. It is short, it belongs to this quarter, and the team would be glad to have reached it. "Customers get an answer the same day they write" is an objective. "Improve support" is too vague to tell when you've arrived, and "Hire a third support person" is a task. Anyone in the company should understand the objective without reading the key results under it.

Google's re:Work guide, Set goals with OKRs, says "Objectives are ambitious and may feel somewhat uncomfortable." Aim for something the team won't reach by carrying on as it is.

What a key result is

A key result tells you whether the objective happened. It is a number with a start value, a target and, during the quarter, a current value. "Median first reply time from 9 hours to 3 hours" says where you began and where you want to end up, and each week the current value shows how far along you are. The same guide says key results "should describe outcomes, not activities."

How to tell a key result from a task

Ask one question. If you finished it and nothing else changed, would the objective be any closer? "Write 20 help articles" can be finished while the inbox stays as full as before, so it's a task. "Tickets closed by a help article from 10% to 25%" only moves if the articles work. That's a key result, and the 20 articles are one way to reach it.

The wording gives tasks away too. The re:Work guide puts it this way: "If the KRs include words like 'consult,' 'help,' 'analyze,' 'participate,' they're describing activities." Write, launch, build and run usually point the same way.

Keep the tasks, but file each one under the key result it serves. Then everything the team is doing stays tied to a number it is meant to move.

A few key results are a plain yes or no, such as a launch that has to happen by a date. Use those sparingly. Where you can, measure what the launch is supposed to change.

How many OKRs to set

The re:Work guide recommends three to five objectives with around three key results each, and warns that "more can lead to over-extended teams and a diffusion of effort." For a team of under ten people, two or three objectives with two to four key results each is enough. You should be able to read the whole set in a minute and go through it in one short weekly meeting.

If you have more candidates than that, choose the ones that matter most this quarter. The rest go on a list for next quarter.

Give every key result one owner: the person who updates the number each week and speaks up when it slips. Other people can do the work, but one name answers for the number.

How to write OKRs in five steps

1. Start from what needs to change

List the problems that cost the team most right now, with the numbers you already have: the support inbox, sales, refunds, delivery times. Each of the biggest problems is a candidate objective.

2. Write the objective as a sentence

Describe the state you want to reach. "Orders go out the same day, complete" says more than "Shipping improvements", because you can picture it and check it.

3. Measure the start before you set the target

Find the current value of every key result before the quarter begins. A target without a start value can't be scored, and a start value you guessed makes every score a guess too.

4. Set targets that stretch

Pick a target that would make this an excellent quarter if you hit it in full. If you're sure you'll reach it, it's too low. The section on scoring explains why a 0.7 can be a good result.

5. Name the owners and fix the check-in

Put one name on each key result and agree a day each week when owners update the current values. Then share the set with everyone it affects.

How to score OKRs

At the end of the quarter, score each key result from 0 to 1 by how much of the distance from start to target you covered:

score = (final value - start) / (target - start)

The formula works for numbers that should go down as well. Help emails from 140 to 70 a month, ending at 91, scores (91 - 140) / (70 - 140), which is -49 / -70, or 0.7. If you beat the target, record 1.0. If the number moved the wrong way, record 0.

The objective's score is the average of its key results. In the guide's words, "Each individual key result is graded and then, using a rough average, correspondingly the objective is graded." During the quarter, the same formula with the current value gives you the progress so far.

What counts as a good score? Google usually grades on a scale of 0.0 to 1.0, and its guide says "The sweet spot for OKRs is somewhere in the 60-70% range." A lower score may mean the team isn't achieving what it could. A higher one may mean the targets aren't set high enough, and the guide adds that someone who consistently hits every objective in full should "think bigger." So a team that averages 0.65 on stretch targets has had a good quarter.

A full example: one quarter at Thimbleway

The company, the people, the dates and the numbers below are invented. Thimbleway is a six-person online shop that sells sewing patterns as PDFs and fabric kits by post. Mara Quinn founded it and runs the OKRs. Noor Haddad answers customers, Elena Russo designs the patterns, Jonas Becker packs and ships the kits, Sam Okafor builds the website part-time and Felix Ward does marketing. The quarter ran from Wednesday 1 July to Wednesday 30 September 2026. Monthly figures count the last 30 days.

The OKRs they set

At the end of June the team agreed three objectives and two key results for each, with start values measured that month. Each key result has one owner, and Felix owns two.

Key resultObjectiveOwnerStartTarget
Pattern help emails down to 70 a monthCustomers finish the patterns they buyNoor140 a month70 a month
Pattern refund requests down to 10 a monthCustomers finish the patterns they buyElena30 a month10 a month
90% of orders ship the same dayOrders go out the same day, completeJonas60%90%
Wrong-item complaints down to 5 a monthOrders go out the same day, completeSam25 a month5 a month
Repeat customers place 26% of ordersPeople come back for a second patternFelix18%26%
6,000 newsletter subscribersPeople come back for a second patternFelix4,0006,000

The tasks sit inside each key result's page. Noor's page lists video walkthroughs for the ten best-selling patterns. Jonas's lists a 2 pm order cut-off and pre-packed kits for the top ten sellers. Sam's lists a barcode scan at the packing table. Felix's repeat-customer page lists an email offering a second pattern 14 days after a first order.

The check-in on Monday 10 August, week 6 of 13

Key resultProgressConfidenceCurrent
Pattern help emails down to 70 a month31%On track118 a month
Pattern refund requests down to 10 a month15%At risk27 a month
90% of orders ship the same day50%On track75%
Wrong-item complaints down to 5 a month55%On track14 a month
Repeat customers place 26% of orders0%Off track18%
6,000 newsletter subscribers25%On track4,500

Help emails are only 31% of the way there, but Noor kept them on track because the first videos went live that week and the rest were recorded. Confidence is a forecast, so a slow start with the fix in place can still be on track.

Elena opened the refund key result and wrote two short sections inside it:

Why at risk. Most refund requests say the finished piece didn't fit. The size charts on the five best-selling patterns give body measurements, and buyers read them as the measurements of the finished garment.

What we're doing. Elena adds finished-garment measurements to those five charts by Friday 21 August. Until then, Noor answers every fit complaint with the corrected measurements before offering a refund.

Felix marked repeat customers off track because the second-pattern email went out for the first time in week 5, a month later than planned. By the end of August he will know whether the email brings people back.

The scores on Wednesday 30 September

Key resultStartTargetFinalScore
Pattern help emails down to 70 a month14070910.7
Pattern refund requests down to 10 a month3010200.5
90% of orders ship the same day60%90%84%0.8
Wrong-item complaints down to 5 a month25590.8
Repeat customers place 26% of orders18%26%22%0.5
6,000 newsletter subscribers4,0006,0005,2000.6

The objectives score 0.6 for "Customers finish the patterns they buy", 0.8 for "Orders go out the same day, complete" and 0.55 for "People come back for a second pattern". The average across all six key results is 0.65.

Why this example works

Every key result has a start value measured before the quarter, so anyone can check the final scores with the formula. None of the key results is a task. The videos, the size charts and the barcode scan all sit inside the key results they were meant to move, so when every video was live and help emails still ended at 91 instead of 70, the score said so. The at-risk note gives a cause and a date. And the scores tell the team where to aim next quarter: the two 0.8s say the shipping targets could have been higher, and the two 0.5s say what to look at first.

Common mistakes

A to-do list with numbers on it. "Publish 12 blog posts" is countable, but it's still a task. Ask what the posts are meant to change and measure that.

Too many objectives. Five objectives for a team of four means each one gets a fraction of the attention. Two or three is enough.

No start value. "Grow newsletter subscribers to 6,000" can't be scored if nobody wrote down the 4,000 you started from.

Set and forget. OKRs written in the first week and opened again in the last are a wish list. A weekly update of the current values takes a few minutes and catches problems in time.

Moving the target mid-quarter. If the target turns out wrong, leave it and write down why in the key result's page. Changing it hides what you learned.

Using the scores to grade people. Scores tied to bonuses lead to safe targets. The FAQ below has more.

Where OKRs meet the rest of your planning

A key result says what should change. The projects that change it need their own plan, and a project brief is a good place to name the key result a project is meant to move. While the project runs, the weekly status update can report that key result's current value under its numbers. At the end of the quarter, a retrospective on the scores is a good way to decide what to keep and what to change for the next set.

Writing OKRs in Prompt Notebook

Prompt Notebook is ours, so read this part with that in mind. The OKR template is a database called OKRs this quarter. Each row is one key result, with columns for Objective, Progress, Confidence, Owner, Start, Target and Current. Objective is a select, so you replace its options with your own two or three objectives. Progress is a percentage you fill in at each check-in, using the formula above. Confidence has three options: On track, At risk and Off track.

The first view is a board grouped by objective. A second board groups by confidence, so the at-risk and off-track key results sit together, and a table lists every key result sorted by progress, lowest first. Each key result is also a page you can write in, which is where the tasks and the at-risk notes go. In the sample, the billing tickets key result is marked At risk and has two headings inside it, Why at risk and What we're doing. The sample is a quarter for an invented invoicing app, so you can see a filled-in set before you replace it. When the quarter ends, save the page as a template and start the next quarter from the copy.

Frequently asked questions

How many OKRs should a small team have?

Two or three objectives, each with two to four key results. Google's re:Work guide suggests three to five objectives, but a team of under ten people has less time to spread across them. If the whole set doesn't fit on one screen, cut it.

What is the difference between OKRs and KPIs?

A KPI is a number you watch all the time, such as monthly revenue or the share of orders that ship the same day. A key result is a change to a number that you commit to for one quarter, with a start and a target. Key results often move a KPI. Thimbleway's same-day shipping rate is a KPI, and "from 60% to 90% this quarter" turned it into a key result.

How often should you check OKRs?

Update the current values once a week and score them at the end of the quarter. A weekly update shows a key result slipping while there is still time to change course. Write the objectives and key results for the next quarter before the current one ends, so the team doesn't start the quarter without them.

Should OKRs be tied to performance reviews?

Keep them apart. Google's re:Work guide says "OKRs are not synonymous with performance evaluation." If a low score can cost someone a bonus, people set targets they know they'll reach, and the stretch is gone.

Can a key result be a launch or a project?

Occasionally. A launch that must happen by a fixed date can be a yes or no key result, scored 0 or 1. More often a launch is a task, so ask what it should change and measure that. The launch then goes inside that key result's page as one of its tasks.

Try it on your own notes

Prompt Notebook is free, with unlimited pages. Type one sentence and the AI drafts the first version.

Cookies and storage

Prompt Notebook needs one cookie to keep you signed in. Accepting turns on Google Analytics and Google's reCAPTCHA spam check on the contact form, and declining keeps the form working. Nothing optional runs until you choose.

Read the privacy notice