Home/Blog/OKRs/How to Set a Key Result Baseline Before …
OKRs

How to Set a Key Result Baseline Before the Target

How to set a key result baseline: find today's value first, then set the target against it, and if you cannot find it, make finding it your first key result.

Cover of the FIKR Space guide: How to Set a Key Result Baseline Before the Target

To set a key result baseline, find the current value of the metric before you choose any target, write it down with the source it came from, and set the target against it. If you cannot find the current value, finding it becomes your first key result.

A target with no baseline looks like a goal but is not measurable, whatever the wording suggests. This article explains why, how to get the starting number, and what to do when nobody can produce it.

How to set a key result baseline: what it is and why it comes first

A baseline is the value of the thing you want to change at the moment you decide to change it. It is a plain fact about the present, recorded before the quarter begins.

It comes first because a target is a distance, and a distance needs two ends. The guide uses a simple case: reach five hundred weekly active users means something entirely different if you are at four hundred and fifty than if you are at fifty. In the first case the goal is almost already met. In the second it is a tenfold change of behaviour. The sentence is identical and the ambition is not.

A team that sets targets without knowing the starting point is guessing at ambition. It might be reaching for something it has already achieved, or promising something nobody could do, and it will not find out which until the end of the quarter, when it is too late to matter.

The same target at three different starting points

It helps to see how much work a baseline does. Take the guide's example target and look at it from three starting positions.

Starting valueWhat the target meansWhat the team would be doing
Four hundred and fiftyA small step from where you already arePossibly sandbagging, since the goal is nearly met
Somewhere in betweenA real stretch whose size you can judgeChoosing deliberately how ambitious to be
FiftyA very large change in behaviourPerhaps promising something the team cannot deliver

The middle row is illustrative, built from the guide's two figures. The point of the table is not the numbers. It is that the target alone gives you no way to choose between these readings.

Free guide, 32 pages: The OKR Playbook. Send me the guide.

Why a missing baseline wrecks the end of the quarter

Without a starting number nobody can tell whether the goal was ambitious or already met. That has a predictable consequence at the end of the cycle: the conversation turns into an argument about interpretation.

One person says the result is a triumph because it moved. Another says it was always going to move. A third remembers the number differently. Nobody is lying. There is simply nothing written down to settle it, and the score becomes a negotiation. This is how a baseline-free metric, one of the four bad patterns in the guide, turns an honest scoring session into a contest of memories. The mechanics of that session are in how to score OKRs.

Finding the number: five steps

Getting the baseline is usually less about analysis and more about agreement. The guide's checklist for writing key results supplies the questions, and they fall naturally into an order.

  1. Name the metric in words. State exactly what is being counted, so the thing you measure is the thing you meant.
  2. Agree the source. The measurement source should be agreed and accessible before the quarter starts, not found afterwards.
  3. Read today's value. Take the number from that source, and record when you took it.
  4. Check that two people agree. Two people should report the same number from the same data. If they do not, the definition is not yet tight enough.
  5. Write it next to the target. Every key result carries a baseline as well as a target, in the same line.

Step four is the one that saves arguments later. A baseline that only one person can reproduce is a belief, not a baseline.

When you do not have the number

Sometimes the honest answer is that nobody knows. The guide is direct about what to do: if you do not have the baseline, finding it is your first key result, and that is a perfectly legitimate goal.

It is also frequently the most valuable one a young company sets, because it reveals that nobody actually knew. That discovery is worth having early. A company that believes it understands a number it has never measured is making decisions on a story, and the first quarter of measurement replaces the story with a fact.

This changes how you read a quarter. A goal of establishing the number properly, with an agreed source and a definition two people reproduce, is a changed state: the company moves from not knowing to knowing. It passes the would-we-know test as well as any other. The tests themselves are set out in how to write key results.

Do not let the easy number choose for you

A related trap is picking the metric because a baseline already exists. The guide warns that teams who start from the metric, because one is available, reliably produce goals that are precise and pointless.

So hold the order. Decide the outcome first. Then choose the number that would demonstrate it. Only then ask whether you have a baseline for it. If you do not, you have found a first key result, not a reason to switch to a different metric that happens to have history.

FIKR OS, strategy meets execution: OKRs, roadmaps and kanbans in one system. See FIKR OS.

Where a baseline sits in the set

A baseline is not extra paperwork. It is one of the things that makes a key result what it is. Look at how it appears on the guide's checklists.

  • Every key result has a baseline, not only a target.
  • You know today's value for every metric, or finding it is itself a key result.
  • The measurement source is agreed and accessible before the quarter starts.
  • Two people would report the same number from the same data.

If any of those boxes cannot be ticked, the guide's rule is that it becomes your next task. That is a useful way to think about the baseline: it is not a hurdle in front of the work, it is the first piece of the work.

Why the baseline changes what a score means

The guide separates committed goals from aspirational ones, and a baseline is what lets you tell them apart in practice. A committed goal is one you expect to deliver in full. An aspirational goal is set beyond comfortable reach, and getting most of the way is a success.

Neither label means anything without a starting value. If you do not know where you began, you cannot say how big a stretch the target was, so you cannot say whether a partial result is a good outcome or a disappointing one. With the baseline written down, the distance travelled is a fact, and the conversation can be about what it tells you instead of about how it feels.

Baselines and honesty

A written baseline protects everyone at scoring time. It stops a target being quietly reinterpreted once the result is known, and it makes the sandbagged target visible. A target set just above a baseline that the team is sure to clear tells you something about the incentives around the goals, and it is a prompt to check those incentives rather than the team.

It also feeds the memory of judgement that the method is meant to build. A year of results is only informative if each one can be compared with where it started. The reasons for keeping that record are in what are OKRs.

Free guide, 32 pages: The OKR Playbook. Send me the guide.

Common questions about starting numbers

People ask the same few things when they first try this. Short answers follow in the section below, but there is one habit worth stating plainly here. Record the baseline on the day you set the goal, not on the day you score it. A starting value reconstructed from memory at the end of the quarter is not a baseline. It is an opinion shaped by the result.

When you review your goals mid-quarter, the baseline should still be sitting beside the target, unchanged. If it has been edited, ask why. The mid-quarter check in how to run an OKR retrospective is a good moment to confirm that the starting values were left alone.

FIKR OS, strategy meets execution: OKRs, roadmaps and kanbans in one system. See FIKR OS.

Frequently asked questions

What if the metric has never been measured?

Make measuring it the first key result. The guide treats that as a legitimate and often very valuable goal, because it shows that nobody actually knew the number.

Can I set the target first and find the baseline later?

You can, but the target is a guess until you do. The baseline decides whether the target is a stretch, a formality or an impossibility, so get it before you commit.

How precise does the baseline need to be?

Precise enough that two people reading the same data report the same number. Beyond that, an agreed source and a recorded date matter more than decimal places.

Does every key result need a baseline?

Yes. A key result with a target and no baseline is not measurable, whatever it looks like.

The full method, with the checklists, is in The OKR Playbook, a free 32-page playbook.

LG

Luis Goncalves

// Founder & CEO at FIKR Space

Three-time founder. Built and exited Evolution4All before this. Now building FIKR Space — the operating infrastructure underneath every innovation ecosystem (startups, accelerators, governments, investors). Lisbon-based, works global.

Claim your founding member spot.

Every founding member is hand-reviewed. Tell us who you are and how you want to co-create — we get back inside 48 hours.

Role
Job Title
Country
Cookies

We use cookies.

Essential ones keep the site working. The rest only run if you say so. No dark patterns, no pre-ticked boxes.Privacy policy

Co-create with us. It's about building it together.Co-Create With Us