What 29,987 Key Results Show About How Teams Run OKRs

Behavioral data from 3,527 organizations and 29,987 key results on OKRs Tool: eight findings on what teams that hit their goals do differently.

Steven Macdonald
5 Mins read
November 8, 2026
What 29,987 Key Results Show About How Teams Run OKRs

Organizations whose first key result was seen through went on to hit 53% of their later key results, against 24% when it fell short. That's one of eight findings from 29,987 key results logged by 3,527 organizations on OKRs Tool, covering what teams wrote, when they updated and how their goals finished, with no survey answers involved.

A survey can tell you that most teams say they check in weekly. Platform logs tell you when the check-ins happened, which numbers moved and which goals sat at zero until the quarter ended. That difference is why we keep a behavioral dataset alongside our survey research: it shows what teams did with their OKRs, matched to how each goal finished.

This page brings together the findings from the latest export, 29,987 key results from 3,527 organizations with around 24,000 progress updates. Each finding is an association, so it shows which behaviors travel with goals that land without proving that any one of them causes the result. Where a finding holds only partly, or holds mainly between companies, we say so.

Explore all OKRs Tool research

Platform data and benchmark reports built on more than 2,000 survey respondents, all in one place.

See the Research →

The Findings at a Glance

Three features of a key result or its organization go with large gains in the share that hit their target, and one that teams often fear goes with almost no cost.

1. The First Key Result Predicts the Rest

The single strongest predictor in the dataset is how an organization's first-ever key result finished. Organizations whose first key result reached 70% or more of its target went on to hit 53% of their later key results, against 24% when it fell short.

The pattern holds when "first" means the first key result an organization updated (55% against 23%), and even engaging with the first goal matters: organizations that updated their first key result at least once hit 39% of later key results, against 14% for those that never touched it again.

Key results hit their target 53% of the time when the organization's first key result was seen through, against 24% when it fell short; 67% with an explicit deadline against 51% without; 69% at 16 words or more against 35% at one to three words; and 68% when progress was revised downward at least once against 72% when it only went up.

The downside is the sharper half. When the first key result stayed at zero, organizations hit 16% of their later key results, 58% of the goals they set afterwards also died at zero, and they stopped adding new goals after a median of four days, against 32 days for organizations whose first key result hit.

That makes the first goal the strongest single predictor of why OKRs fail in the data, and a reason for leaders to set and visibly tend the first goals themselves as part of their leadership accountability.

2. Winning Teams Leave Almost Nothing at Zero

Splitting organizations with four or more objectives into quartiles by hit rate, the top quartile left a median of 8% of key results at zero for the whole cycle. The bottom quartile left 56%, more than half of everything it set.

Seen the other way round, the gap is in how many goals get moving at all.

An abandoned key result still counts against the completion rate and still shows up red at the quarterly review, so a team that abandons half its list reports a weak quarter however well the other half went. The gap points to follow-through as the clearest difference between the teams that hit their goals and the teams that don't.

Out of every 25 key results, the median top-quartile organization moved 23 off zero during the cycle (92%), while the median bottom-quartile organization moved 11 (44%) and left 14 at zero.

3. Key Results Rise and Fall Together

Across 1,463 objectives with actively tended key results, 49% had every key result finish within 20 points of the others, and the median gap between an objective's best and worst key result was 21 points. Outcomes cluster at the team level too, where 22% of teams hit none of their goals and 2% hit all of them.

Key results inside one objective usually share an owner, a team and the same share of attention, so they tend to slip together. When one stalls, the cause usually sits with the objective, and the rescue at the mid-quarter review works best at that level.

4. Deadlines Matter, and Numbers Alone Don't

Breaking key results into the elements of the classic template, only one stood out. Key results with an explicit timeframe hit their target 67% of the time, against 51% without one.

The other elements made little difference. Key results containing a number hit 56% of the time, against 58% without one, a percentage added four points, and key results with a number, a baseline and a timeframe together hit at almost the same rate as those with none of the three.

The practical lesson for writing OKRs is to give every key result a date someone can be held to, alongside the baseline and target that make it scorable.

5. Careful Writing Marks the Teams That Hit

