OKRs Are Not a Reporting Format

It is the quarterly review. A product team puts its OKRs up on the screen. A leader scans the slide and asks the question that gets asked in these rooms everywhere. “Good, so where are we on each of these, and what are we shipping next quarter?” Every key result is sitting at a comfortable green. The team walks through the percentages, everyone nods, and the meeting moves on to the next team. The OKRs did exactly what they were asked to do in that room, which was to look reassuring. They did nothing else, because somewhere along the way they stopped being objectives and became a status dashboard.

This is one of the most common ways a good practice goes hollow. OKRs were meant to be a commitment to a meaningful change in the world. In a great many organizations they have quietly degraded into a reporting layer. It becomes a quarterly form to complete, a set of fields to turn green, and a way to look accountable without changing what the team actually does. Christina Wodtke wrote Radical Focus, the definitive book on the method. She is blunt that OKRs were never meant to be to-do lists or accountability charts. She likens it to a stepsister trimming her foot to fit the glass slipper. Bolting the format onto a team that has not changed how it works is painful and ultimately unconvincing.

What OKRs were supposed to do

An OKR is a commitment to an outcome. The objective names a meaningful change the team intends to create. The key results put numbers on what that change looks like, so the team can be honestly judged on whether it happened. The entire mechanism exists to point a team at a result that matters and to hold it there. The alternative is a list of things the team kept itself busy with.

That framing carries a specific kind of power, which is the power to decline. When a team has committed to moving a real outcome, every proposed piece of work has to answer whether it serves that outcome. The ones that do not can be turned away. As the definition of OKRs puts it, they put everything in context and make it easier to shoot down ideas that will not move the needle. An OKR that cannot be used to say no to something is not functioning as an OKR.

An OKR is a bet you are willing to lose

A real objective carries the possibility of failure. That possibility is the source of its value, not a flaw in it. Say a team commits to reducing churn by a third and lands at a fifth. That gap is useful information about the world, and about the team’s understanding of it. The willingness to set a target you might miss is what makes the eventual number mean something. A goal you are certain to hit was never a commitment, it was a description of what you were going to do anyway.

The slow drift from commitment to reporting

No team decides to turn its OKRs into theater. The drift happens gradually. It is usually driven by the questions leaders ask, not by any failure on the team’s part. The degradation is a rational response to an incentive. That is why it is so widespread, and so hard to see from the inside.

The mechanism is well described by Jeff Gothelf, who points out that when leaders keep asking a team what it is going to build, well-written OKRs slowly turn into a task list of projects and initiatives. The team senses that leadership values the feature list more than the outcome, so it gives leadership what it rewards. The key results drift a little further each quarter, from “this is the change we will create” toward “these are the things we will deliver.” Eventually the OKRs are just a delivery plan wearing different formatting.

A field that is always green has stopped measuring anything

Once OKRs become a reporting artifact, the incentive flips entirely. The goal of a report is to look good. So the targets get set where they can be hit, and the status stays green. The quarterly review becomes a performance of progress rather than an honest accounting of it. A key result that has never once come in red is a decoration, not a measurement. Real measurement requires the genuine possibility of an uncomfortable number. The same instinct shows up when teams are pushed to dress their work in metrics that protect them, the dynamic we examined in how good teams get forced into bad narratives, where the OKR exists to justify the team rather than to direct it.

The tells of OKR theater

It is usually easy to spot OKRs that have become reporting, once you know what to look for. The signs are consistent across organizations, and any one of them is a signal that the practice has drifted from commitment toward performance.

Targets set low enough to guarantee a win

The clearest tell is sandbagging. When the numbers attached to key results are set comfortably within reach, the team has optimized for the wrong thing. It is aiming to hit the targets, not to create the change worth pursuing. A quarter of perfectly met targets is not evidence of a high-performing team. It is usually evidence that the targets were chosen to be met. Ambition and the risk of falling short are supposed to be baked into the format.

Outputs wearing the costume of outcomes

