Fixing the manager span of control in growth stage companies

The hidden cost of accidental org design

When a company grows from 50 to 500 people, the organizational structure usually evolves through necessity rather than intent. A founder hires a head of sales, who hires three managers, who each hire six account executives. This works until it doesn't. Most workforce planning cycles focus on budget: how many people can we afford and when should they start. This is a mistake. The real work of planning happens at the structural level. If you add 20 engineers to a department with a poor manager-to-contributor ratio, you will decrease velocity instead of increasing it.

At Recruidos, we see two recurring problems in mid-market companies: the management bottleneck and the hollow middle. The management bottleneck occurs when a leader has more than eight direct reports, leading to delayed decisions and missed one-on-ones. The hollow middle occurs when managers have only two or three reports, creating unnecessary layers of hierarchy that slow down information flow. Before you open a single requisition for the next quarter, you must audit your span of control.

Auditing your current span of control

Start by exporting your current staff list into a spreadsheet. You need four columns: employee name, job title, manager name, and department. Calculate the span of control for every person who manages at least one person.

In the United States and Europe, the average span of control for a technical manager is usually five to seven people. For a high-volume operational role like customer support, it might be ten to twelve. If you find managers with three or fewer reports, you have a structural inefficiency. These managers often become glorified project managers or they micromanage their small teams because they do not have enough people to lead. Conversely, if a manager has more than nine reports, they likely do not have time for career development or performance management.

Look for layers. Count the steps from the CEO to the most junior individual contributor. In a company of 500 people, you should not have more than five or six layers. If you have eight layers, you are operating with the bureaucracy of a firm ten times your size. This creates a game of telephone where the strategic goals set in the boardroom are unrecognizable by the time they reach the front line.

The ratio method for headcount planning

Instead of asking department heads what they want, give them a structural framework based on ratios. This forces them to think about org design before hiring. For example, tell your engineering VP that for every seven software engineers, they are allowed to hire one engineering manager. Tell your sales leader that for every eight account executives, they need one sales manager and one sales operations specialist.

This method prevents the common trap of hiring a new manager just because an existing one feels busy. Often, a manager feels busy because they are doing the work of their reports, not because they have too many reports. By enforcing a minimum span of control, you force senior leaders to delegate and trust their teams.

In the European Union, where labor laws in countries like Germany or France make restructuring difficult, getting this right at the planning stage is even more important. It is much easier to design a broad, flat structure today than it is to remove redundant management layers two years from now when growth slows and margins matter.

Redesigning for autonomy

Effective org design assumes that information should travel horizontally as much as vertically. When you plan your next phase of growth, look at the dependencies between teams. A common mistake is to organize by function alone. This creates silos where marketing does not talk to product, and product does not talk to sales.

Consider a pod-based structure for certain departments. In this model, you group people by mission rather than just by craft. A product pod might include one product manager, four developers, one designer, and one data analyst. From an org chart perspective, these people might still report to their respective functional heads for career growth, but their daily work happens in the cross-functional pod.

When planning headcount for these pods, you must account for the overhead of collaboration. A pod of six people needs a clear lead. If you plan to scale from three pods to ten pods, you cannot just hire 42 more people. You need to decide who will manage the leads of those pods. This is where you decide if you need a Director of Product or a VP of Engineering. Do not hire these senior roles until the span of control for the existing leadership team exceeds seven.

Handling the transition

Moving from a loose, founder-led structure to a disciplined org design will cause friction. Some managers will feel demoted if their span of control is reduced, or if they are asked to move back to an individual contributor role because the organization does not need their layer of management.

You must frame these changes around impact. A manager with twelve reports is not a hero; they are a single point of failure. By reducing their span to seven, you are giving them the capacity to actually coach their team and contribute to strategy.

When you present the new workforce plan to the executive team, do not lead with the names of the people you want to hire. Lead with the diagram of the organization you want to build. Show them the current spans of control and the proposed spans after the new hires arrive. If the new hires make the organization taller and skinnier, reject the plan. If the new hires maintain a healthy, flat structure that keeps teams close to the customer, approve it.

Building the blueprint

Workforce planning is not a financial exercise. It is a design exercise. The tools you use matter. While a spreadsheet is fine for the data, you need a visual tool like Lucidchart, Miro, or specialized org design software to see the reporting lines.

Every time a department head requests a new role, they should be required to submit an updated org chart showing where that person fits and what the resulting spans of control will be. If the new hire creates a reporting line of 1:1 or 1:2, the request should be denied unless there is a clear plan to add more reports to that manager within 90 days.

This level of discipline ensures that as you scale, you do not lose the speed that made you successful in the first place. You are not just hiring people to fill desks; you are building a machine that is designed to communicate, decide, and execute without getting stuck in its own gears.