How to Write OKR Objectives (With Examples)

Most teams can spot a bad objective when they see one, but find it harder to explain what makes a good one work. The wording feels off, the team never quotes it, and by week three of the quarter nobody remembers it without opening a document.

This article breaks down how to write OKR objectives that hold up in practice. We will start with the basics of what an objective is, look at a simple test that separates strong objectives from generic ones, walk through two real examples, and finish by rewriting a typical weak objective into something a team can actually rally behind.

If you are new to the framework as a whole, the broader guide on how to write great OKRs covers objectives and key results together. Here we go deep on the objective alone.

What an objective is, at its most basic

Before anything else, it helps to strip the objective down to its core. An objective is:

• The ambition. It describes what we want to achieve, not how we will measure it.
• Inspiring. It should be filled with vision and strategy, something worth working towards.
• Free of numbers. Metrics belong in the key results, not in the objective itself.

That last point is worth dwelling on, because it is where many teams go wrong from the start. The moment a number appears in an objective, it stops being an ambition and becomes a measurement. In OKRnest this separation is built into the structure itself: objectives cannot carry metrics, and key results must have them. The tool simply does not let you blur the line.

If you want a starting point for the wording, there is a simple formula: verb + what we should do + why. ”Turn our retail customers into fans by over-delivering at every step of the journey” follows it exactly. The formula is support, not a rule, but it pushes you towards objectives that are active, concrete and motivated.

The quick test: could this be anyone’s objective?

When I look at an objective, the quickest test is to ask whether it could come from any organisation, or whether I can feel that it fits this particular team or company. If it is too generic and does not convey choices or strategy, I can see that right away.

”Increase profitable growth” fails the test. So does ”improve customer satisfaction” or ”become more data-driven”. Any company in any industry could have written them, which means they say nothing about what this organisation has chosen to focus on.

A great objective, by contrast, carries traces of strategy in its wording. It hints at a chosen customer segment, a promise the company has made, or a bet it is making this cycle. When you read it, you learn something about the organisation.

This test works because objectives exist to communicate focus. Strategy is fundamentally about making choices, and an objective that makes no choices is not doing its job, no matter how polished the wording is.

The most common failure: trying to say everything

The pattern I see most often in poorly written objectives is that they are too wordy. The team has tried to get too much into a single sentence, and I know immediately that it will not stick and it will not work.

What usually happens is that the objective tries to tell the whole story behind the goal. It picks up as much as possible from the strategy document and stretches itself to fit as many key results as possible underneath. Instead of making choices, the team is bringing everything along. The result is a paragraph pretending to be an objective, and nobody can repeat it from memory.

There is a second failure mode that often travels with the first: lack of inspiration. When an objective is written by consensus, the group tends to settle on a safe summary of what should be included and then finalise it. Along the way, the opportunity to connect the objective to the vision and mission quietly disappears. What remains is a flat statement of business focus that gives very little reason to get up in the morning and work towards it.

Both failures are covered in more depth in the article on the most common OKR writing mistakes, but they are worth flagging here because they are the two things a great objective must avoid by design.

Two examples of great objectives

Abstract principles only carry you so far, so let us look at two objectives I would consider great, and why they work.

”Turn our retail customers into fans by over-delivering at every step of the journey.”

This objective is strong because it contains inspiration and a will to do something positive. It is something a team can rally behind. At the same time, the objective almost starts generating its key results for you: you immediately begin thinking about how this might be measured, perhaps through customer satisfaction, or through service speed towards this particular segment. It also shows a clear strategic focus, a specific customer segment with a specific strategy attached to it.

”Deliver on our promise to grow our team members at a higher pace than they would grow anywhere else.”

This one is very specific to a company in a particular situation, an employer that has promised its people a place to really grow. It connects clearly to who the organisation is, and it communicates unmistakably that enabling employees to grow is a strategic priority. The key results will admittedly be trickier here, since growing people may not have obvious metrics, but it can be measured: employee engagement surveys, asking employees the question outright, or counting how many people have stepped into new roles within a set period.

Notice that both objectives pass the quick test. Neither could have been written by a random company. One reveals a bet on a customer segment, the other reveals a promise that defines the employer brand.

Inspiring and practical at the same time

Should objectives be inspiring or practical? The honest answer is both, and the balance matters.

Objectives should use inspiring wording, and being inspiring usually means being positive. They should be about moving towards something we want to see, rather than fixing something we want to avoid. An objective that says ”lower churn” frames the work as damage control. An objective built around making customers stay longer frames the same work as something worth doing. It is a better, stronger battle cry for the organisation to rally behind, even though the underlying business problem is identical.

At the same time, the content needs to be grounded in reality. Inspirational wording is not a licence to drift into vision statements. The objective still needs to be easy to understand and concrete enough that the team knows what it is actually about. If it could double as a line from the company’s ten-year vision, it has floated too far from the quarter it is supposed to guide.

Choosing your ambition level

There are two common approaches to how ambitious the wording of an objective should be, and both can work.

