An equipment maintenance business combines five regional operations into a national service. The new structure removes regional management roles and gives local supervisors a direct reporting line to the operations director. The proposal promises faster communication and lower management costs. It also changes who resolves disputes over specialist engineers, coordinates large customer commitments, and notices when local workarounds are becoming shared problems.
The change may succeed. It may remove duplicated approvals and give experienced supervisors more discretion. Its success depends partly on whether those regional functions were unnecessary, transferred, or simply omitted from the design. Removing a reporting line does not settle that question.
Middle management can support organisational stability by connecting work across teams and time horizons. That contribution is worth examining without treating every existing layer as essential. A useful assessment identifies what the organisation needs done, who will do it after a change, and how it will detect problems early enough to respond.
Start With Functions Rather Than the Number of Layers
Middle management generally sits between senior leadership and frontline management or delivery teams. Titles vary: a regional manager, department head, or engineering director may occupy this position in one organisation and a different position in another. The relevant feature is the role’s place in the operating arrangement.
In the maintenance business, regional managers may have scheduled specialist capacity across sites, resolved customer exceptions, and supported supervisors. Some may also have required approvals for routine work that local staff could safely decide. These are different activities and need separate consideration.
A review should ask which activities require judgement, which can become a standard process, and which no longer serve a useful purpose. The outcome might be a smaller regional role, a national scheduling team, a broader mandate for supervisors, or retention of a manager where the coordination demand remains high.
This avoids assuming that stability belongs to a particular job title. Teams can coordinate directly, specialists can maintain shared standards, and systems can make information easier to use. Those arrangements still require time, competence, and someone responsible for keeping them effective.
Connect Local Evidence to Decisions About the Whole Service
A supervisor sees that a recurring equipment fault is consuming more visits. The director sees that national response times are worsening. Connecting those observations may reveal a shared training need, an unreliable part, or a service promise that no longer fits the work.
A regional manager can help assemble this evidence, compare sites, and bring a decision to the right level. The value is in preserving the meaning of the local information. A national average alone might conceal that one equipment model accounts for most repeat visits, while an unfiltered stream of individual cases may obscure the pattern.
The return path matters too. If leadership changes the service offer, supervisors need to know which customers are affected, when the change applies, and what commitments remain valid. A summary that omits those conditions can lead sites to act on different interpretations of the same decision.
These functions can continue in a flatter structure if the organisation establishes another reliable route. The design should specify how operational evidence reaches investment and service decisions, and how the resulting choices reach the people implementing them. Publishing more information is useful only if people can find and apply what matters.
Make Shared Resources Available Through a Usable Process
Specialist engineers cannot be in several regions at once. When two major customers need the same capability, a scheduling tool can expose the collision. Someone still needs to decide whether to move another job, obtain external help, or revise a customer commitment.
A regional manager may hold sufficient authority to settle some conflicts. A national conflict may need a director’s decision. The structure should distinguish those cases and provide a response route that fits the consequences of waiting. Supervisors should not have to negotiate the same priority dispute repeatedly without access to a decision.
This is also a capacity question. Giving the director all regional escalations may be workable at a modest volume, but become impractical as demand grows. Assess the expected decisions and support needs before assuming that a wider reporting span will improve speed.
The related article on managers without authority examines repeated negotiation in more detail. Here the organisational design question is where the decisions and preparation work should sit after a layer changes, including how much capacity the receiving roles will need.
What Research Can Establish About Management
Management practices can affect performance. In Bloom and colleagues’ field experiment in Indian textile firms, an intervention introducing management practices improved productivity in the studied setting. The research concerns a package of practices and their adoption. It does not establish that preserving any particular management layer prevents organisational collapse.
That distinction matters when using evidence in a restructure. A company cannot infer from management research that every current manager adds value, or that a fixed proportion of managers is optimal. It needs to examine its own work, capabilities, dependencies, and operating conditions.
Equally, reducing management payroll is only one part of the comparison. Work may transfer to supervisors, specialists, or senior leaders. Some may disappear because the approval or report was unnecessary. An assessment should account for both possibilities instead of assuming either that all work persists unchanged or that every removed role represents a net saving.
The evidence can include decision waiting time, repeated visits, time spent resolving scheduling conflicts, supervisor access to support, and the reliability of customer commitments. These indicators should be interpreted together. A temporary rise in escalations may show a newly visible problem rather than deterioration caused by the change.
Design the Transition Around the Work That Must Continue
Before changing the structure, follow several real cases through the proposed arrangement. Use an ordinary scheduling request, a serious customer exception, an absence during peak demand, and a disagreement between sites. Identify who decides, who supplies evidence, and what happens while a choice is pending.
The exercise may expose missing permissions or an overloaded receiving role. It can also show that an existing approval adds little. Adjusting the design before implementation is more useful than declaring all friction evidence that the old hierarchy was necessary.
Knowledge continuity belongs in the transition plan. Regional managers may know why a customer arrangement differs, where a procedure fails, or which specialist can answer an unusual question. That knowledge should be examined and transferred to the relevant people and records. The article on organisational memory explores how to do this without making one person’s recollection the permanent source of truth.
Decide how the organisation will learn after the change. Set a review point, establish which measures are available beforehand, and name who can adjust the design. Some problems will require training or a clearer mandate; others may justify restoring coordination capacity. A review is useful when it can lead to a real change in responsibilities or resources.
Give the transition an explicit operating limit. If supervisors cannot obtain a resource decision within the time needed to meet service commitments, identify who will intervene and what can be deferred. A temporary support arrangement may be justified while the new route becomes reliable. Calling that adjustment a failed restructure too early can discourage useful correction; refusing to adjust despite repeated evidence can prolong a preventable problem.
Include the people receiving the transferred work in the review. A director’s shorter approval chain may coincide with supervisors spending more time preparing escalations or losing access to coaching. The comparison should examine the whole service, including where time and responsibility moved.
Avoid Making Managers the Permanent Workaround
A structure may appear stable because managers repeatedly repair the same missing handoff. In the maintenance business, a regional manager might spend Friday afternoons reconciling schedules that two systems represent differently. That effort can keep service running, but it also indicates a process or information problem worth fixing.
Removing the manager before addressing the mismatch may expose the problem. Retaining the role indefinitely without repair also has a cost. A better plan distinguishes the temporary work needed to keep operating from the change that reduces the recurring burden.
Managers should be able to report those burdens without presenting every resolved issue as a disaster prevented. A short account of the mismatch, the time it consumes, and the proposed repair gives leadership a basis for investment. It also helps determine whether the role needs more capacity or less avoidable work.
The same standard applies to management activity that creates delay. If regional approval merely repeats a check already completed by a competent supervisor, the organisation can test removing it within appropriate limits. Supporting middle management should include improving the work it does.
A sound structure provides routes for evidence, decisions, support, and continuity at a cost the organisation can sustain. Middle managers often contribute to those routes, but their value depends on the remit and conditions around them. When changing layers, examine how those functions will operate in the proposed design and whether the people taking them on have the authority, information, and time to do them well.