The second tell is key results that are really tasks. “Launch the new onboarding flow” is something the team will build, but it tells you nothing about whether anything improved. A genuine key result describes a change in customer behavior or business result, such as new users reaching their first success faster. When the key results read like a release checklist, the OKRs have already become a delivery plan. The outcome the work was meant to serve has fallen out of view.

OKRs that never fail, and objectives that never sit still

The third tell comes in two forms that often travel together. OKRs that never come in red have stopped carrying real commitment. Because these objectives get rewritten every few months, they never stay still long enough to judge anyone against them. As a result, no one is ever accountable for missing one. Christina Wodtke is clear that the discipline is the point: OKRs are set for the quarter and reviewed in a steady weekly cadence, not quietly rewritten whenever the number looks at risk. A commitment you can revise on a whim is not a commitment at all.

Why the roadmap and the OKRs are different artifacts

A lot of the drift comes from collapsing two different things into one. There are two separate questions here. One is what change the team is committed to creating. The other is how the team currently plans to create it. OKRs answer the first; the roadmap answers the second. When the two get merged, the OKR inherits the roadmap’s job of listing planned work. That is the moment it turns into a task list.

Keeping them distinct is what lets each do its job honestly. The OKR carries the commitment, the measurable change the team will be held to. It should stay stable across the quarter. The roadmap shows the plan, the team’s current best thinking about how to hit that commitment. It is allowed to flex freely as the team learns. We made the broader case for that flexibility in why Now-Next-Later is more honest than any timeline, and the same separation applies here. A roadmap can change every week without weakening anything. The commitment lives in the OKR, not in the list of features. Conflating them produces the worst of both. You get a commitment that flexes whenever it is inconvenient, and a plan that everyone treats as a promise.

Restoring OKRs as the commitment the roadmap serves

Pulling OKRs back from reporting toward commitment is a set of deliberate choices, and most of them are about restraint rather than effort. The aim is to make the OKRs few enough, real enough, and stable enough that they once again function as the thing the rest of the work answers to.

Write fewer, and let them be losable

Most teams have too many OKRs, which dilutes focus and makes the whole set feel like a checklist. The consistent advice across the field, reflected in our own product OKR examples, is to run one to three objectives at a time, each with a small number of key results, and to set targets ambitious enough that missing one is a real possibility. Fewer and losable is what restores the commitment. Look at your current set: how many of your key results could plausibly come in red this quarter? If the honest answer is none, you are looking at a report.

Ask what users will do differently, not what you will ship

Because the drift is driven by the questions leaders ask, the repair starts there too. Gothelf’s suggested replacement for “what are you going to build” is to ask what users will be doing differently if the team succeeds this quarter. That question pulls the team back toward outcomes and away from the feature list, and it is a small change in a recurring conversation that reshapes what the OKRs become over time. Leaders get the OKRs they ask for.

Separate the commitment from business as usual

Not everything a team does belongs in an OKR. Routine operational work and ongoing maintenance are real and necessary, and stuffing them into the OKR format is part of what makes objectives feel like a status report of everything happening. Reserving OKRs for the meaningful changes the team is genuinely betting on, and tracking the routine work separately, keeps the objectives focused on commitment. This is also why forcing every team into the same outcome-and-metric mold backfires for enabling and platform teams, a problem we worked through in why platform teams should not have to pretend to be revenue teams.

Why OKRs have to be losable to mean anything

The quickest test of whether an organization has real OKRs or a reporting format dressed as OKRs is to ask what happens when one is missed. In a team with real OKRs, a missed objective triggers a useful conversation about what the team learned and what it should do differently. In a team with reporting, a missed objective is an embarrassment to be avoided, which is exactly why the targets get set low enough that it never happens.

OKRs only do their work when they carry genuine commitment, when the team has bet on a change it might not achieve and is willing to be honest about the result. The moment an OKR’s purpose becomes looking good in a quarterly review, it has stopped being an objective and started being decoration, and decoration moves no outcomes. Keep them few, keep them honest, keep them losable, and keep them separate from the roadmap that serves them. A green dashboard was never the goal. The change behind the number always was.