span of control
Also called: span of management, number of direct reports
The number of people who report directly to one manager. There is no single right number: it depends on how similar the work is, how experienced the people are and how much time the manager has for one-to-ones.
Span of control is the number of people who report directly to one manager. A wide span means a flatter organization with fewer managers; a narrow one means more layers. Real teams range from two or three direct reports to well over fifteen, and there is no research-backed single ideal number.
What matters is the time each person needs from their lead. That depends on how similar the work is (one kind of task or many), how experienced the people are, how much of the lead's own week goes to hands-on work, how spread the team is across places and time zones, and how much is already settled in writing. Ten experienced people doing similar work can need less of a lead than four people where two are new. A useful way to size a span is a time budget: add up what each person needs each week (one-to-ones, reviewing work, coaching, onboarding) and compare it with the hours the lead actually has for it.
Too wide a span shows up as cancelled one-to-ones, decisions queuing at the lead and new people stuck for days. Too narrow shows up as close supervision of people who don't need it and a lead who fills the gap by doing the work. The fix for a wide span isn't always another manager: a senior person who onboards newcomers, clearer decision rights and better written guidance all reduce the time each person needs.
Example
Klasna's Support lead plans a target 40-hour week with 6 hours for one-to-ones and team meetings. Assume, for the sake of the sum, a 45-minute weekly one-to-one with each person, a 1-hour team call, and an extra 1.5 hours a week for each new person in their first weeks (pairing and reviewing replies).
Six reports felt like a lot in the spring not because six is a bad number but because two of them were new: Dmytro and Sofiia were planned at 25 tickets in their first week, against 55 once up to speed. The ways out were in the budget, not in the headcount: Bohdan and Olha paired with the newcomers, and the January one-to-ones of the experienced coordinators could move to every other week for the peak.
Common mistakes
- Looking for a magic number. The right span depends on the work and the people, not on a rule of thumb.
- Counting heads instead of hours. Two new people can need more time than four experienced ones.
- Forgetting the lead's own hands-on work. Hours spent on your own tickets come out of the same week.
- Widening the span by cancelling one-to-ones. The time problem stays and moves to where you can't see it.
- Adding a manager as the only fix. Senior buddies, written guidance and clear decision rights also cut the time people need.
Learn it in the course
- Structuring a small team · Choose between a split by subject, by channel or a shared pool, give each area an owner and a backup, and make hand-offs and two-boss setups work.