How Many OKRs Should You Have?
One of the first questions any team asks when adopting OKRs is how many they should actually write. The honest answer is: fewer than you think. OKRs are supposed to be a filter for what matters most, not a comprehensive list of everything a team is working on. If your OKR list looks like a full project backlog, it has stopped doing its job.
The Common Guidance
A widely used rule of thumb is three to five Objectives per team per cycle, each with two to four Key Results. That's not a hard law, but it's a reasonable starting point. It forces real prioritization, since you can't credibly claim ten things are all top priorities at once. If everything is a priority, nothing is.
The number of Key Results matters just as much as the number of Objectives. Two to four per Objective is usually enough to define what "done" looks like without turning the Objective into a task list. Once you're past four or five Key Results on a single Objective, you're often tracking activities rather than outcomes.
Why Teams Overload Their OKRs
Teams rarely set out to write fifteen Objectives. It usually happens gradually. Someone wants to make sure their project is represented. A stakeholder asks for their initiative to be tracked. Nobody wants to say no, so the list grows one addition at a time until the OKR set has quietly turned into a wish list.
The fix isn't a stricter rule, it's a clearer question: what will we actually focus on this cycle, even if it means other reasonable, good ideas wait. That's an uncomfortable conversation, but it's the conversation OKRs exist to force. It's the same discipline behind Harvard Business Review's case for focusing on fewer projects, which found that organizations make faster progress by deliberately stopping work that no longer matters, not by starting more of it.
Fewer OKRs Create Real Focus
A short OKR list is easier to remember, easier to talk about in a check-in, and easier to actually act on day to day. When people can recall their team's Objectives without looking them up, those Objectives are actually shaping decisions. When the list is long, it fades into the background and daily work goes back to being driven by whatever feels urgent instead of what's actually important.
This is one reason Easy OKR keeps its interface simple and doesn't encourage long, sprawling OKR trees. A shorter list that people actually use beats a comprehensive one that gets set once and forgotten.
Adjusting the Number for Team Size and Maturity
A small startup team might do fine with a single organization-level Objective and a couple of supporting ones, since alignment is easy when everyone sits in the same conversation. Larger organizations with multiple teams need a bit more structure to cover different functions, but the same principle applies at every level: each team should still be able to name their top few priorities without hesitating.
Teams new to OKRs also tend to do better starting smaller. It's easier to build the habit of writing measurable Key Results and checking in regularly with two Objectives than with six. You can always add more structure once the basic rhythm is working.
A Simple Test
If you're unsure whether you have too many OKRs, ask your team to list them from memory. If they can't, you likely have too many, regardless of what the recommended range says. The right number is the number your team can actually keep in their head and act on.