Ask a team lead how many OKRs their team is running and the honest answer usually comes with a wince. Eight objectives. Six. A dozen key results spread across them. Each felt necessary in the planning meeting. Together they describe a team pursuing everything and moving nothing.
The question has a real answer, and it is smaller than what most teams are carrying.
The working number is one or two objectives
For a single team running OKRs in a single quarter, the budget is one objective, maybe two, with three to five key results each. That is the whole allocation, not one per person or per function. One or two for the team, for the quarter.
A company can carry more. If leadership runs three or four company objectives and each department picks up the one or two that apply, the tree stays legible top to bottom. The moment a ten-person team writes its own eight, that legibility is gone and the exercise stops doing anything useful.
What eight objectives actually does
Eight objectives per team is the most common failure mode I see, and it never looks like failure at the start. It looks responsible. The team wants goals covering product quality, hiring, a launch, technical debt, response time, documentation, a partnership, and onboarding. Every one is real.
Here is what that list does over a quarter. Attention is finite, and eight objectives split it into slivers too thin to move anything. The owner of objective six checks in twice and then goes quiet, because objectives one and two are where leadership is looking. By week eight, half the list is stale and nobody has said so. At quarter-end the team grades a catalog of things it was going to do anyway and calls the 40 percent that happened a partial win.
A list of eight reads as priorities but functions as the team's job description with the word "objective" stapled to each line. That is closer to a KPI dashboard or a backlog than to a set of quarterly bets.
Why the count predicts whether work moves
There is a direct line between how many objectives a team runs and whether any of them move, and it runs through the work. An objective moves when real work is pointed at it: projects and tickets that someone is spending hours on this week. A team has a fixed number of those hours.
Split that capacity across two objectives and each gets enough work behind it to show a change by quarter-end. Split it across eight and each gets a fraction of someone's attention, which produces status updates and not outcomes. This is why goal counts and self-reported progress tell such different stories: the progress bar creeps up because a human typed a number, while the work underneath never had the mass to move the metric.
So if you want to know whether a team has too many OKRs, do not count the objectives. Count the ones with real work mapped to them this week. The rest are decoration, and decoration on a goal board is where trust in the whole system quietly leaks away.
How to cut down without a fight
Cutting is harder than adding, because every objective has a sponsor who will defend it. A method that works: put them on one page and ask one question. If we could move only one this quarter, which would it be? Rank the rest against that. The top one or two are your objectives. Everything below the line sorts into two piles.
Some of it is ongoing work that belongs as a KPI you monitor, not an objective you are trying to change. Keeping response time under two hours is a health metric, not a quarterly bet. The rest is backlog that can wait without the company noticing. Move it there and stop grading it.
Then grade the survivors before you commit to them. A short list of weak objectives is no better than a long one. The five checks in how to grade OKRs take about two minutes per objective and catch the ones that are really tasks wearing an objective's clothes.
Fewer objectives, each with work behind it, beats a comprehensive list every quarter. If you are choosing a system to run them in, the goal-setting software roundup compares how the main tools handle focus and ownership. Vindaris ties each objective to the work moving it, so one with nothing behind it shows up empty instead of green.
FAQ
How many key results should each objective have? Three to five. Two usually means the objective is thin or you have looked at success from only one angle. Six or more means you have started listing tasks and diluted the objective until nothing is clearly the point. Objectives and key results are separate budgets, and both stay small on purpose.
Can a company have more OKRs than a single team? Yes. Leadership can reasonably run three or four company objectives, and each department picks up the one or two that apply to it. The number stays small at every level, but it compounds down the tree, which is exactly why an individual team writing eight of its own breaks the whole structure.
What do I do with the goals I cut? Sort them into two piles. Ongoing work that needs watching becomes a KPI you monitor rather than a quarterly bet. Everything else is backlog that can wait without anyone noticing, so move it there and stop grading it as though it were an objective.