Across 876 organizations, struggling teams logged roughly twice as many initiatives per objective as high performers — and completed close to none of them. High performers logged around one initiative for every three objectives, and finished about 23%. The number of initiatives on the board isn't a measure of effort. It's a measure of how stuck the Key Results underneath them are.
An initiative is the work a team does to move a Key Result — the projects, bets, and priorities chosen deliberately because they should shift a specific number. Not more goals. Not success metrics. The actions taken to make the number move.
Most guidance treats initiatives as the missing link between strategy and execution: write good goals, add initiatives underneath, watch progress follow. The platform data points somewhere less comfortable. Initiatives are optional scaffolding, and when the list starts growing, that growth is usually a symptom of Key Results that aren't moving — not a sign the team is working harder.
What the Initiative Data Actually Shows
High-performing organizations in the platform data logged roughly one initiative for every three objectives. Struggling organizations logged about twice as many. If initiatives were the engine of progress, that relationship would run the other way.
The completion figures make it sharper. High performers finished about 23% of the initiatives they logged. Struggling teams finished close to none. So the teams with the shorter list are the ones actually shipping the work, and the teams with the longer list are accumulating projects that never get done.
The most defensible reading is that a long initiative list is a symptom of a stalling team, not a cause of one. When a Key Result refuses to move, the instinct is to add another initiative — another project that might unstick it. The list grows. The number doesn't. High performers don't accumulate initiatives because they don't need to: their Key Results are already moving.
Initiatives Are Scaffolding, Not the Structure
The value of an initiative is in the choosing, not in the tracking. Deciding that this specific project is the one that will move a Key Result forces a hypothesis: we believe X will shift the number. That decision is useful. The list of everything the team happens to be working on is not.
This is where the 52% figure becomes relevant. OKRs Tool's analysis found that 52% of Key Results across growing teams were tasks or existing metrics dressed up as outcomes. "Launch the onboarding checklist" isn't a Key Result — it's an initiative. When teams push tasks up into the Key Results layer, they lose the outcome measure entirely and the whole OKR stops functioning as a goal.
Initiatives give those tasks somewhere legitimate to live: underneath the Key Result, connected to the outcome they're meant to move, without contaminating the measure itself. That's the real job of the initiatives layer — keeping the Key Results clean.
Read the List as a Diagnostic
The practical use of an initiative list has less to do with planning and more to do with diagnosis. If a Key Result hasn't moved by mid-cycle, the list answers three questions in order.
Is the team doing anything at all that could plausibly move this number? A Key Result with no initiative underneath it and no movement isn't being worked on — it's being watched. That's the most common failure in the platform data: whether Key Results ever moved during the cycle was the strongest predictor of success in the entire dataset.
Have the initiatives stalled, or have they shipped and simply not worked? These are different problems requiring different responses. A stalled initiative is a capacity or ownership problem. A shipped initiative that didn't move the number is a hypothesis problem — the bet was wrong, and the honest move is to replace it rather than wait.
Is the list growing while the number stays flat? That's the warning sign. Adding a fourth initiative to a Key Result that hasn't budged in six weeks rarely fixes anything. It usually means the team is generating activity to avoid confronting a stuck outcome. The weekly check-in is where that pattern should surface — teams that check in weekly complete 43% more OKRs than those reviewing monthly or ad hoc, largely because drift gets caught early enough to act on.
A Complete OKR With Initiatives
The structure that works is deliberately lean: one Objective, one measurable Key Result with a named owner, and a small number of initiatives chosen because the team genuinely believes each one will move the number.
Each initiative is a hypothesis, not a commitment. If the checklist redesign ships and activation doesn't move, the right response is to drop it and try something else — not to keep it on the board and add a fourth item beneath it. Teams aren't graded on completing initiatives. They're measured on whether the Key Result moved.
Fewer Bets, Honestly Reviewed
The teams that get the most from an initiatives layer treat it as a small set of live hypotheses reviewed every week, not a backlog that accumulates across the quarter. Two to four per Key Result is a reasonable ceiling, and the platform data suggests most high performers sit well below it.
When a Key Result isn't moving, the answer is almost never another initiative. It's a harder question about whether the bets were wrong, whether they shipped at all, or whether the Key Result was miscalibrated from the start. A check-in that asks those questions produces better outcomes than one that reviews a growing list of things nobody has finished. See how OKRs Tool connects Objectives, Key Results, and initiatives in one view — free for up to 5 users.'
Data: OKRs Tool platform data (876 organizations, 7,419 objectives, 20,952 key results), The 2026 OKR Benchmark Report (330 organizations). Note: initiative counts reflect what teams logged in OKRs Tool; teams tracking project work in separate systems may log fewer initiatives than they run.
