A manager is hired to improve coordination between two teams.
Before the role exists, the teams coordinate informally. It is imperfect. They miss a dependency occasionally. They repeat context. They solve most issues through direct conversations.
The new manager introduces a cleaner system: a shared planning document, a request intake process, a weekly sync, an escalation path, and a dashboard for visibility. None of it is absurd. Each piece can be defended.
Three months later, the teams spend more time coordinating than they did before. Requests wait in the intake queue. The weekly sync covers items that could have been solved in ten minutes. The dashboard needs updates. Someone proposes a coordinator to manage the coordination process.
The management layer has created work that proves the management layer is necessary.
Activity Becomes the Evidence
Self-justifying management rarely begins with bad intent. It begins with weak measures.
If a manager is assessed by team size, budget, process ownership, meeting presence, reporting volume, and visible engagement, expansion becomes rational. Simplification is risky because it makes the work less visible. A clean handoff that no longer needs the manager does not show up as clearly as a recurring forum the manager runs.
Process becomes evidence of value. The manager can point to intake volume, alignment meetings, reporting cadence, risk registers, and stakeholder updates. The activity is real. The question is whether it improved the outcome or created another layer the work must pass through.
That question is often missing.
Process Expands Faster Than It Retires
A useful management layer simplifies as well as adds.
Self-justifying management only adds. A new template for planning. A new approval path for risks. A new review meeting. A new dashboard because the previous dashboard did not create enough visibility. Each addition responds to a specific concern and survives after the concern fades.
Over time, teams operate under accumulated process debt. No individual process is outrageous. The aggregate makes ordinary work slow enough that more management seems necessary to navigate it.
This is how bureaucracy protects itself. The more process exists, the more people are needed to explain, enforce, summarize, and improve the process.
Standardization Can Invent Problems
A director audits three teams and finds inconsistency.
Different tools. Different code review norms. Different planning rituals. Different documentation practices. The teams are shipping adequately, but the inconsistency looks like risk. How can the organization scale if every team works differently?
A standardization program begins. Common tools, unified templates, mandatory training, compliance checks. The work expands. Teams migrate away from local systems that fit their constraints into standard systems that fit nobody perfectly.
Some standardization is valuable, especially where teams share interfaces. But inconsistency is not automatically dysfunction. Sometimes it is local adaptation.
Self-justifying management treats variation as a problem because variation creates a program to manage.
Meetings Create Visible Management
Meetings are management’s most legible artifact.
A weekly status meeting becomes a planning meeting, then a retrospective, then a pre-meeting before the leadership review, then a follow-up forum to track actions from the review. Each meeting has a plausible purpose. Together they create a loop where people meet about work more than they change the work.
The meeting load is hard to challenge because every meeting can be defended individually. Coordination matters. Planning matters. Retrospectives matter. Leadership prep matters.
The pathology lives in the system, not the calendar invite. The meetings preserve management visibility even when they do not remove the underlying constraint.
Reporting Can Exceed the Work
A team sends a weekly update. The manager summarizes it for a director. The director folds it into a VP report. The VP turns it into an executive narrative. Each layer asks for slightly different fields.
The team now maintains multiple versions of status. Leadership receives more reporting and often less truth. By the time the information arrives, it has been compressed into language that avoids alarm and preserves the reporting chain.
Reporting is useful when it supports decisions. It becomes self-justifying when the reports exist primarily because a management layer needs information to process.
If removing a report would make a role’s value harder to explain without harming decisions, the report is carrying more politics than insight.
Why It Is Hard to Remove
Once a management layer exists, the organization adapts around it.
The manager runs the planning meeting. They hold stakeholder relationships. They know who needs to be warned before a change. They maintain the dashboard everyone complains about and still uses. Removing the role now requires replacing the coordination mechanism the role created or absorbed.
That lock-in is real even when the layer is inefficient.
Elimination also has political cost. Removing a role says the role may not have been needed. It reflects on the people who created, funded, promoted, and defended it. Peers may resist because questioning one layer threatens others.
So the layer remains. It is easier to tolerate diffuse overhead than to spend concentrated political capital removing it.
What Valuable Management Looks Like
Management adds value when it resolves real coordination problems that would exist without the manager.
A launch spans engineering, product, marketing, support, and operations. Someone has to sequence dependencies and make trade-offs when they collide. A technical program crosses three teams with shared architecture. Someone has to see the full system. A manager notices that several teams are solving the same problem and consolidates the work before duplication hardens.
Valuable management makes decisions, synthesizes information, transfers learning, and reduces future coordination cost.
Self-justifying management increases the coordination surface. It creates forums, reporting, and processes that require more management to sustain them.
The test is whether the management layer makes the system simpler to operate over time. If every year requires more meetings, more dashboards, more coordinators, and more escalation paths to achieve the same output, the layer is probably feeding on its own complexity.
How to Resist the Trap
Measure process cost. Track time spent on reporting, approval navigation, status meetings, and preparation for meetings. Compare it with decisions made, blockers removed, and delivery outcomes improved.
Require process retirement. New recurring meetings should replace old ones. New reports should retire old reports. New approval steps should have sunset dates and owners.
Protect direct communication. Managers can synthesize and decide without becoming mandatory conduits for every relationship.
Reward scope reduction. A manager who gets the same or better outcomes with fewer meetings, fewer reports, and less dependency on themselves has created value. A manager who needs more process every quarter has created demand for their own services.
Management is overhead until it improves the work enough to justify itself. Mature organizations admit that and keep asking for proof. Less mature ones confuse the visible management of complexity with the creation of value.
