What to Leave Out of Your OKRs on Purpose
When a planning cycle starts, teams naturally want to route every initiative on their list through OKRs. It feels responsible: write it down, give it a Key Result, make sure it gets attention. But a team, especially a shared resource like an IT or engineering group, only has so many hours in a quarter. When every worthwhile idea gets an Objective, capacity gets spread across too many fronts, and nothing gets the traction it needs. The uncomfortable truth is that focus doesn't mean picking the best ideas and OKR-ing everything else too. It means saying no to good ideas, on purpose, so the chosen few can actually succeed.
Good Ideas Are Not the Bar
The mistake most teams make is treating "is this worth doing" as the test for whether something becomes an Objective. Almost everything on a roadmap clears that bar. The real question is different: does this deserve to compete for our limited attention this quarter, ahead of everything else we could also be doing? Christina Wodtke's Radical Focus makes this argument directly: teams that succeed with OKRs are ruthless about cutting the list down to a small number of objectives, not because the rest don't matter, but because trying to make progress on everything guarantees mediocre progress on all of it.
Leaving something out of your OKRs is not the same as deciding it's unimportant. It's a statement about sequencing. A worthwhile initiative that doesn't make this quarter's cut can still happen, just not as an Objective competing for the same limited capacity as your top priorities.
Three Places Excluded Work Should Actually Go
Routine operational and maintenance work belongs in the standing backlog, not an OKR. Patching servers, renewing certificates, clearing a support queue, updating documentation, these things need to happen every quarter regardless of what the OKRs say. Turning them into Key Results doesn't make them more likely to get done, it just clutters the OKR list with items that were never really about achieving something new.
Initiatives that need heavy cross-team resourcing but aren't this cycle's top priority should go through a separate intake process, not be shoehorned into OKRs to get attention. Teams sometimes attach a big initiative to an Objective purely because they know that's how leadership pays attention. That's a symptom of a missing portfolio process, not a reason to inflate the OKR list. A shared intake or roadmap review, separate from OKRs, is the right venue for weighing big cross-team asks against each other and deciding what gets resourced next.
Anything that doesn't clearly ladder up to this cycle's chosen objectives should wait for a future cycle, not get added as a bonus objective. If a new idea surfaces mid-planning and it doesn't connect to the direction leadership has already committed to, the answer is usually "not yet," not "let's squeeze in one more objective." Every extra objective dilutes the attention available for the ones that were chosen first.
An Example: Declining to OKR the Right Way
An engineering team was asked to add "migrate our internal admin tools to a new design system" as a Key Result under this quarter's platform reliability Objective. The work was legitimate and the team agreed it should happen eventually. But it had nothing to do with reliability, and squeezing it in would have meant splitting attention between fixing the flakiest part of the deployment pipeline and a design system migration that could wait. The team leader declined to add it as a Key Result. Instead, the migration went into the team's standing backlog as a prioritized item for the following quarter, with a note explaining why it was deferred rather than dropped. Reliability work stayed the single focus, and the migration didn't get lost, it just waited its turn.
How to Tell If Something Belongs Outside OKRs
Ask three questions before adding anything to the OKR list. Does this repeat every quarter regardless of strategy? If yes, it's operational work for the backlog. Does this need resourcing from multiple teams but isn't the top priority for any of them right now? If yes, it belongs in a portfolio or intake process. Does this fail to connect to the objectives already chosen for this cycle? If yes, it can wait for the next one. Only initiatives that fail all three tests, ones that are new, strategically important right now, and clearly tied to what the organization is trying to achieve this cycle, deserve a place in the OKR set.
Michael Porter's classic "What Is Strategy?" makes essentially the same argument at the organization level: strategy is defined as much by what an organization chooses not to do as by what it chooses to pursue. The same discipline applies one level down, at the OKR set. Leaving things out of your OKRs on purpose isn't neglect. It's the discipline that makes the things you did choose actually achievable.