Redesigning Middle Management for the Age of AI: Moving from Coordinators to Strategic Leaders

If you are responsible for how your organisation is structured, you have probably received two instructions about the managers in the middle. One says AI will absorb much of their work, so the layer should get smaller. The other says they should become more strategic, so the job should get bigger. Both land on the same people at the same time, usually without a description of what has changed in the role itself. Redesigning middle management for the age of AI is the work of closing that gap.

This blog is written for leaders who already accept that managers still matter and now need to decide what the role should contain. It covers what “strategic” can realistically mean at this level, which decisions managers should own, how wide their spans should be, what capabilities and measures support the shift, and how to sequence the change.

What does redesigning middle management actually involve?

It means changing what the managerial job is accountable for, who decides what, how many people each manager supports, which capabilities the role requires and how success is measured. Removing layers, or adding the word “strategic” to a job description, changes none of those things.

It helps to treat the role as five connected design choices. The first is the work: which tasks leave the job, which stay and which new ones arrive. The second is decision rights: which calls belong to the manager, which AI can make within set limits and which move up the hierarchy. The third is span of control, meaning the number of people a manager can support well. The fourth is capability, the skills the role now depends on that it may not have asked for before. The fifth is measurement, which is what the organisation notices and rewards.

When one of these changes without the others, the role pulls against itself. A manager asked to coach more but still measured on report output will keep producing reports. A manager given new decision authority without the judgement skills to use it will escalate everything. This is why redesigning middle management belongs in organisational design, where structure, roles, accountabilities and decision-making are considered together, rather than in a training plan or a headcount exercise.

Why does telling managers to “be more strategic” not work?

Because strategic work needs time, authority and capability, and an instruction supplies none of the three. When AI frees a few hours, those hours are usually claimed by wider spans or new demands before anyone has the chance to use them for strategic thinking.

Gartner’s 2024 strategic predictions illustrate the tension. The release forecast that AI would raise spans of control by automating scheduling, reporting and performance monitoring, which would leave remaining managers free to focus on more strategic and value-added activities. In the same passage, Gartner listed the likely problems: managers overwhelmed by additional direct reports, and mentoring and learning pathways that may break. Those two lists describe one situation from two sides. The time that AI frees is the same time that extra direct reports consume. These are forecasts, not measurements, but the arithmetic behind them is easy to recognise in practice.

Three other things tend to undermine the instruction. The mandate is vague, so “strategic” means something different to each manager and each senior leader. Accountability moves faster than authority, so managers answer for the outcomes of AI-supported processes they cannot change. And the signals stay the same: the same scorecards, the same approvals, the same meetings. A simple test is to ask three managers what being strategic means in their job this quarter. If the answers differ widely, the instruction has not yet been designed into the role. Redesigning middle management starts by replacing the instruction with a role that has time, authority and capability built in.

What does “strategic” mean for a middle manager?

At this level, strategic work is not setting company strategy. It is turning strategy into local priorities, deciding how work is shared between people and AI, reading what is happening on the ground, and developing the team’s capability. All four rely on context that a tool does not hold.

Translating direction into team priorities. Gallup’s 2026 research on AI and workplace productivity describes managers as the people who bring organisational direction down to practical guidance about where AI fits in employees’ actual work. The same translation applies to any strategic priority: someone has to decide what it means for this team this quarter.

Allocating work between people and AI. Deciding which tasks a person does, which an AI tool does and who checks the result is a design decision, and it recurs every time the work or the tools change. Managers are positioned to make it because they know the work and the people.

Sensing and reporting. Senior leaders usually see summaries. Managers see friction: a process that meets its targets but frustrates customers, or a team that has quietly stopped using a tool. Passing that upward in a useful form is strategic input.