Hit rates climb steadily with the length of a key result: 35% at one to three words, 45% at four to six, 47% at seven to ten, 58% at eleven to fifteen and 69% at sixteen words or more. Teams that hit their goals write a median of 14 words per key result, against 10 for teams that miss, and the climb holds when yes/no key results are excluded.

The gap sits mostly between companies, and within the same organization longer key results did only slightly better than shorter ones. Word count marks a team that thinks carefully about what each key result means, how it's measured and by when, and padding a key result with extra words won't change its odds.

6. Early Movement Predicts the Finish

Two checkpoints in the quarter carry most of the signal about how a key result will finish.

A key result that has already moved by its first check-in hits its target 62% of the time, against 27% for one still at zero. Of 1,121 key results that were flat at their first check-in, 35% never received another update.

Key results moving by their first check-in hit their target 62% of the time against 27% for those still at zero; flat key results that started moving before the midpoint recovered 66% of the time against 47% for those that started later.

The ones still being worked on could recover, and timing decided most of it. Flat key results that started moving before roughly the midpoint of the quarter recovered to 70% or more of target 66% of the time, against 47% when they started later. The first check-in shows which goals are in trouble, and the middle of the quarter is the last good chance to fix them, which matches the OKR Pacing Benchmark finding that key results that hit were typically at 50% by week four.

7. Downgrades Carry Almost No Penalty

Among key results with eight or more weeks of update history, 46% had at least one update that moved progress backwards. Those key results hit their target 68% of the time, against 72% for key results whose progress only went up.

A downgrade usually means someone looked at the number, found it was wrong and fixed it, which is how a watermelon OKR gets caught early. Making corrections normal in every weekly check-in keeps owners reporting the real figure, at almost no cost to the result.

8. Winning Key Results Often Finish Early

Of the key results that hit their target, 43% reached their final value in the first half of the cycle and held it, while the median winner locked in its result 87% of the way through. Goals that land show two common shapes: front-loaded and finished early, or steady to the deadline.

That changes how an early 100% should be read. Before calling a key result sandbagged, check the baseline and the update history, because front-loaded work is one of the normal shapes of a goal that lands. Committed goals are meant to reach 100%, while stretch goals are scored with room to fall short.

How the Platform Data Fits With Our Surveys

The behavioral findings line up with what leaders report in our survey research. In the OKR Benchmark Report, teams tracking progress as work happens hit their goals very consistently 59% of the time, against 28% when progress is rebuilt at review time, and teams with an owner on every OKR hit 65%, against 17% where only some are owned. In The Death of OKRs, 49.5% of companies had stopped using OKRs on at least one team, and half of all endings happened with nobody deciding.

The platform data shows the same story in timestamps: goals that get moving early, stay updated and get corrected when the numbers change are the ones that land, and goals left at zero take the goals around them down too.

What the Logs Say About Running OKRs

Across eight findings, the platform data points to follow-through above everything else. Organizations that see their first goal through, move their key results early, correct the numbers as they go and leave almost nothing at zero hit far more of their goals than organizations that set goals and leave them. The writing still matters in two specific ways, a deadline and a clear description, and both make a goal easier to follow through on.

For the person running OKRs, the clearest signals to watch are the first goals of a cycle and any key result still at zero after the first check-in. A platform that asks every owner for a weekly update, flags key results that haven't moved and shows everything on one live OKR dashboard makes those signals visible while there's still most of a quarter left to act on them.

Run OKRs the way the data says works

OKRs Tool asks every owner for a weekly update, flags key results still at zero and keeps progress live, so goals get moving early and stay that way. Free 14-day trial, no credit card.

Start Free →


Data: OKRs Tool platform data, The OKR Benchmark Report, The Death of OKRs (and How to Revive Them) and the OKR Pacing Benchmark.

CEO Photo

Founder

Steven Macdonald│LinkedIn│X

Steven is the founder of OKRs Tool, OKR software built for senior operators inside growing companies. Trusted by 350+ teams to run OKRs that survive beyond the first cycle — with weekly check-ins, required KR ownership and a visual alignment map that shows how every goal connects.