I have sat through more OKR readouts than I care to count, and most of them follow the same script. A team presents a deck. The objectives are inspirational. The key results are color-coded green, with one brave yellow to show humility. Everyone nods. Then the deck closes, the quarter resumes, and the work people actually do that week has almost nothing to do with what was on the slides. The OKRs were a performance. They got written, presented, and forgotten, and the only thing they reliably produced was the meeting where they were reviewed.
That is OKR theater, and it is the default outcome of the process, not a failure of one bad team. The OKR framework, objectives and key results, is genuinely useful. The ceremony that has grown up around it is what kills it. So when we rebuilt how we do goal setting, we threw out almost all of the ritual and kept the single thing that matters, which is whether the goals change what people choose to work on when nobody is watching.
The test for a real OKR
Here is the only question I ask of any objective and key result. Does it change a decision? If a goal does not cause someone to pick up one task instead of another, to say no to a request they would otherwise have said yes to, or to stop a project that is no longer serving the objective, then it is not a goal. It is a wish written in goal format. And a company full of wishes will produce a lot of nice slides and very little focus.
Most OKRs fail this test because they were written to describe what the team was already going to do. That is the quiet trap. You take your existing roadmap, dress each item up as a key result, and now you have OKRs that are guaranteed to hit because they were never going to influence anything. They are a forecast wearing the costume of a goal. A real key result creates the possibility of changing course. If there is no version of the quarter where you look at the metric and decide to do something different, the metric is decoration.
Fewer goals than feels comfortable
The single biggest improvement we made was cutting the number of objectives until it hurt a little. A team with seven objectives does not have seven priorities. It has zero, because everything is a priority and therefore nothing is. When every initiative can be justified as serving some objective, the OKRs have stopped doing their one job, which is to tell you what not to do.
We hold most teams to one or two objectives per quarter, with two or three key results each. That feels uncomfortably small to people the first time, because it forces them to leave good work off the list. That discomfort is the point. The value of a goal comes entirely from what it excludes. If your objectives include everything you might work on, you have written an inventory, not a strategy. The teams that ship the most are almost always the ones with the shortest goal lists, because clarity about the few things that matter is what lets them move fast on those things and ignore the rest with a clear conscience.
Kill the quarterly grading ritual
The most theatrical part of the OKR process is the end-of-quarter grading. Teams assign a score of 0.0 to 1.0 to each key result, debate whether a 0.7 should really be a 0.8, and produce a tidy summary that goes into a deck nobody reads after the meeting. The scoring feels rigorous. It is mostly a ceremony that converts the previous three months into a number whose only function is to be reported.
We do not grade quarters anymore. Instead we check progress against the key results continuously, in the same place the work lives, so that the number is always current and nobody has to reconstruct it at the end. The question is never "what score did we earn." It is "given where this metric is right now, what should we change this week." A goal that you only consult at the start and the end of a quarter cannot influence the middle, which is where all the actual deciding happens. The grade is a backward-looking artifact. We care about the forward-looking decision.
This is also where most goal-setting software gets it backward. Tools that live in a separate planning app, disconnected from the tasks and projects where work happens, guarantee that goals and work drift apart. We keep objectives next to the projects that serve them in Atlas, so progress on the work rolls up to the goal without anyone maintaining a parallel spreadsheet. When the goal and the work are the same surface, alignment stops being a meeting and becomes a property of the system.
Set the cadence at the week, not the quarter
OKRs are usually framed as a quarterly exercise, and that framing is half the problem. A quarter is too long a loop. By the time you grade it, the decisions that mattered are already three months gone. The objective should be set for the quarter, yes, because direction needs to be stable enough to commit to. But the moment that the objective actually earns its keep is the weekly one, when a person or a team looks at what they could do and uses the goal to decide what they will do.
So our planning rhythm pushes the OKR into the week. Objectives are set quarterly and barely touched after that. Key results are reviewed often enough that they inform the next sprint of work. And the conversation we want is small and frequent: what is in the way of this key result, and what is the single most useful thing we can do about it before we meet again. That conversation is worth more than any quarterly readout, and it takes a fraction of the time.
- One or two objectives per team, no more, even when it feels too few.
- Key results that could plausibly come out red, because a goal you cannot miss is not a goal.
- No quarterly grading ceremony; review progress where the work already lives.
- Use the goal weekly to decide what to do next, which is the only time it pays off.
Alignment is the real product
When people complain that OKRs do not work, what they usually mean is that the process consumed time and produced slides. That is a fair complaint about the theater. It is not a fair complaint about the underlying idea, because the underlying idea, getting a whole organization pointed at the same small set of outcomes, is one of the hardest and most valuable things a company can do. Alignment does not happen by accident at any scale beyond a single room.
So strip the ceremony without mercy. Cut the deck, cut the grading, cut the objectives down to the few that matter. Keep the one mechanism that justifies the entire framework: a clear, shared set of goals that genuinely changes what people choose to work on each week. That is OKRs without the theater, and it is the only version that has ever made a team of mine move faster instead of just look busier.