The management layer is removed on Friday.
On Monday, the coordination work is still there.
Someone has to decide which project gets the shared engineer. Someone has to explain the strategy to the team. Someone has to tell stakeholders the timeline moved. Someone has to resolve the API disagreement, track the dependency, notice the underperformance, prepare the status update, and keep two teams from building incompatible versions of the same thing.
The salary line improved. The work moved.
Eliminating managers saves time only when the management work was unnecessary. Often the work was necessary and merely invisible because managers contained it.
The Work Was Coordination
Management looks like overhead because it often produces no code, campaign, sale, ticket, or design artifact.
Its output is a resolved priority conflict, a cleared dependency, a decision made before it becomes a crisis, a stakeholder kept from interrupting a team, a performance issue addressed before the team absorbs it, or context translated between strategy and execution.
When the manager disappears, those tasks go somewhere.
Individual contributors schedule the meetings. Senior engineers become de facto coordinators. Executives handle tactical escalations. Some work simply does not happen until failure makes the omission visible.
The organization then sees slower delivery and calls it transition pain. Sometimes it is the real cost of distributing coordination to people whose primary work needs focus.
Individual Contributors Pay in Context Switching
Engineering, design, analysis, and writing often need long stretches of loaded context. Coordination interrupts that context.
A manager can move between meetings, quick decisions, stakeholder messages, and status updates because much of the role is already interrupt-driven. An engineer pulled into the same pattern loses the deep work state that made their technical time valuable.
A one-hour coordination meeting does not cost one hour of engineering work. It costs the meeting, the preparation, the recovery, the half-finished thought before it, and the avoidance of starting hard work in the thirty-minute gap afterward.
This is why distributing management work can be more expensive than hiring a manager. The same coordination task is now performed by people with higher opportunity cost and worse working conditions for that task.
Authority Does Not Redistribute Automatically
Managers often have formal authority to arbitrate priorities, allocate attention, hold people accountable, and escalate with standing.
Individual contributors usually do not.
Two teams disagree about an API. Without a manager, they negotiate. Neither can overrule the other. The discussion continues until someone with authority is pulled in, often later and with less context. The decision takes longer and may be worse.
Senior ICs often fill the gap because they have credibility. They still may lack authority over staffing, priorities, and performance. They become managers in practice while being measured as individual contributors.
That arrangement burns people out quickly. It asks them to absorb managerial responsibility without the title, time, training, or authority.
Information Fragments
Managers accumulate cross-team context by design. They know who is working on what, where the dependency sits, which stakeholder is anxious, what leadership really cares about, and which conflict is about to surface.
Remove the role and that context has to be rebuilt for each coordination event.
An engineer needs help from another team. They have to find the right person, establish why the request matters, learn the other team’s priorities, and keep track of follow-up. The manager used to know the matching manager, the history, and the right framing.
Direct communication can be faster when the relationship already exists. It can be much slower when every request starts with discovery.
The Middle Horizon Disappears
Individual contributors tend to optimize around immediate work. Executives tend to optimize around strategy, budgets, and larger organizational risk. Managers often hold the middle horizon: the next few months of dependencies, staffing, sequencing, and trade-offs.
When that layer is removed, the middle horizon can vanish.
Teams complete tasks while slowly drifting from strategy. Dependencies are discovered late. Capacity conflicts appear only when two projects need the same person in the same week. Performance issues sit because no peer wants the social cost of confronting them.
The organization does not notice immediately because already-defined work can continue for a while. The failure appears later, when the next layer of coordination should have happened and did not.
The False Economy
The simple calculation is manager salary saved.
The real calculation includes individual contributor time spent coordinating, reduced deep-work output, slower decisions, executive time spent on tactical issues, missed dependencies, rework, attrition from senior people carrying two jobs, and the coordination failures that appear months later.
A manager’s salary is visible. Distributed coordination cost is spread across calendars and delayed outcomes. That makes the savings look cleaner than they are.
The organization may save a headcount line and spend more in lost execution capacity.
When It Actually Works
Manager elimination can work in small, simple systems.
A team under ten people, with low dependency work, strong documentation, clear ownership, mature contributors, good async tools, and few cross-functional handoffs may coordinate without a dedicated manager. In that environment, management can be overhead.
The model breaks as dependencies grow. Once work spans multiple teams, scarce resources, competing priorities, customer commitments, and performance management, coordination becomes a specialized function again.
The useful question is whether coordination needs are small enough to distribute without overwhelming the people doing the primary work.
Reduce Coordination Before Removing Coordinators
Organizations usually want to eliminate the pain managers represent: meetings, approval chains, status reporting, and bureaucracy.
Removing managers does not remove the causes. Unclear strategy still requires alignment. Misaligned incentives still create conflict. Complex dependencies still need sequencing. Weak tooling still forces synchronous coordination. Centralized authority still creates escalation.
The better order is to reduce the coordination load first. Clarify strategy. Give teams authority. Improve interfaces. Reduce dependencies. Automate status where possible. Build tools and norms for async coordination.
As the work decreases, fewer managers may be needed. That is different from deleting the role and hoping the work evaporates.
Coordination above a certain scale has to be someone’s job. The choice is whether it is done explicitly by people equipped for it, or implicitly by everyone at the cost of the work they were hired to do.
