Managing ten or more direct reports creates a practical challenge. If you schedule a 60-minute weekly one-on-one with every employee, your calendar can quickly fill with ten or more hours of meetings before you even account for preparation, follow-up, team meetings, project work, and your own responsibilities.
That pressure often leads managers to make predictable compromises. They may cancel meetings with quieter employees, shorten every conversation, move everyone to a monthly schedule, or make one-on-ones faster and more transactional. While these changes can save time, they do not necessarily solve the underlying problem.
The real goal is to scale the one-on-one system without making employee relationships shallow. Managers need a structure that protects meaningful access, feedback, development, and support while still keeping the overall meeting load manageable.
Why One-on-Ones Become Harder at Scale
As your number of direct reports grows, several pressures increase.
- Calendar pressure: More employees create more recurring meetings.
- Preparation: You need context for each person's work, goals, challenges, and previous commitments.
- Follow-up: Every conversation can lead to action.
- Meeting fatigue: You may have several one-on-one meetings in a single day.
- Unequal attention: Employees with urgent problems can consume more time, while quiet or high-performing employees receive less.
Scaling one-on-ones, therefore, requires deliberate design.
First, Ask Whether 10+ Direct Reports Is Sustainable
Before optimizing the calendar, ask whether the management structure itself makes sense.
Ten direct reports can be manageable when:
- Employees are senior.
- Roles are stable.
- Employees work independently.
- The manager's responsibilities are primarily people leadership.
It can be much harder when:
- Employees are junior.
- Work changes quickly.
- Frequent coaching is required.
- The manager is also a heavy individual contributor.
- The team spans very different functions.
If your one-on-ones constantly disappear because you cannot support the number of people reporting to you, the problem may not be scheduling. It may be a span of control.
Not Everyone Needs the Same Cadence
Fair management does not require identical meeting frequency. Employees have different needs.
Weekly
May be appropriate for:
- New employees.
- People in major transitions.
- Employees who currently need close support.
- Roles with rapidly changing priorities.
Biweekly
May work for:
- Established employees.
- Stable responsibilities.
- Independent contributors.
Less frequent, deeper conversations
May sometimes work for highly senior employees who have strong access to the manager through other channels.
Do not reduce frequency based on who complains least. Use employee needs.
FirstHR's guide to one-on-one meetings also emphasizes that managers should adapt meeting cadence to each employee's role, experience, and current needs rather than use the same schedule for everyone. It recommends regular weekly or biweekly conversations where employees have meaningful influence over the agenda, managers focus on blockers and support, and both sides leave with clear action items. For managers leading larger teams, this approach helps maintain useful one-on-ones without making every meeting identical.
Standardize the Framework, Personalize the Conversation
A common meeting structure saves preparation time.
For example:
- Employee topics.
- Current challenges.
- Feedback.
- Development.
- Follow-ups.
The structure can remain the same across the team. The conversation should not. A new hire may need role clarity. A high performer may need career opportunities. Someone struggling may need clear expectations and follow-up. Standardize the container, not the content.
Shorter Doesn't Automatically Mean Worse
A useful 30-minute one-on-one can be better than an unfocused 60-minute meeting.
Shorter meetings work when:
- The employee is prepared.
- The agenda is focused.
- Routine updates happen elsewhere.
- Important topics receive enough time.
Do not shorten meetings simply to fit more into your calendar if employees consistently need deeper conversations. The meeting length should reflect the work being done inside it.
Move Status Updates Out of One-on-Ones
This becomes especially important when you manage 10 or more people.
If every employee spends 15 minutes telling you:
- What do they finish?
- What is in progress?
- What is due next?
You may spend several hours each week collecting information that could have been written down.
Use:
- Project tools.
- Dashboards.
- Weekly written updates.
- Team meetings.
Then use the one-on-one for:
- Blockers.
- Feedback.
- Decisions.
- Workload.
- Development.
- Manager support.
Use a Shared Agenda
A shared agenda reduces preparation time for both people.
Simple sections can include:
- Employee topics: Anything they want to raise.
- Manager topics: Feedback, priorities, or questions you need to discuss.
- Follow-ups: Commitments from previous meetings.
- Development: Longer-term goals and growth.
The agenda should help both people arrive ready.
Keep a Simple Note-Taking System
When managing many people, memory becomes unreliable.
Track:
- Commitments.
- Development goals.
- Important feedback.
- Decisions.
- Follow-up dates.
Avoid over-documenting personal conversations.
The purpose is continuity, not surveillance.
Don't Cancel the Quiet Employees First
This is one of the biggest risks at scale.
When your calendar becomes crowded, you may think:
"Jamie is doing fine. I'll cancel that one."
Meanwhile, the employee with constant problems keeps every meeting.
Over time, reliable employees can become the least managed people on the team.
That can create:
- Lack of recognition.
- Missed development.
- Retention risk.
- Poor visibility into emerging concerns.
High performance reduces the need for supervision. It does not remove the need for management.
Batch Preparation, Not Conversations
You can reduce overhead by reviewing several one-on-one agendas together before a meeting block.
For example, spend 20 minutes reviewing:
- Outstanding commitments.
- Recent feedback.
- Agenda items.
- Important updates.
Then, enter each conversation prepared.
What you should not batch is the actual relationship.
Avoid treating every employee the same way with the same questions and advice simply because the meetings happen back-to-back.
Use Office Hours for Small Questions
If employees frequently save minor operational questions for one-on-ones, consider adding another access mechanism.
For example:
- Manager's office hours.
- Shared decision channels.
- Short team Q&A sessions.
This can reduce pressure on individual meetings without removing them.
Know When You Need Another Management Layer
There is a point at which efficiency improvements no longer solve the problem.
Warning signs include:
- You repeatedly cancel one-on-ones.
- Employees cannot get timely decisions.
- Feedback arrives too late.
- You do not remember important commitments.
- Development discussions disappear.
- Every decision flows through you.
- You have no time for strategic work.
- Employees wait too long for coaching.
At that point, consider whether the team needs:
- Team leads.
- Another manager.
- Clearer delegation.
- A different reporting structure.
Adding a management layer is not automatically bureaucracy.
Sometimes it is what allows employees to receive actual management.
Example Schedule for 10+ Direct Reports
One possible structure could be:
- Monday: Three 30-minute one-on-ones.
- Tuesday: Two one-on-ones plus teamwork.
- Wednesday: No recurring one-on-ones. Keep space for strategy and deep work.
- Thursday: Three one-on-ones.
- Friday: Two one-on-ones plus follow-up and preparation.
This is only an example. You could also split the team across alternating weeks, depending on employee needs. The important thing is protecting enough capacity that the meetings actually happen.
Managing 10 or more people makes one-on-one meetings more difficult, but the solution is not to reduce every conversation to a 15-minute status check. Managers should scale deliberately by adjusting meeting cadences where appropriate, moving routine reporting to other channels, using a consistent agenda, and keeping simple notes to maintain continuity.
It is also important to make sure quiet employees and high performers are not overlooked simply because they require less day-to-day attention. They still need feedback, recognition, development opportunities, and access to their manager. At the same time, managers should recognize when the number of direct reports has become so large that it is affecting the quality of support they can provide.
The goal is not to fit as many one-on-one meetings as possible into the calendar. It is to make sure every employee still has meaningful access to the manager responsible for supporting their work, development, and long-term success.