One of the most common structural problems in growing companies is not visible on the organization chart at first glance. A manager may have too many direct reports, too few direct reports or the wrong combination of responsibilities. Over time, this affects decision speed, employee development, management workload and the ability of the company to scale.
A founder who once managed five employees may eventually find twelve, fifteen or even twenty people reporting directly to them. Meetings multiply, approvals are delayed and managers spend most of their week responding to operational questions. In another company, the opposite problem may exist: too many management layers, small teams and expensive supervisory structures.
The concept used to analyze this issue is called Span of Control in Management. It describes the number of employees who report directly to a manager and therefore require some level of supervision, coaching, coordination and performance management.
There is no universal number that works for every organization. The ideal span depends on the complexity of work, experience of employees, degree of standardization, decision authority, management capability and the amount of collaboration required.
This guide explains how companies can evaluate management span, recognize the signs of an overloaded organizational structure and determine whether they need wider spans, narrower spans or a redesign of roles and processes.
آنچه خواهید خواند:
The Key Question Is Not “What Is the Perfect Number?”
The better question is: how many people can this manager effectively support while maintaining decision quality, coaching, accountability and strategic focus? The answer depends on the nature of the work, not simply the size of the company.
What Is Span of Control in Management?
Span of control refers to the number of people who report directly to one manager. If a sales director has eight sales managers reporting directly to them, the director’s span of control is eight. If a CEO has twelve functional leaders reporting directly to them, the CEO’s span is twelve.
The concept matters because every direct report creates management work. Managers need to review performance, resolve exceptions, make decisions, provide coaching, coordinate priorities and communicate changes.
As the number of direct reports increases, managers must either become more efficient, delegate more authority or reduce the amount of individual attention provided to each person.
This is why span of control is closely connected with organizational design. A company cannot decide how many management layers it needs without also deciding how many people each manager can realistically manage.
Wide Span vs. Narrow Span of Control
Organizations generally operate somewhere between two structural approaches: wider spans with fewer management layers and narrower spans with more management layers.
| Wide Span | Narrow Span |
|---|---|
| More direct reports per manager | Fewer direct reports per manager |
| Fewer management layers | More management layers |
| Greater employee autonomy may be required | More individual management attention is possible |
| Can reduce organizational cost | Can increase management cost |
| May improve communication speed | May improve coaching and supervision |
| Risk of manager overload | Risk of bureaucracy and excessive supervision |
Why Span of Control Matters for Growing Companies
Span of control is particularly important during periods of growth because organizational complexity often increases faster than the management structure.
A founder may continue to manage department heads, senior specialists, important customers and several operational issues directly. This structure may have worked when the company was smaller, but it becomes difficult to maintain as the business expands.
When a manager has too many direct reports, coaching becomes irregular, performance problems are discovered late and routine decisions move upward because managers have insufficient time to clarify expectations.
When spans are unnecessarily narrow, the opposite happens. Too many management layers can slow communication, increase cost and create positions that primarily transfer information rather than improve decisions.
Is Your Management Structure Slowing Down Growth?
Review reporting lines, management workload and decision authority before adding another management layer.
Iran: 09123411029
Oman: 0096891151085
How Many Direct Reports Should a Manager Have?
There is no single ideal number of direct reports. A manager overseeing standardized, repetitive work may successfully manage a relatively large team. A leader managing complex expert work, major customer relationships or rapidly changing projects may need a smaller span.
This means companies should avoid selecting a number first and then forcing the organization to fit it. Instead, they should evaluate the management workload created by each role.
Six Factors That Determine the Right Span
- Complexity and variability of the work
- Experience and independence of team members
- Clarity of processes and performance standards
- Amount of coordination required between roles
- Number of decisions requiring manager involvement
- Amount of coaching and development the employees require
1. Work Complexity
Highly standardized work usually supports a wider span because employees encounter similar situations and can follow established procedures.
Complex knowledge work is different. Consultants, engineers, senior salespeople or project leaders may frequently face situations requiring judgment, coordination or coaching.
A manager responsible for several complex functions may therefore become overloaded with fewer direct reports than a manager responsible for a larger standardized operational team.
2. Employee Experience and Independence
Experienced employees generally require less frequent supervision. They understand expectations, can solve routine problems independently and know when an issue genuinely requires escalation.
New employees or employees in changing roles may require more coaching, feedback and clarification.
This means the same team can require a different span over time. A manager may initially need a narrower span while building capability and later manage a larger team once processes and skills improve.
3. Process Standardization
Clear processes reduce management workload because employees know how routine situations should be handled.
When every employee uses a different method and every exception becomes a management discussion, even a relatively small team can consume substantial management time.
Companies that want wider management spans should therefore invest in clear processes, operating standards and decision rules. The broader principles of aligning processes, roles and decision authority are also discussed in
Business Operating Model Design
.
4. Decision Authority
A manager may appear to have an acceptable number of employees but still become overloaded because too many decisions require their approval.
For example, if salespeople need approval for every discount, operations managers need approval for every supplier change and HR needs approval for each recruitment decision, management capacity quickly becomes the bottleneck.
Clear decision rights can allow the same manager to support a wider span without reducing control. The manager focuses on exceptions and important decisions rather than routine approvals.
5. Coordination Requirements
Some teams can work independently. Others depend heavily on multiple departments, customers and external partners.
The greater the coordination requirement, the more management time each direct report may require. A manager overseeing six cross-functional project leaders may face greater complexity than a manager supervising twelve employees performing similar work.
Organizational design should therefore examine the quality of relationships between roles rather than simply counting boxes on the organization chart.
6. Coaching Requirements
Managers do more than review output. They develop people, provide feedback, resolve conflict and prepare employees for greater responsibility.
If a role requires substantial people development, a very wide span may reduce management quality even if daily operational work remains under control.
This factor is especially important for first-line managers, where employee development and performance conversations may represent a significant part of the role.
A Practical Span-of-Control Test
Signs That a Manager Has Too Many Direct Reports
- One-to-one meetings are frequently cancelled.
- Managers spend most of their week responding to urgent questions.
- Performance problems are discovered late.
- Employees receive inconsistent feedback.
- Important decisions wait for manager availability.
- Managers regularly work outside normal hours to complete administrative tasks.
- Strategic and improvement projects are repeatedly postponed.
- Employees escalate routine issues instead of solving them independently.
- The manager becomes a communication channel between team members who could communicate directly.
Signs That Span of Control May Be Too Narrow
An overloaded manager is easy to recognize, but narrow spans also create problems.
If managers supervise only a very small number of employees while those employees perform predictable work independently, the organization may have unnecessary management layers.
- Managers spend significant time forwarding information between levels.
- Employees need several levels of approval for simple decisions.
- Job titles increase faster than business complexity.
- Communication becomes distorted as it moves through layers.
- Management cost increases without a clear improvement in performance.
- Employees feel excessively supervised despite being experienced and capable.
Design the Right Management Structure for the Next Stage of Growth
Review management layers, direct reports, decision rights and workload before changing the organization chart.
Iran: 09123411029
Oman: 0096891151085
Span of Control at the CEO Level
CEO span deserves particular attention because the CEO’s time is one of the most limited resources in the organization.
A CEO may have finance, sales, marketing, HR, operations, technology, legal and several business-unit leaders reporting directly. In founder-led companies, additional specialists or long-term employees may also report directly to the founder because the relationship existed before the company grew.
The result can be a structure in which twenty people technically report to the CEO but only a small number receive meaningful management attention.
A CEO structure should group responsibilities logically and determine which leaders genuinely require direct access to the chief executive. This reduces unnecessary escalation and creates clearer accountability.
Do Not Add a Manager Just Because a Team Became Larger
Companies sometimes respond to team growth by automatically adding another management layer. This may solve workload temporarily, but it can also introduce unnecessary complexity.
Before adding a manager, leadership should determine what problem the new role is expected to solve. Is the current manager overloaded because the team is larger, or because processes are unclear? Does the team need more coaching, or are too many routine decisions being escalated?
If the real problem is unclear processes or authority, adding another manager may simply create another approval layer.
Organizational structure should follow the work required, not automatically follow employee count.
When Should You Add a New Management Layer?
A new management layer may be justified when the existing manager can no longer provide effective direction and the organization has a meaningful group of responsibilities that can be managed together.
| Situation | Likely Response |
|---|---|
| Large team with standardized work | Consider process improvements before adding a layer |
| Large team requiring frequent coaching | A narrower span may be justified |
| Many different functions report to one executive | Consider grouping related functions under a leader |
| Manager overloaded with approvals | Clarify decision authority before adding managers |
| Managers spend most time transferring information | Reduce layers or redesign reporting |
Span of Control and Management Meetings
Management span directly affects meeting load. A manager with many direct reports may spend a large percentage of the week in individual meetings and status reviews.
One solution is not simply to cancel meetings. Organizations should distinguish between information sharing, decision-making, coaching and performance review.
Routine status information can often be handled through dashboards or team reviews. Individual meetings can then focus on decisions, development and exceptions.
A structured
Management Operating Rhythm
can help organizations define which discussions belong in weekly, monthly and quarterly meetings.
Span of Control and Management Control Systems
A wider span is easier to manage when performance information is clear. Managers do not need to ask each employee for constant updates if objectives, KPIs and exception thresholds are visible.
Management control systems therefore influence organizational structure. Better reporting, accountability and escalation rules can allow companies to reduce unnecessary supervision.
The objective is not to maximize the number of direct reports. It is to reduce management activity that does not add value so leaders can spend more time on decisions, development and improvement.
How Technology Changes Span of Control
Technology can increase management capacity by making information easier to access and reducing administrative coordination.
Dashboards can eliminate manual status requests. Workflow systems can route routine approvals automatically. Collaboration tools can improve communication without requiring the manager to act as an intermediary.
However, technology does not automatically justify wider spans. If employees still require complex judgment, coaching or conflict resolution, managerial workload remains significant.
The most effective use of technology is to remove administrative management work while preserving human attention where leadership genuinely adds value.
Common Span-of-Control Mistakes
- Using one target number for every department: work complexity differs significantly between functions.
- Adding managers before fixing decision rights: an approval problem can become a larger hierarchy problem.
- Ignoring employee maturity: experienced teams may need less supervision.
- Counting people but not complexity: six highly diverse roles may require more management than twelve similar roles.
- Keeping historical reporting lines: employees may report directly to the founder simply because they always have.
- Creating managerial titles without real accountability: hierarchy increases while decision authority remains centralized.
- Changing the organization chart without redesigning processes: structural change alone may not reduce management workload.
A 90-Day Span-of-Control Review
Companies do not need to reorganize immediately. A 90-day review can provide enough evidence to determine where structural changes are necessary.
Days 1–30: Map
List every manager, their direct reports, major responsibilities, meeting load and recurring decisions.
Days 31–60: Diagnose
Identify overloaded managers, unnecessary layers, unclear decision rights and roles requiring excessive supervision.
Days 61–90: Redesign
Adjust reporting lines, clarify decision authority, improve processes and test whether management workload decreases.
Questions to Ask During a Span-of-Control Review
- How many people report directly to each manager?
- How different are the roles managed by that person?
- How much coaching do employees require?
- How many routine decisions require managerial approval?
- How much time does the manager spend in recurring meetings?
- Are performance expectations visible without individual status requests?
- Is the manager still able to improve the business rather than only manage daily operations?
- Could a management layer be removed without reducing decision quality?
- Would adding a layer solve a real management problem or simply redistribute administrative work?
The Role of a Business Consultant in Organizational Structure Design
Reporting structures often develop historically rather than intentionally. Employees report to the same manager because they did so when the company had ten people, even though the organization may now have one hundred employees.
This makes structure difficult to evaluate internally because existing roles and relationships can influence the discussion.
A business consultant can review management workload, reporting lines, decision authority, management layers and cross-functional dependencies. The objective is to determine whether structural complexity supports the business or simply reflects historical growth.
For organizations that need a broader review of strategy, structure and performance, professional
Business Consulting
can connect organizational design decisions with the company’s growth priorities.
Build a Management Structure That Can Scale With Your Business
Clarify reporting lines, reduce management bottlenecks and create the right balance between autonomy, accountability and supervision.
Iran: 09123411029
Oman: 0096891151085
Final Thoughts: The Right Span Creates Both Control and Autonomy
Span of control is not simply an organizational-chart calculation. It reflects the amount of management attention required to keep people aligned, capable and accountable.
A span that is too wide can overload managers, weaken coaching and turn executives into bottlenecks. A span that is too narrow can increase management cost, create bureaucracy and slow communication.
The correct structure depends on the work. Companies should consider complexity, employee experience, process quality, decision authority, coordination and management capability before changing reporting lines.
The goal is not to maximize or minimize the number of direct reports. The goal is to create a structure where managers can focus on the work that genuinely requires management while employees have enough clarity and authority to perform effectively without unnecessary supervision.