Span of Control
Span of Control
What Is Span of Control?
- The number of direct reports a single manager oversees
- The right team size varies with the type of work and skill level
- As the span widens, development and feedback break down first
Once you actually count the span of control, the language of the organizational discussion changes. The judgment 'that team lead neglects people management' becomes the fact that 'that team lead has 16 direct reports and hands-on work on top.' The remedy shifts from leadership training to splitting teams or reallocating headcount. The habit of checking the numbers first stops the blame on individuals and brings reorganization, hiring plans, and evaluation design to the same table. Keep in mind, though, that span of control and the number of layers are linked variables: narrowing one widens the other, so you need to calculate both together.
The right number depends on the nature of the work. A production line or call center, where tasks are standardized and results are immediately visible, can run with one manager overseeing 15–20 people. But in teams like planning or development, where every output is different and judgment is involved, once you go past 6–8 people, the quality of feedback is the first thing to suffer. If the manager also does hands-on work, the bar drops even lower, so for a team lead who spends more than half their time on hands-on work, about 5 people is realistically the limit.
You also need to decide how to count. Counting only direct reports on the org chart misses the real burden. The true number is the “effective headcount managed,” which adds TF concurrent staff, dispatched and contract workers, and people from other departments on dotted-line reporting. Reporting lines and span of control are separate layers. Approvals can still go through the team leader while evaluation and development are handled by a part leader, and in that case the felt burden changes dramatically even with the same headcount. Whether authority was handed over along with the work is the test of whether the separation is real.
The most common mistake in practice is a reorganization that only fixes the numbers. If you appoint several part leads to lighten the team lead’s load but the team lead keeps authority over evaluations, leave approval, and interviews, you add one layer while decisions still pile up on the team lead. Decision-making slows because of the extra reporting step, yet the one-on-one rate stays flat for months on end. Conversely, if you make a 'flat organization' the goal itself and merge teams, one team lead ends up handling three completely different kinds of work at once, and new-hire training is the first thing to disappear.
Ara LimExpert in global leadership, AI, and business communication
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum ConsultingIn 1933, V.A. Graicunas showed mathematically that the number of relationships a manager must handle rises sharply as the number of direct reports grows. Lyndall Urwick and others then proposed an ideal span, making it a core concept of classical management theory. A contingency view later took hold: the right number depends on the nature of the work.
Let’s look at a hypothetical case. Company A, which makes and sells industrial valves (210 employees, KRW 48 billion (≈ US$35,912,000) in annual revenue), was six weeks away from a Q3 reorganization. While the head of Domestic Sales Team 1 managed 16 direct reports, the monthly one-on-one completion rate fell to 31%, and over the past year 5 sales reps left within their first 6 months. Among the executives, the first suggestion was 'let’s run leadership training for team leads again.'
- When the head of HR recounted using payroll records and approval lines instead of the org chart, Sales Team 1’s leader had 16 direct reports, and 19 once task force assignments were included. The comment “Even one meeting per quarter is a stretch” went straight into the meeting minutes.
- An HR manager tracked the weekly schedules of 8 team leads for 2 weeks. Hands-on work took an average of 62% of their time, leaving only about 15 hours a week for management. Holding a 30-minute meeting with each of 16 people, prep included, used up all of that time.
- Sales Team 1 was split into two parts, since its work divided into dealer management and new-business development. Conversely, two technical support teams of 3–4 people each were merged into one, removing a layer of hierarchy.
- The CEO gave the two newly created part leads first-round evaluation authority and leave approval together, stating firmly, "If we give them only the title, the work just comes back to the team lead’s desk." Part lead compensation was also set with a position allowance of KRW 200,000 (≈ US$150) per month.
- Four months after the restructuring, the average number of direct reports per team leader fell from 11.4 to 7.2, and the rate of monthly one-on-ones rose from 31% to 84%. Sales attrition within six months dropped from 5 people to 1.