Balancing continuity and change. In a study published in Administrative Science Quarterly, Quy Huy examined how middle managers contributed to radical change. His three-year field study of one large firm undergoing radical change found that middle managers helped their groups adapt by pairing commitment to change projects with attention to how people were reacting to them. Low commitment to change led to inertia, while high commitment with little attention to people’s reactions led to chaos. The author describes the study as suggestive rather than generalisable, but the pattern supports the point here: balancing change and continuity depends on reading people, which is hard to hand to a tool.

None of these is new to management. What changes is that they become the main body of the job instead of the part left over after the administration.

How does the role change from coordinator to strategic leader?

The centre of gravity moves from relaying and checking work to deciding priorities and developing people. Coordination does not disappear, but the routine portion is handled by systems and only the contested portion reaches the manager.

The difference shows up in six areas.

• Main contribution. A coordinator moves information and work between people. A strategic leader sets priorities and decides trade-offs for the team.
• Use of time. A coordinator spends it on meetings, status reports, approvals and checking. A strategic leader spends it on coaching, exceptions, cross-team alignment and sensing.
• Relationship with information. A coordinator controls and relays it. A strategic leader interprets it and tests it against context.
• Relationship with AI. A coordinator supervises the tools or avoids them. A strategic leader decides what AI does, checks the results and models good use.
• Source of authority. A coordinator relies on position and access to information. A strategic leader relies on judgement and the trust of the team.
• Success measure. A coordinator is judged on tasks completed and reports delivered. A strategic leader is judged on decision quality, team capability and retention.

Few managers fit wholly into one model, and this contrast is meant to show the direction of movement for a given role, not a classification. Some roles, such as those running tightly regulated processes, will keep more of the coordinator model than others. The aim is to be deliberate about which parts of coordination remain and why.

Which decisions should middle managers own once AI informs the work?

Managers should own decisions where context, trade-offs and accountability meet: exceptions, priorities, work allocation and people decisions. Routine, rule-based decisions can sit with AI inside agreed limits, and decisions with wider consequences should move up.

Writing this out as three tiers makes it usable:

• AI acts within limits, and the manager samples the results. Scheduling, routing of standard requests, approvals under a set threshold.
• The manager decides, with AI as an input. Team priorities, exceptions to policy, task allocation, performance and development conversations.
• The manager escalates. Decisions that cross budgets or teams, affect many customers, or raise ethical or legal questions.

Documenting the tiers matters as much as the allocation itself. Without a record, managers can drift in one of two directions: deferring to recommendations they do not fully understand, or overriding them without explanation. Either way, accountability weakens, because nobody can say who decided and on what basis. A one-page decision charter for each manager role, listing decisions owned, decisions informed by AI and decisions escalated, gives managers something to act on and gives the organisation something to review. This is a design practice rather than a research finding, so the thresholds should be set and revisited with the people who will use them.

How wide should a redesigned manager’s span of control be?

There is no universal number. Span should reflect how much people-related work remains once routine tasks leave the job, and it should be tested in a pilot rather than assumed. Wider spans are the usual first move, and they are also the quickest way to remove the time that strategic work needs.

A short calculation shows why. A manager who holds a 30-minute one-to-one with each report every week spends four hours on those conversations with eight reports and eight hours with sixteen. That is a fifth of a 40-hour week, before any development planning, hiring, conflict resolution or work with other teams. If AI has returned a few hours of administration to the manager, doubling the team can absorb all of them and more.

Several factors push the sensible range up or down:

• How standardised the work is. Repeatable work is easier to oversee at wider spans.
• How experienced the team is. Newer staff usually need more coaching and context.
• How reliable the AI tools are in that function. Output that needs heavy checking adds to the manager’s load.
• How much coordination the team needs with others. Teams with many dependencies draw more of the manager’s time.

Setting a range for each role family, rather than one organisation-wide ratio, and reviewing it after the pilot gives a more defensible answer than a target borrowed from another company.

What capabilities do managers need to lead strategically alongside AI?

Four capabilities carry most of the weight: team-level AI fluency, judgement under ambiguity, coaching, and influence across teams. Training on how a tool works addresses only part of the first.

