Most companies at the 10-to-50-person stage have an org chart that exists in the founder's head. That is not a structure. It is a single point of failure. Here is how to think about spans of control and management layers before they become a crisis.
I have done RIFs. I have been in rooms where we made decisions about which roles to eliminate, which teams to consolidate, and how to communicate those decisions to people who did not see them coming. It is among the hardest operational work there is, and I can tell you from experience that a significant percentage of every RIF I have ever been involved in was made worse, more expensive, and more damaging to culture than it needed to be because the org structure that preceded it was never deliberately designed.
Poor org design is not just an HR problem. It is a cost problem, a decision-speed problem, and eventually a survival problem.
Span of control is simply the number of direct reports a manager has. A manager with a span of eight has eight people reporting directly to them. A manager with a span of two has two.
Neither extreme is inherently right. But both extremes have predictable costs.
Too wide a span means managers are stretched too thin to actually manage. They become coordinators and information routers rather than developers of people and drivers of outcomes. Work quality degrades quietly before it degrades visibly. High performers leave when they realize no one is investing in their growth. At the founder level specifically, a span of ten or twelve direct reports often means the CEO is spending their entire week in 1:1s and none of their week thinking strategically.
Too narrow a span means too many management layers for the size of the organization. When a 25-person company has four layers of management, every decision slows down. Communication becomes a game of telephone. Managers who have only one or two direct reports often become either disengaged or, worse, micromanagers who cannot let go of execution because that is where they still feel useful.
The org chart you never drew is the one everyone else is drawing for you, inconsistently, in their heads.
This is the range where most companies first encounter org design problems, and it is also the range where those problems are most likely to be ignored. The company is past the early chaos where everyone does everything. But it is not yet large enough that organizational dysfunction is obviously costing money in a measurable way.
What typically happens is this: a founder hires people and assigns them to report directly to themselves or to the earliest employees. Those earliest employees get larger and larger teams over time, not because anyone decided they should manage those teams, but because that is where new hires ended up. The result is an org structure that is a historical artifact of the order in which people were hired, not a deliberate design for how work should flow through the company.
By the time the company hits 30 or 40 people, the founder is often managing eight to twelve direct reports, several of whom are themselves managing teams. Critical decisions are queued behind the founder's bandwidth. New managers have never been formally trained and are figuring it out in real time. Accountability is murky because the reporting lines were never explicitly defined.
The point at which a founder should deliberately introduce a management layer is typically somewhere between 10 and 15 direct hires, and earlier if those hires are doing substantively different types of work. The goal is not to create hierarchy for its own sake. It is to ensure that the work of developing people, maintaining accountability, and driving execution does not all flow through one person's calendar.
A useful rule of thumb for growing companies: aim for spans of five to eight at most levels of the organization. Below five, question whether the management layer is necessary. Above eight, question whether the manager is actually managing or just nominally supervising.
When designing a management layer, group people by how their work naturally depends on each other, not by their seniority or their historical relationship to the founder. The engineering lead should manage engineers. The customer success lead should manage customer success. This sounds obvious but it is violated constantly in practice.
When a company hits a cash constraint and needs to reduce headcount, the companies that navigate that most cleanly are the ones that already have a clear org chart. They know exactly which roles are redundant, which functions are over-staffed relative to current revenue, and which management layers can be consolidated without damaging the core of the business.
Companies without a deliberate org structure face a much harder decision. Every cut feels more personal and less structural, because without a clear design, there is no structural logic to appeal to. The cuts end up being messier, slower, more legally exposed, and more damaging to the people who stay.
Draw the org chart before you need to redraw it under pressure.
If you are approaching a hiring inflection point or managing through a headcount reduction and need structured thinking on org design, Overcrest does this work. Reach out through overcrest.co.
The Overcrest Brief
Practical thinking on strategy, operations, fundraising, and growth for founders and operators at every stage.