Skip to main content

Does Removing a Management Layer Save Time? Account for the Work That Changes

A credible assessment includes responsibilities removed, work transferred, and the capacity needed during the transition.

Does Removing a Management Layer Save Time? Account for the Work That Changes

A consultancy merges two departments and proposes removing a layer of delivery managers. Project leads will report directly to a director, update a common portfolio record, and resolve routine dependencies with one another. The proposal promises fewer approvals and more time spent on client work.

That outcome is possible. Some reviews may duplicate work already done by project leads, and the director may be able to delegate decisions that previously travelled through several roles. But the current managers also arrange staffing, coach new leads, negotiate changes with clients, and address problems that projects cannot resolve alone. Those responsibilities need a destination.

The useful assessment starts with the work that will change. There is no general basis for claiming that eliminating managers rarely saves time, or that individual contributors are inherently worse at coordination. Savings depend on which activities disappear, how the remaining work is organised, and whether the new arrangement can operate reliably.

Establish What the Current Layer Actually Does

Job descriptions provide a starting point, but actual cases reveal more. Ask the delivery managers and project leads to trace a normal planning cycle, a staffing conflict, and a project in difficulty. Identify decisions, relationships, recurring tasks, and responsibilities that require discretion or confidentiality.

Separate necessary work from its current method. Resource allocation might require a decision when two clients need the same specialist. It need not require three successive presentation meetings. Coaching may require dedicated time but not the same reporting relationship. A weekly update might be unnecessary if an existing record already provides accurate information.

Also examine work the current layer fails to do. A redesign should not assume that every existing responsibility is being fulfilled well. Managers might be overloaded, have conflicting objectives, or lack the authority to resolve issues. Removing a role could expose a gap that already existed, rather than create it.

Research can inform this investigation without settling it. In The Value of Bosses, Edward Lazear, Kathryn Shaw, and Christopher Stanton analyse supervisor effects using data from technology-based service workers in one company. They find meaningful differences associated with supervisor quality. The study provides evidence that supervision can affect outcomes in that setting; it does not estimate the effect of removing a management layer from every kind of organisation.

That distinction matters. The consultancy needs evidence about its own responsibilities, alternatives, and constraints. A finding that some managers add value cannot justify every layer, just as complaints about one layer cannot establish that all management work is dispensable.

Decide What Stops, What Moves, and What Changes

Create a short account of the proposed arrangement for each important responsibility. Some work should stop because its purpose has expired or another requirement already covers it. Some should move to an existing role with suitable capacity. Other work may be redesigned so that it is needed less often.

The consultancy could give project leads authority to agree small staffing exchanges within defined limits. A shared record could make availability easier to find. The director might retain decisions that affect client commitments or exceed the department’s capacity. This could reduce both the number of escalations and the work needed to prepare them.

Naming the director as the destination for everything is insufficient. Estimate the volume and character of the decisions they would receive. Include support for project leads, not only formal approvals. A wider reporting span may be workable for experienced leads with stable work and difficult for people managing unfamiliar projects through frequent change.

Employee support and sensitive concerns need particular care. Decide who provides development feedback, handles conflicts, and receives a concern that cannot appropriately go to a peer. The arrangement should explain how people obtain help when the designated person is unavailable or involved in the issue. These responsibilities require suitable access, competence, and time, regardless of the job title attached to them.

Transfer Authority Along With Responsibility

A project lead asked to resolve staffing conflicts needs to know which commitments they can make. Can they change a specialist’s allocation? Does the other project lead need to agree? Who decides when the proposed exchange would put a client’s delivery at risk?

Without answers, removing the intermediary may replace one approval route with repeated negotiation. With suitable boundaries, it may make routine decisions considerably faster. The change in authority is part of the redesign and should be assessed explicitly.

The same applies to information. A delivery manager may currently know about a client’s likely extension before that information enters the staffing plan. If the new process relies on the shared record, establish who supplies this information and when. Transferring a spreadsheet without transferring the meaning of its entries can leave the new arrangement less usable than it appears.

Avoid making one experienced contributor the informal destination for every unresolved matter. They may be willing to help, but the additional work needs recognition, capacity, and a defined remit. The companion discussion of informal authority in flat organisations considers how these responsibilities can otherwise become difficult to see or challenge.

Include Transition Effort and Displaced Work

The cost comparison should cover more than salaries. Include preparation and meeting time, work transferred to project leads and the director, changes to systems, training, and the effort needed to establish new relationships. Some of these are temporary; others recur.

Do not turn that list into an assumed financial loss. Time spent coordinating is not automatically wasted time, and an hour released from a meeting does not automatically become an hour of billable delivery. People may need the capacity for planning, learning, or a workload that was already excessive. State what kind of saving is being claimed.

Interruption effects deserve attention without a universal multiplier. A short request can disrupt work that requires sustained context, but the cost varies with the task, timing, and working arrangement. Project leads may be able to group routine requests into predictable periods. Urgent issues need a route that does not depend on waiting for those periods.

Separate transition effects from the intended operating model. It is reasonable to expect some early effort while people learn the arrangement. It is less reasonable to describe every continuing delay as temporary without evidence of improvement. Set review points and identify which capabilities must be in place before the new structure can operate as proposed.

Plan continuity before the reporting change takes effect. The outgoing delivery managers may hold knowledge of client sensitivities, informal staffing arrangements, and unresolved concerns that cannot be captured by forwarding meeting invitations. Identify what the receiving roles need to understand, arrange relevant introductions, and record outstanding commitments with their current status.

Some information needs restricted handling. A general portfolio document is not an appropriate destination for every employee concern or confidential client discussion. Transfer access according to the responsibility, and establish where the new role can obtain suitable support. A redesign should not depend on a former manager continuing to answer sensitive questions informally after their responsibility has ended.

Give the receiving roles time to learn. A project lead may need practice in negotiating staffing or recognising when a concern needs specialist help. That requirement does not establish that the change is unworkable; it belongs in the transition plan and its cost. The proposed saving is more credible when it includes the work needed to make the new arrangement dependable, rather than assuming that responsibilities transfer instantly with a new reporting line.

Test the Design Against the Difficult Cases

A quiet month may not reveal whether the consultancy can handle conflicting client commitments. Work through a case in which the same specialist is needed by two urgent projects, a lead is absent, and a customer changes scope. Establish who acts, what they can decide, and where the necessary information comes from.

If a bounded trial is practical, follow a group of comparable projects through the new arrangement. Monitor decision waiting, missed commitments, rework, client experience, and the workload of people receiving additional responsibilities. Compare case complexity and demand as well as headline completion rates. A different project mix can obscure improvement or deterioration.

Where the change is already committed, retain a route for correcting the operating model. That does not necessarily mean restoring the previous layer. It could mean narrowing a director’s remit, providing dedicated staffing support, or adjusting which decisions belong to project leads. People need permission to describe problems without being treated as resistant to the reorganisation.

The US Government Accountability Office’s guidance on mergers and organisational transformations, developed from a practitioner forum, interviews, and a literature review, emphasises the human aspects of implementation. It offers relevant planning considerations, rather than a controlled estimate of the benefits of flattening a hierarchy. Communication and participation need to affect how the new arrangement works, not merely explain an already completed chart.

Removing the delivery layer saves useful time if fewer steps are needed and the remaining responsibilities are carried out with adequate authority and capacity. If those conditions do not hold, the organisation may have redistributed effort rather than reduced it. The practical objective is a better way to deliver and support the work, with a credible account of its costs and consequences.