A calendar opens like a crime scene. Meetings occupy nearly every square, approval requests wait in digital queues, and beneath one executive’s name sits a forest of direct reports, each carrying a smaller forest of their own. Nobody appears to be doing anything obviously foolish. Everyone is busy. That is precisely the problem. Organizations can become so fascinated with supervising work that supervision becomes work, creating layers whose main function is to explain, approve, coordinate, and reapprove what capable employees could have handled themselves. Control feels productive right up until nobody has time left to produce.
Management span is usually presented as a neat organizational-design question: how many people should report to one manager? Reality is considerably messier. A manager overseeing experienced specialists may handle a broader team than someone responsible for inexperienced employees performing complex, interdependent work. Technology changes the equation too. Clear dashboards, shared documentation, and automated workflows can reduce coordination costs, while ambiguous responsibilities and fragmented systems make even small teams exhausting to manage. The mistake is searching for a perfect ratio when the real question is whether the structure helps decisions travel efficiently.
Picture a regional operations manager receiving a request to replace a broken piece of equipment. The employee needs one approval. The supervisor needs another. Finance must confirm the budget. Procurement wants a form. The manager eventually receives the request between two meetings and approves it with a thumb pressed against a phone screen. The machine has been idle for days. Nobody intended to create this absurdity. Each layer was added for a reasonable purpose, yet together they produced a system where a small decision required the attention of people increasingly distant from the actual problem.
Amazon’s “two-pizza team” principle became famous because it captured an enduring organizational insight: smaller teams can sometimes communicate and act more effectively when responsibility is clear. The deeper lesson is not that every company should make teams tiny. It is that organizational design should reduce unnecessary dependencies. A product team may contain brilliant people and still move slowly if every decision travels upward. Conversely, a large team can function well when authority, information, and accountability are designed properly. Size matters. So does the architecture around it.
There is a darker reason organizations accumulate managers: management can become a substitute for fixing systems. When processes are unclear, leaders add coordinators. When accountability is weak, they add supervisors. When communication fails, they add meetings. When strategy changes constantly, they add people whose job becomes explaining the latest change. Soon an organization has a managerial layer for every problem except the original one. A company may believe it has become more controlled when it has actually become harder to steer. Bureaucracy rarely arrives wearing a villain’s costume. It arrives as a sensible exception.
A healthier organization asks a more uncomfortable set of questions. Who can make this decision now? Why can’t they? What information are they missing? Which approval genuinely protects the organization, and which merely protects a hierarchy from blame? Good managers do not measure their importance by how many people depend on them. Their real achievement may be making dependency unnecessary. That requires trust, capability, clear boundaries, and the courage to remove authority from places where authority has become ceremonial. Perhaps the most revealing measure of management is not how many people report upward, but how many decisions can move forward without stopping there.
