A team should set 1 to 3 Objectives per quarter, each with 2 to 4 Key Results. At company level, 3 to 5 Objectives is the upper limit. That is usually all a team can move in one quarter while keeping the work visible and the check-ins short.
Why fewer OKRs work better
OKRs exist to create focus. Every extra Objective splits attention, budget and meeting time. With too many OKRs:
- Priorities blur and nobody knows what matters most this quarter.
- Resources spread thin, so many goals move a little instead of a few moving a lot.
- Weekly check-ins turn into status reports instead of decisions.
The limit is a feature. It forces the conversation about what the team will not do this quarter.
Recommended numbers by level
- Company level: 3 to 5 Objectives, set by the leadership team.
- Team level: 1 to 3 Objectives per quarter, each with 2 to 4 Key Results.
- Individuals: none. Wave Nine does not recommend individual OKRs. People contribute through the actions they own under their team's Key Results.
Teams do not need an OKR for every company Objective. They localize the company OKRs: they pick the one or two Objectives where they can make the biggest contribution and write their own OKRs for those.
How many Key Results per Objective?
Two to four. Fewer than two usually means the Objective is not measured from enough angles. More than four usually means the Objective is too broad and should be split, or that some Key Results are really actions.
Each Key Result should measure an outcome, such as a change in customer behavior or a business result, not an activity. "Hold 3 client calls" is an action. "Raise client satisfaction from 72% to 80%" is a Key Result.
Example of a healthy volume
The company has three Objectives for the quarter. The product team supports one of them:
- Objective: Make onboarding effortless for new customers
- KR1: Increase activation rate from 35% to 50%
- KR2: Reduce time to first value from 7 days to 3 days
- KR3: Raise onboarding satisfaction from 7.2 to 8.5
The marketing team supports a different company Objective with one or two OKRs of its own. Each team stays focused and accountable without stretching too thin.
How to trim a long list
- Strategic fit: Which candidates directly support the company's top priorities this quarter?
- Impact versus effort: Which ones create the most impact for the effort required?
- Capacity: Does the team have the people and time to move this alongside its daily work?
- Overlap: Does another team already own this outcome? Then share it or drop it.
Candidates that do not make the cut can become actions under another Key Result, stay on a KPI dashboard, or wait for next quarter.
When you are just starting
In the first OKR cycle, be even stricter. Start with one or two company Objectives and one Objective per pilot team. Teams learn the process and get an early win before the program grows.
When a team asks for more
Large or cross-functional teams sometimes argue for four or five Objectives. Before agreeing, check whether each one is truly critical this quarter, fully resourced, and distinct from the others. Merging two related Objectives is usually the better answer.
Want help applying this in your organization? Book a free strategy session.
Write Goals That Drive Results.
Book a free strategy session and we'll show you how to get your teams writing high-quality, outcome-focused OKRs.
