What is an OKR? A plain-English guide for team managers

Your team is busy every week, yet at the end of the quarter it is hard to say what actually changed. Someone suggests OKRs, and suddenly there are templates, scoring rules and opinions everywhere.

This guide explains what an OKR is in plain words: the three parts, how progress is measured, what a quarter looks like week by week, and one full example you can copy. No framework jargon, and nothing you need a consultant for.

What does OKR stand for?

OKR stands for Objectives and Key Results. It is a simple way for a team to agree on what matters most this quarter and how they will know they got there.

That second half is the point. Plenty of teams agree on what matters. Far fewer agree on how they will know. OKRs force that answer into a few numbers everyone can read the same way.

The three parts of an OKR

An OKR has two parts on paper and a third that keeps it alive.

• Objective: where you want to be. Qualitative, short and a little ambitious. “Make the core workflow twice as fast.” No numbers here; the objective is the direction, written so a teammate would remember it.
• Key results: the proof. Two to five numbers that show you got there. “Cut median time to create a report from 12 to 6 minutes.” Each one has a start, a target and one owner.
• Check-ins: the habit. Once a week, each owner updates the number and says how confident they are. Five minutes, not a meeting.

Without the third part, the first two become a slide nobody opens after week two.

An OKR example, start to finish

Here is one objective for a product team, with three key results:

Objective: Make pricing clear enough to buy without a call.

Key result	Start	Target	Owner
Raise trial-to-paid conversion	8%	12%	Product lead
Cut pricing questions to support	90 a month	30 a month	Support lead
Grow self-serve upgrades	40 a month	75 a month	Growth

Notice what is missing: “launch the new pricing page” is not on the list. That page is probably how the team will move these numbers, but it is a task, not a result. If the page ships and conversion stays at 8%, the objective has not been met. The difference between the two is the most common stumbling block, and we cover it in how to write key results that measure outcomes.

How progress is measured

Progress is how far the current value has moved from start to target. If trial-to-paid conversion starts at 8%, the target is 12% and today it is 10%, progress is (10 − 8) ÷ (12 − 8) = 50%.

That number alone does not tell you whether 50% is good. Halfway through the quarter, it is right on plan. Two weeks before the end, it is behind. So progress is compared with planned by now: where the key result should be today if the work goes the way you expect.

Not everything grows in a straight line. A key result that needs research first may barely move for six weeks and then jump. Choosing a path that matches how the work really happens keeps the plan honest, so a research-heavy key result is not marked as behind in week three.

Status compares progress with the plan, together with the owner’s confidence: on track, at risk or off track. At the end of the quarter, each key result gets a score from 0.0 to 1.0. We go deeper into scoring, confidence and paths in OKR scoring and the weekly check-in.

A quarter, week by week

A typical OKR quarter has four moments:

1. Week one: set two or three objectives. Draft them with the people who will do the work, agree on owners and write down the starting values.
2. Every week: the check-in. Each owner updates the number, gives a confidence from 1 to 10 and adds a line on what changed.
3. Mid-quarter: a longer look. Is anything clearly off track? Does a key result need a different path, or was it the wrong number?
4. The last week: score and carry. Give each key result a final score, write down what you learned, and decide which unfinished key results move to the next quarter.

Thirteen weekly check-ins at five minutes each is just over an hour per owner for the whole quarter. That is the real cost of OKRs, and it is small next to a quarter of work pointed the wrong way.

How many objectives and key results?

Fewer than you think:

• Two or three objectives per team, per quarter. Never more than five. Every extra objective takes focus from the others.
• Two to five key results per objective. Three is the sweet spot. One key result is easy to game; six cannot be tracked.
• One owner per key result. A person who owns more than four usually updates none of them.

Too many objectives is only one of the ways OKRs go wrong. The others are in common OKR mistakes.

When OKRs are the wrong tool

OKRs are for the few things you want to change. They are not for everything your team does. Keeping systems running, answering customers and closing the books every month are real work, but they do not belong in OKRs unless you are trying to change how they go.

OKRs are also not a performance review. Tie them to bonuses and people start setting targets they know they can hit, which defeats the purpose. Keep the two separate.

How Manager Kit helps with OKRs

In Manager Kit, the OKRs module holds your objectives and key results for each quarter, with an owner for each: someone on your team or you. You pick a planned path for every key result, from a steady line to “research first”, and the weekly check-in records the value, a confidence from 1 to 10 and a note. The quarter chart shows progress against the plan, and key results that are due a check-in appear on This week. The guide inside the module has this explanation, an example library of 36 objectives to borrow, and prompts you can copy into the AI tool you already use. The kit is used by you alone, and the data stays on your device.