The ideal number is 3 to 5 objectives, each with 3 to 5 key results. This gives your team enough scope to make meaningful progress while maintaining the focus needed to actually achieve results. Most teams perform best with 3 objectives and 3 to 4 key results each, totaling around 9 to 12 key results per quarter.
This guide explains why these numbers work, how to adapt them to your situation, and how to avoid the common mistake of setting too many OKRs.
The Short Answer
John Doerr, who brought OKRs to Google and wrote the definitive book on the framework, recommends 3 to 5 objectives per cycle. Google’s internal guidance suggests the same range. Research on cognitive load and organizational focus supports this limit.
For key results, the standard recommendation is 3 to 5 per objective. Fewer than 3 may not fully capture what success looks like. More than 5 suggests your objective is too broad and should be split.
Here is the math:
| Objectives | Key Results Each | Total Key Results |
|---|---|---|
| 3 | 3 | 9 |
| 3 | 5 | 15 |
| 5 | 3 | 15 |
| 5 | 5 | 25 |
Most successful teams land between 9 and 15 total key results per quarter. Going beyond 20 usually signals a focus problem.
Why Less Is More with OKRs
Setting fewer OKRs feels risky. Leaders worry they will miss something important or limit their team’s potential. But the evidence points the other way. Fewer OKRs consistently outperform longer lists.
Cognitive Load Has Real Limits
Psychologist George Miller found that humans can hold about 7 items in working memory at once, plus or minus 2. When you give a team 8 objectives with 5 key results each, you have created 40 things to track. No one can keep that straight.
Teams with fewer OKRs can actually remember their goals. They can recite them in meetings, refer to them when making decisions, and stay aligned without constantly checking a document.
Focus Multiplies Impact
When everything is a priority, nothing is. A team trying to achieve 10 objectives will make incremental progress on many fronts but breakthrough progress on none.
The same team focused on 3 objectives can concentrate resources, align effort, and push through obstacles. They finish quarters with real accomplishments instead of a list of partial progress.
Decision Fatigue Is Real
Every objective you add creates more decisions. Which one matters most today? Where should this person spend their time? How do we handle a conflict between priorities?
Fewer OKRs means fewer daily decisions about what matters. The team already knows. They can spend their mental energy on execution instead of prioritization.
The Paradox of Choice
Research by psychologist Barry Schwartz shows that more options often lead to worse decisions and less satisfaction. This applies to goals too. Teams with too many OKRs struggle to commit fully to any of them. Teams with focused OKRs can go all in.
Breaking Down the Numbers
Why 3 to 5 Objectives?
Three objectives is often the sweet spot. It provides enough breadth to cover different aspects of your work without fragmenting focus. Consider what happens at different counts:
1 objective: May work for highly focused teams or individuals, but often too narrow for a full team’s quarterly scope.
2 objectives: Works well for smaller teams or those in execution mode on a single initiative.
3 objectives: The most common recommendation. Covers enough ground while maintaining focus.
4 objectives: Reasonable for larger teams or those with genuinely distinct workstreams.
5 objectives: The upper limit. Beyond this, focus typically breaks down.
If you consistently need more than 5 objectives, your objectives may be too narrow. Consider combining related ones into broader themes.
Why 3 to 5 Key Results per Objective?
Key results answer the question: “How will we know we achieved this objective?” You need enough to fully capture success, but not so many that you lose focus.
1 to 2 key results: May not fully represent what success looks like. You might achieve the key results but miss the spirit of the objective.
3 to 4 key results: The ideal range for most objectives. Captures the important dimensions of success.
5 key results: The maximum. If you need more, your objective is probably too broad.
6+ key results: Almost always a sign to split the objective into two.
Total Key Results: The Real Constraint
While the 3 to 5 / 3 to 5 framework is helpful, the total number of key results is what really matters for team capacity.
9 to 12 total key results: Ideal for most teams. Manageable load with clear focus.
13 to 18 total key results: Workable for experienced teams with strong OKR discipline.
19 to 25 total key results: Approaching overload. Requires careful prioritization.
25+ total key results: Almost certainly too many. Teams at this level rarely achieve meaningful progress on any single key result.
Factors That Affect Your Count
The 3 to 5 guideline works for most teams, but your specific situation matters. Consider these factors when setting your number:
Team Size
Smaller teams should have fewer OKRs. A 3-person team cannot execute as many initiatives as a 15-person team. Scale your ambition to your capacity.
| Team Size | Recommended Objectives | Total Key Results |
| 1-3 people | 1-2 | 3-6 |
| 4-7 people | 2-3 | 6-12 |
| 8-15 people | 3-4 | 9-15 |
| 16+ people | 3-5 | 12-20 |
OKR Maturity
Teams new to OKRs should start with fewer objectives. The framework takes practice. Start with 2 objectives your first quarter, then expand as you build the muscle.
Experienced OKR teams can handle slightly more complexity because they have systems for tracking, discussing, and adjusting their goals.
Strategic Complexity
Some teams have genuinely diverse responsibilities that require broader OKR coverage. A product team managing multiple product lines may need more objectives than a team focused on a single product.
However, complexity is often an excuse for poor prioritization. Challenge yourself to focus even when the work feels broad.
Cycle Length
Most teams run quarterly OKRs. If you use a different cadence, adjust accordingly:
Monthly OKRs: 1 to 2 objectives maximum. Not enough time for more.
Quarterly OKRs: 3 to 5 objectives. The standard recommendation.
Annual OKRs: Can support more objectives, but consider breaking them into quarterly milestones.
Resource Constraints
Teams with limited resources need fewer OKRs. If you have a small budget, competing demands on team time, or dependencies on other teams, reduce your objectives to what you can realistically control and complete.
Company vs. Team OKRs
One common mistake is copying company OKRs down to teams verbatim. This creates duplication and misses the point of cascading goals.
How Cascading Should Work
Company OKRs set direction for the entire organization. Team OKRs describe how each team will contribute to that direction. The relationship is supportive, not identical.
Example:
Company Objective: Become the market leader in customer satisfaction
- Marketing Team Objective: Build a brand reputation for exceptional customer care
- Product Team Objective: Deliver a product experience that delights users
- Support Team Objective: Resolve customer issues faster than any competitor
Each team has its own objective that supports the company goal. None simply copied the company OKR.
Alignment Without Duplication
Team OKRs should clearly connect to company priorities, but they should be written in the team’s own language and focused on what that team can control.
Ask: “If our team achieves this objective, how does it help the company achieve its objectives?” If the connection is unclear, reconsider the team OKR.
Avoid OKR Multiplication
When company OKRs cascade to teams without discipline, the total number explodes. If a company has 5 objectives and 6 teams each create 3 objectives to support them, you suddenly have 18 team objectives competing for attention.
Coordinate across teams. Not every team needs to support every company objective. Focus each team on the company priorities where they can have the greatest impact.
Common Mistakes to Avoid
Setting Too Many Objectives
This is the most frequent error. Leaders want to capture everything important, so they add more objectives. The result is a team that cannot focus on anything.
Fix: Force-rank your potential objectives. Choose the top 3. Everything else goes on a “not now” list.
Treating Key Results as Tasks
Key results should measure outcomes, not activities. “Launch new feature” is a task. “Achieve 30% adoption of new feature” is a key result.
When key results are tasks, teams often add too many because they are listing their to-do items instead of defining success.
Fix: For each key result, ask: “Is this something we do, or something that happens as a result of what we do?”
No Prioritization Within OKRs
Even with 3 objectives, some will matter more than others. Teams often treat all OKRs as equally important, leading to scattered effort.
Fix: Stack-rank your objectives. Know which one you would protect if you had to cut the others.
Skipping Regular Check-ins
OKRs only work if teams review them regularly. Without check-ins, OKRs become documents that get written at the start of the quarter and forgotten.
Fix: Schedule weekly or biweekly OKR check-ins. Review progress, identify blockers, and adjust tactics.
Changing OKRs Mid-Cycle
Some teams revise their OKRs frequently, adding new ones as priorities shift. This defeats the purpose of the framework.
Fix: Commit to your OKRs for the full cycle. If something truly urgent arises, explicitly trade it for an existing OKR rather than adding to the list.
How to Prioritize When Everything Feels Important
Narrowing to 3 to 5 objectives is hard. Use these techniques to make ruthless prioritization easier:
The “One Thing” Test
Ask: “If we could only accomplish one objective this quarter, which would it be?” That is your top priority. Repeat for second and third place.
Impact vs. Effort Matrix
Plot potential objectives on a 2×2 grid: high impact vs. low impact, high effort vs. low effort. Prioritize high-impact objectives regardless of effort. Deprioritize low-impact objectives regardless of how easy they seem.
Stack Ranking
List all potential objectives and force-rank them from 1 to N. No ties allowed. Draw a line after your top 3 to 5. Everything below the line waits for a future quarter.
The CEO Test
Ask: “If our CEO asked what we are focused on this quarter, could I explain it in under 30 seconds?” If you need several minutes to list all your objectives, you have too many.
Signs You Have Too Many OKRs
Watch for these warning signs:
- Team members cannot recall all objectives without checking a document
- Weekly updates mention different objectives each time
- Progress is incremental across many fronts but significant on none
- Team feels busy but not productive
- OKR review meetings run long because there is too much to cover
- Key results frequently get marked “no progress” because attention went elsewhere
Signs You Have Too Few OKRs
These signals suggest you might add another objective:
- Team finishes key results early and has unused capacity
- Important work is happening that does not connect to any OKR
- Objectives feel too narrow to represent the team’s full scope
- Team members wonder why certain priorities are excluded
Having too few OKRs is rare. When in doubt, err on the side of fewer.
Find Your Team’s Right Number
The 3 to 5 objectives guideline works for most teams, but the right number for your team depends on your size, maturity, and context. Start with 3 objectives if you are unsure. You can always add complexity in future quarters, but you cannot recover focus once it is lost.
The goal is not to have the perfect number of OKRs. The goal is to achieve meaningful results. Fewer, focused OKRs are the most reliable path to get there.
ScaleUpExec‘s fractional COOs bring hands-on experience implementing OKRs across numerous organizations. Reach out today to learn how we can help you build the operational foundation for your next phase of growth.
