What Are OKRs and How to Write Ones That Work
OKRs are simple to explain and easy to get wrong. Most bad OKRs fail the same way: the key results measure activity instead of outcomes.
OKR stands for Objectives and Key Results, a goal-setting method popularized by Intel and later Google. The structure is deliberately minimal: an objective is where you want to go, and key results are how you will know you got there.
The method is easy to describe and hard to do well. The difference between OKRs that focus a team and OKRs that become a quarterly box-ticking ritual comes down to a few specific choices.
Objectives: qualitative and ambitious
An objective is a short, memorable statement of a meaningful goal. It should be qualitative and inspiring, something a team can rally around, not a metric. 'Become the obvious choice for freelance designers' is an objective. It says where you are going and why it matters.
Keep objectives few. One to three per team per quarter is plenty. A list of ten objectives is not a set of priorities; it is a wish list, and it will dilute focus rather than create it.
Key results: measurable outcomes, not tasks
This is where most OKRs go wrong. A key result must be a measurable outcome, so that at quarter end there is no argument about whether you hit it. The classic mistake is writing key results as activities: 'launch the referral program' is a task, not a result.
The fix is to measure the change you actually want. Instead of 'launch the referral program', write 'reach 200 sign-ups from referrals'. Launching is something you control; the outcome is what you are actually after. If a key result can be marked done by completing a task regardless of impact, it is a task in disguise.
- Each key result needs a number and a target, so success is unambiguous.
- Aim for two to four key results per objective.
- Measure outcomes you want, not activities you will do anyway.
- Set targets that stretch; if you hit 100 percent of every one easily, you aimed too low.
Grade and review, do not set and forget
OKRs are worthless if you write them in week one and look again at quarter end. Check in regularly, monthly at minimum, to see whether the key results are trending toward target and whether anything has changed. The check-in is where OKRs actually steer work.
At quarter end, grade honestly. On stretch goals, landing around seventy percent is often considered healthy, because consistently hitting everything means you set safe targets. Use the grading conversation to learn, not to punish.
Common OKR mistakes
- Too many objectives, so nothing is truly prioritized.
- Key results that are tasks, so you can 'succeed' without any real outcome.
- Sandbagging targets to guarantee a green score.
- Setting them once and never reviewing until the quarter closes.
- Cascading them so rigidly that teams lose ownership of their own goals.
How Atlas fits
Atlas lets you track objectives and key results alongside the projects and tasks that drive them, on one model, so a key result links to the actual work moving it. That connection is what keeps OKRs from drifting into a separate document nobody opens between quarters.