In open beta — $100/month flat for your whole team See pricing →
OKR template

Product OKR examples

This is a free product OKR template with 2 objectives, 6 key results, and 7 starter initiatives you can copy. Activation and habit — whether new users reach value, and whether teams come back without being chased. It is written for Seed, Series A and Growth companies.

  • 2 objectives
  • 6 key results
  • Seed
  • Series A
  • Growth

What does a product OKR look like?

Copy these as they are and edit the numbers to your own baselines. The objective is the outcome you want to be true by the end of the quarter; the key results are how you will know it happened; the initiatives are the bets you are making to get there.

Objective 1 New business

Turn first-time users into people who come back on their own

Acquisition is wasted if new signups never reach the moment the product pays off. The annual goal is a product that sells itself; this quarter is the first honest step toward it.

KR 1.1 Headline

Reach first value within 24 hours: 31% → 55% of the signups from that week

How it is measured: Share of each week's signups that complete the first real workflow within a day

Baseline: 31% · Target: 55%

Initiatives

  • Watch 8 session recordings of signups who stalled and fix the first wall they hit
  • Cut the setup steps required before the first useful screen from seven to three
KR 1.2

Week-4 return rate 22% → 35% of the accounts created that month

How it is measured: Accounts active in week four, over accounts created that month

Baseline: 22% · Target: 35%

Initiatives

  • Send a day-3 nudge tied to what the account has not done yet
KR 1.3

Median time from signup to first shared report 3 days → 20 minutes

How it is measured: Median minutes between account creation and the first report shared with a teammate

Baseline: 3 days · Target: 20 minutes

Initiatives

  • Seed every new workspace with a sample report built from their own first import
Objective 2 Expansion

Make the core workflow something teams rely on every week

Retention inside existing accounts is what compounds. Depth of use beats breadth of features, and it is the metric our annual expansion plan rests on.

KR 2.1 Headline

Use the core workflow in 3 of any 4 weeks: 18% → 40% of paying accounts

How it is measured: Paying accounts with the core workflow used in three of any four consecutive weeks

Baseline: 18% · Target: 40%

Initiatives

  • Interview 6 accounts that use it weekly and find the trigger the others are missing
KR 2.2

Weekly active teammates per paying account 1.4 → 2.6

How it is measured: Distinct people active in a week, averaged per paying account

Baseline: 1.4 · Target: 2.6

Initiatives

  • Make sharing the default ending of the core workflow instead of an extra step
KR 2.3

Support tickets about the core workflow 120 → 45 per month

How it is measured: Tickets tagged to the core workflow per month

Baseline: 120 · Target: 45

Initiatives

  • Group last quarter's tickets into themes and fix the top two in product

Why are these key results written this way?

Every example above passes the same quality rubric Hespia grades real OKRs against. Four rules do most of the work, and they are worth keeping when you edit the numbers:

  1. The objective has no number in it

    An objective is a qualitative state of the world you want to be true. The number belongs one level down, on the key result. An objective with a metric in the title is really a key result that lost its parent.

  2. Every key result shows a baseline, not just a target

    "Reach first value within 24 hours: 31% → 55% of the signups from that week" is readable at a glance because the movement is visible. A target with no starting number cannot be paced weekly, so nobody can tell in week 4 whether it is slipping.

  3. Every ratio names a denominator the team cannot shrink

    "Of the accounts that started the quarter" is a fixed denominator. "Of active accounts" is not — the definition of active can move, and the percentage improves without anything real changing.

  4. Enabling work sits in initiatives, not in key results

    "Launch the new onboarding" is work; "activation in week one from 31% to 45%" is the result the work is meant to produce. Shipping the project is not the same as the outcome arriving, so the two live at different levels.

A template remembers. It doesn't chase.

Copied into a doc, these 6 key results depend on someone reopening the doc every week. Hespia seeds this exact board in one click, then reads pace on every key result weekly, flags what is slipping in week 4 instead of week 13, and writes the digest nobody wants to write. $100/month flat, whole team included.

Get started

Product OKR questions

What are good product OKRs?

Good product OKRs pair a qualitative objective with key results that each carry a number. In this template the objectives are "Turn first-time users into people who come back on their own" and "Make the core workflow something teams rely on every week", and every key result underneath states the metric, where it starts, and where it needs to land — for example "Reach first value within 24 hours: 31% → 55% of the signups from that week". If a key result has no starting number, it is a task rather than a key result.

How many key results should a product team have?

Three to five key results per objective, and no more than two or three objectives per team in a quarter. This template uses 2 objectives and 6 key results in total, which is a realistic quarter for one team. More than that and the weekly check-in stops fitting in fifteen minutes, which is how the ritual dies.

Are these product OKR examples free to use?

Yes. Every objective, key result, and initiative on this page is free to copy into any doc, spreadsheet, or goal tool, with no signup and no email. Hespia, the AI mentor that tracks weekly pace on each of these key results and chases the owners, is $100/month flat for the whole team.

Why does every key result here name its denominator?

Because a ratio without a stated denominator can be improved by shrinking the bottom number instead of growing the top one. A team that reports "percentage of active accounts" can quietly redefine "active" and post a win it did not earn. Every percentage in this template names a denominator the team cannot move, such as the accounts that started the quarter.

More OKR templates

Product monetization OKR examples

The product doing its own selling: trials that convert without a call, and usage that opens the upgrade conversation for you.

Company and founder OKR examples

The two goals a founder-led company runs on: win the segment you chose, and make the business predictable enough to plan a year around.

Engineering OKR examples

Delivery and reliability as outcomes, not story points: how fast a change reaches customers, and how rarely it hurts them.

Engineering quality and tech debt OKR examples

Bugs found before customers find them, and the accumulated debt that taxes every change — paid down where it slows you most.

← All OKR templates