Home/Blog/OKRs/What Are OKRs? What Goals Actually Do fo…
OKRs

What Are OKRs? What Goals Actually Do for a Company

What are OKRs? A plain account of what goals do for a company, the six effects that matter and the honest limit that decides whether the method works or fails.

Cover of the FIKR Space guide: What Are OKRs? What Goals Actually Do for a Company

What OKRs are: a way of writing down a goal as an outcome you want to change, together with the evidence that will show it changed, so that a trade-off is decided in advance instead of one interruption at a time. They are a focusing tool. They are not a way of judging people.

That second sentence is where most explanations stop too early. Plenty of articles describe the vocabulary and then leave you with a template. This one is about what the method is for, because a founder who understands the purpose can write a good goal without a template, and a founder who only has a template can write a perfectly formatted goal that changes nothing.

What are OKRs, and what are they for?

The letters stand for objectives and key results. An objective is a direction: where you are trying to get to and why it matters. A key result is the evidence that you are getting there. Put together they say what should be different at the end of a period, and how you will know.

The purpose is narrower than most people assume. A goal is not there to record intentions, because intentions were never in short supply. A goal exists to make a trade-off explicit and open to challenge before the pressure arrives. When two good things compete for the same week, the written goal is something that settles the conflict faster than a meeting can.

There is a useful test hidden in that. If a goal has never caused anyone to say no, it has not failed to be achieved. It has failed to be a goal, because it was only ever a description of work that was going to happen anyway.

Six things a goal does for a company

The case for the method rests on six specific effects on how decisions get made. None of them is alignment in the abstract.

EffectWhat changes in practice
Trade-offs become explicitPriority stops being set by whoever asked most recently and most loudly
Outcome separates from outputThe team asks what would be different, not what will be delivered
Alignment without overheadPeople make better decisions alone, need less permission and interrupt each other less
Saying no with a reasonA refusal can point to a written choice rather than to your authority
Progress without surveillanceThe weekly talk is about the number and the obstacle, not about how everyone spent their week
A memory of judgementA record builds up of what you set out to do and how good your estimates were

The rest of this article takes each in turn, because the value of the method is the sum of these effects, and a team that gets only one of them usually thinks the method is overrated.

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

Trade-offs in the open

Every company has more good ideas than capacity. That means every company is already making trade-offs all the time. The only question is whether they are made deliberately, in the open, at a moment when people can think clearly, or implicitly by whoever interrupts first.

A written goal is a decision about what will win when the conflict arrives. You feel its value in the sixth week of a quarter, not the first. Without it, priority follows recency and volume, and neither of those correlates with anything that matters to the business.

Outcome versus output

Teams are very good at producing output. Features ship, campaigns launch, tickets close. Output feels like progress because you can see it and count it. But a team can deliver a great deal and change nothing about the business, and in a busy organisation with no outcome discipline that is the normal state, not a rare disease.

Writing goals as outcomes forces a harder question: what would actually be different if we succeeded? Once that question is on the wall, some planned work turns out to be unnecessary and some unglamorous work turns out to be essential. How to phrase the evidence itself is the subject of how to write key results.

Alignment without more meetings

When a company grows out of alignment, the usual response is more meetings, more status reports and more managers relaying context. That works, but it is expensive and it scales badly.

A small set of shared, visible goals does much of the same job at almost no running cost. People who know what the company is trying to achieve this quarter decide better on their own. The benefit shows most sharply just past the size where everyone can still overhear everything, which is the moment shared context stops arriving for free.

Saying no with a reason

Declining requests is a permanent part of a founder's job, and the way you do it compounds. Refusing because you said so spends goodwill each time and teaches people to go around you or to escalate.

Refusing because the request does not serve what the company committed to this quarter, and naming the thing it chose instead, costs nothing. It can be argued on its merits, and it teaches everyone how decisions are made. Over a year that produces a company that can decline things when you are not in the room.

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

Progress you can see without watching people

Founders want to know whether things are moving. Teams do not want to be watched. Goals written as outcomes, with an honest weekly check, ease most of that tension, because the conversation is about whether the number is moving and what is in the way.

It is also a healthier failure signal. It exposes the case where a team is working extremely hard on something that is not producing the result, which is the most expensive failure there is and the one that activity reporting is worst at catching. The weekly rhythm is covered in how to run a weekly OKR check in.

A memory of judgement

A year of written goals, honest scores and short retrospectives is a record. It shows what you set out to do, what happened and how accurate your estimates were. Almost no company keeps one, and it is valuable.

  • It tells you whether you tend to overestimate or underestimate.
  • It shows which kinds of bet have worked.
  • It shows how long change really takes in your business.
  • It lets a new joiner understand not only the plan but how the company thinks.

This is the compounding benefit, and dishonest scoring destroys it completely. That is the main reason honest scores matter more than good ones. The practice is set out in how to score OKRs.

The honest limit

Ignoring this limit is what breaks companies. OKRs are a focusing tool and must not be used as a performance management tool.

The moment attainment is tied to pay, promotion or individual assessment, everyone becomes rational in a way that harms the system. They set targets they are sure of hitting, they hide bad news until the last possible moment and they argue about scoring. That is not cynicism. It is the only sensible response to the incentives.

It damages both functions at once. You lose the ambitious goal setting that made the method worth adopting, and you gain a performance system built on numbers that everyone has quietly tuned. So keep the two apart, say so out loud, and repeat it, because people will assume the opposite until they have watched you not do it.

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

What a good start looks like

If you are new to this, you do not need all six effects on day one. You need a few honest decisions.

  1. Write each objective as a direction a new joiner could understand without context.
  2. Write each key result as a changed state, not a piece of work.
  3. Keep the set small enough that leaving things out hurts. The reasoning for that is in how many OKRs a startup should have.
  4. Check the goals every week, not only at the boundaries of the quarter.
  5. Say plainly that attainment does not feed reviews or pay.

Most OKR programmes that fade fail on one of three things underneath the framework. The goals were a list of work, there were too many of them, or nothing in the weekly rhythm made anyone choose between the goal and something else they wanted to do. If you can avoid those three, the framework itself rarely needs defending.

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

Frequently asked questions

Are OKRs only for large companies?

No. The guide's argument is that the benefit appears just past the size where everyone can overhear everything. A small team that already shares context gains less from the written version, but the trade-off argument still applies whenever there is more to do than capacity.

Is an OKR the same as a to-do list?

No, and confusing the two is the commonest failure. A to-do list records work. An objective records a direction and a key result records evidence that something changed, so the work can change while the goal stays.

Should OKRs affect bonuses?

No. Tying attainment to pay or promotion pushes people to set safe targets and to hide bad news. Keep the two apart and state that openly.

How do I know whether the method is working?

Look for a goal that has caused someone to say no. If none has, the goals are probably a description of what you were going to do anyway.

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