Some organisations let their objectives aim for the stars. They might write ”be the best workplace in Sweden” knowing full well they will not achieve it during the upcoming cycle. The objective stays at that ambitious level, and the key results define what progress looks like this quarter.

Other organisations write objectives that set out the ambition for the current cycle specifically. The same underlying goal in such an organisation might read ”reach the top 20 of Sweden’s most attractive workplaces”, a level the team genuinely intends to hit this cycle.

Neither approach is wrong. The one thing that matters is that the organisation chooses a path and applies it consistently. If one team writes moonshot objectives and the team next door writes cycle-calibrated ones, the objectives stop being comparable, and employees can no longer tell what level of ambition is baked into the words they are reading. Decide once, organisation-wide, and make the convention explicit.

How long should an objective be?

There is a sweet spot in the wording, and you tend to know it when you see it: not too short, not too long.

On the long end, the objective should be short enough to be memorable and concise. It should not mix several focuses into one sentence. One objective, one clear strategic intent. If you need a comma-separated list to capture everything, you are looking at two objectives, or at an objective that has not made its choices yet.

On the short end, an objective that is too brief usually loses what makes it unique to your organisation. ”Increased profitable growth” is three words, but it is not strategically unique. It is essentially a key result placeholder, a label sitting on top of the metrics that adds nothing of its own. A great objective needs at least a couple of words that make it inspiring, ambitious and worth following.

One thing the objective never needs is a deadline. The OKR cycle is the timeline, and every objective and key result inside it inherits that time frame automatically. Writing ”by Q3” into the objective only adds noise.

Strategic OKRs, team OKRs, and how tight the strategy link should be

How tightly should an objective connect to company strategy? The answer depends on which kind of OKR you are writing.

Strategic OKRs are basically a condensed form of the strategy itself, condensed in time frame and in focus. Their objectives should have a very strong link to strategy, because that is their entire purpose.

Team OKRs are based on the strategic OKRs, so the link to strategy is still there, but it runs through a layer. A team’s objectives can also include things that are more team-related, such as improving the quality or output of the team itself. Those objectives are not always 100 percent aligned with the wording of the strategy, and that is fine. A team that gets better at what it does supports the strategy too, just less directly.

This distinction matters when you apply the quick test from earlier. A strategic objective should reveal the company’s choices. A team objective should reveal the team’s choices within that frame. Both should still feel specific to their owner.

Rewriting a bad objective, step by step

Let us put all of this together by rewriting a weak objective into a great one, walking through the thinking at each step.

We start with a classic: ”Lower churn.”

It is short, it is measurable-sounding, and it is exactly what the business needs. It is also negative, generic and uninspiring. It frames the quarter as damage control, and it could belong to any subscription business on the planet.

The first improvement is to flip it from negative to positive: ”Make customers stay longer.” Same business problem, but now the team is building towards something rather than fighting against something. This is already a better battle cry.

The second improvement is to bring in the organisation’s own culture and language, and to add genuine inspiration. What do we actually believe about our customers? What would staying longer look like if we did it brilliantly? That thinking might land somewhere like: ”Turn our customers into fans who stay longer and recommend us to others.”

Now the objective passes the test. It is positive, it carries an ambition (fans, not just retained accounts), and it points towards key results without containing any: retention numbers, recommendation rates, satisfaction scores. The exact wording should be your own, in your organisation’s voice, but the direction of travel is the point: from a generic metric instruction to a specific, inspiring statement of intent.

The rewrite is rarely a single step. Expect to iterate the wording a few times with the team, reading each version aloud and asking whether it sounds like something you would actually say about your own work.

The takeaway

A great objective is an ambition, not a measurement. It is positive rather than corrective, specific to your organisation rather than generic, concise enough to remember, and free of numbers and deadlines. The quickest quality test remains the simplest one: if this objective could belong to any organisation, keep working on it.

When you have a draft you believe in, run it through the OKR writing checklist before you commit, and then give the wording one final read aloud with the team. If it sounds like you, fits your strategy, and makes someone want to start working, you have written a great objective.

FAQ

Can an objective contain a number if it feels natural?

It is very rare that an objective should contain a number. The moment a number appears, the statement tends to become a measurement, and measurements belong in the key results. There are exceptions, an objective could of course be to become number one in your market, for example. But if a number feels essential, it is usually a sign that you are looking at a key result that needs a proper objective above it.

Should the objective mention a deadline like "by end of Q3"?

No. The OKR cycle is the timeline, and everything inside the cycle inherits it. Adding a deadline to the objective only repeats information the framework already provides.

What if my team's objective does not map directly to company strategy?

For team OKRs that is often fine. Team objectives are based on the strategic OKRs, but they can also target the team's own quality and output. Improving how the team works supports the strategy indirectly, even when the wording does not mirror the strategy document.

Is "Turn customers into fans" too vague to measure?

The objective itself is not meant to be measured, that is what the key results are for. A wording like this actually suggests its own measurements, such as customer satisfaction, retention and recommendation rates. Vague is when neither you nor the team can think of any sensible key result at all.