The clearest evidence concerns AI fluency in the sense of enabling a team. Gallup’s 2026 data show that among employees in AI-adopting organisations, 78% of those who strongly agree their manager actively supports AI use are frequent users, compared with 44% of those who do not. Yet only 36% strongly agree that their manager provides that support. Gallup’s description of effective support includes actively backing AI use at team level, modelling it, answering questions and showing how it connects to daily work. These are survey associations, so they do not prove that manager support alone causes the difference, but the pattern is consistent across Gallup’s tracking.

The other three capabilities are less directly measured but follow from the role. Judgement under ambiguity means making a call when an AI recommendation conflicts with experience or with another team’s view. Coaching means regular, specific conversations that develop people, particularly as routine questions go to tools instead of to managers. Influence across teams matters because managers who no longer control the flow of information rely more on credibility and persuasion when aligning their peers.

Capability development belongs inside the redesign, not after it. Managers who have been told the role is changing, but have not yet been helped to develop these skills, are being asked to perform a job they have not been prepared for.

How should performance measures and incentives change?

Measure what managers decide and influence, not the administrative activity that AI now handles. Useful measures include decision speed and quality, growth in team capability, retention of strong people, the quality of AI-assisted work, and the alignment of team priorities with strategy.

Gallup’s work gives a reason to include people outcomes in particular. In an article for the Gallup Business Journal, Randall Beck and Jim Harter reported that managers account for at least 70% of the variance in employee engagement scores across business units. The figure is an estimate from Gallup’s own data and predates generative AI, so it is best read as evidence that a manager’s influence on team outcomes is large, not as a precise number for any single organisation.

If the scorecard still counts reports submitted and approvals turned around, the role will drift back towards coordination whatever the job description says. Measures are the part of redesigning middle management that tells people what the organisation actually values. Promotion criteria need the same review: if managers are mainly promoted for being strong individual performers, the new expectations about coaching and judgement will carry little weight.

What risks should leaders plan for?

Three risks recur: a weakened leadership pipeline, a loss of trust if the redesign is read as a disguised cut, and strain on managers while the old and new roles overlap.

The pipeline risk is one that Gartner named in the same 2024 release: mentoring and learning pathways may break, and more junior workers could lack development opportunities. Fewer manager roles means fewer places to practise leading. Deputy roles, project leadership and planned rotations are ways to create alternative routes.

The trust risk follows from a mismatch between words and actions. If the stated aim is a more strategic role but the visible action is a reduction in headcount, managers tend to believe the action. Being explicit about what has been decided, what has not and where managers can influence the design narrows that gap. Involving managers in drafting their own role charters is a practical way to do it.

The strain risk comes from sequencing. During the changeover, managers carry the old role and the new expectations at the same time. Remove tasks before adding expectations, and give people time to build the new skills. A plan for redesigning middle management should name these three risks at the start, with an owner for each.

How should an organisation sequence the redesign?

Start small: diagnose a few teams, write role charters, pilot for a quarter and adjust before scaling. A 13-week outline is enough to begin.

1. Weeks 1 to 3: Diagnose. Map where manager time goes and which decisions are made at which level. Ask managers directly, not only the leaders above them, and include a few teams of different types.
2. Weeks 4 to 6: Design. Draft a one-page role charter for each manager role covering purpose, decisions owned, expected span range, capabilities and measures. Add a stop list of tasks that should leave the role.
3. Weeks 7 to 10: Pilot. Test the charters with two or three teams. Remove tasks first, then add expectations, and give pilot managers support for AI fluency and coaching.
4. Weeks 11 to 13: Review. Compare decision speed, workload, engagement and the experience of newer staff against the starting point. Adjust spans, charters and measures before extending the changes.

Throughout, one question is worth returning to: what do we want managers to be able to do that they cannot do today, and what has to be true for them to do it? Moving managers from coordinators to strategic leaders is not a single decision. It happens when the work, decision rights, spans, capabilities and measures change together, and it holds when the people in the role help shape it.