Middle managers are where transformation becomes a daily choice. They explain the change, allocate attention and absorb the friction when systems disagree, which makes them the layer most transformation plans rely on and least often design for. Harvard Business Impact found that more than half of midlevel leaders say they spend at least 40% of their time on administration or individual-contributor work. That leaves little room for translation.
The common response is another manager programme. My response is to inspect the role first: what decisions does the manager own, what work can be removed and what evidence must travel upwards? A programme can teach managers what the change means. It cannot create the hours, the authority or the safety they need to act on it.
That finding is not a criticism of managers. It is a design fact. A role filled with administration was designed, perhaps without anyone intending it, to produce reports rather than translation. Transformation then asks that same role to do something its design never made room for.
What middle managers carry in a transformation
A strategic message reaches a manager as a set of competing requests. A new process, a revised target, a customer promise and a reporting demand can all land in the same week. The manager decides which gets attention, how to explain it to the team and what to do when two of them conflict. That is the point at which a transformation either becomes work or stays a slide.
The manager bridge model gives that role a shape. It has three parts: sensemaking, workflow conversion and signal return. Each part needs time and a practical tool.
- Translate: Explain the strategic choice in the team’s context.
- Convert: Change a workflow, handoff or customer interaction.
- Return: Send an honest signal about what is failing.
Sensemaking: Turning the message into a local explanation
Sensemaking means turning a strategic message into a local explanation that respects the team’s reality. A manager who can only repeat the launch narrative has passed on a message, not explained a change.
Useful sensemaking answers three plain questions for the team: what is changing in my work, what stays the same and who do I ask when the two collide. The sponsor’s job is to give managers enough of the reasoning to answer honestly, including the parts that are still undecided. A manager who is trusted with the uncertain parts can be trusted to explain the settled ones.
Workflow conversion: Where transformation earns credibility
Workflow conversion means changing a meeting, approval, handoff or customer interaction. It is where transformation earns credibility.
Teams judge a change by what happens to their week. If the new way of working still needs the old approvals, the old reports and the old escalations, people conclude that the change is optional. Managers need the authority to remove a step as well as to add one, and a sponsor willing to back them when they do.
Convert one workflow at a time. Choose a meeting, an approval or a customer handoff, agree what it looks like after the change and let the manager own the transition. A single converted workflow teaches more than a list of intentions, and it gives the next manager a worked example.
Signal return: Why psychological safety is an execution control
Signal return means reporting what is failing without polishing the message for senior leaders. Psychological safety is an execution control, because a manager who expects a poor reception for bad news will soften it.
The executive team then receives a tidy update while the process stays unchanged. The sponsor influences this more than anyone, because the way the first awkward report is received tells every other manager what to send next time. Treat a failed handoff, a workaround or a blocking rule as useful information, and say so in front of the group.
Give signal return a form. A short weekly note from each manager, asking what failed, which workaround appeared and which rule got in the way, is more useful than a polished status. It should go to someone with the authority to change the rule, and the answer should come back to the manager within the same cycle.
Capacity and authority come before another programme
Middle managers are the bridge because they translate an enterprise choice into a team’s next decision. If the role is already consumed by reporting and individual-contributor work, the bridge has no capacity. The first intervention is often to remove work, not add another leadership module.
If the role is overloaded, no amount of inspiration will create capacity. Start by removing reporting that no decision depends on and by clarifying where escalation begins. Nor does the answer lie in adding another tier. I would first ask whether the existing management layer has been designed to carry the change.
A transformation sponsor should give managers a visible decision boundary. They need to know what can be adapted locally and what must remain consistent. That boundary prevents both passive compliance and uncontrolled reinvention.
Authority matters as much as time. A manager who must ask permission to change a rota, a template or a handoff will wait, and the team will read the wait as a verdict on the change. Decide in advance which adjustments belong to the manager, which need a conversation and which belong to the sponsor, then write that down where managers can find it.
Middle managers are the layer that turns a transformation plan into a change in daily work. Give them a decision to make, a boundary around it and a way to report what happened. If the plan skips that layer, the executive team receives a polished update while the process remains unchanged.
Run manager forums on live operating cases
The best manager forums use live cases. A manager brings a customer complaint, an approval delay or a staffing conflict and applies the new decision rule. The group learns where the rule helps and where the architecture needs adjustment.
Keep the forum small and regular. Managers who bring a real case, leave with a decision and see it adopted tend to come back. Managers who sit through a briefing have little reason to. Over time the cases show a sponsor which rules travel well and which parts of the design need to change.
Progress appears when managers spend less time translating ambiguity and more time improving the system around their teams. That is a capability shift, not a morale slogan.
How to tell whether the middle managers layer is working
The manager bridge model has three tests. Can the manager explain why the change matters in the team’s context? Can the team perform the changed workflow? Can the manager send an unpolished signal back upstream when the design is failing? Each test needs a different support.
Executives should measure whether managers can make the intended decision under pressure, not whether they attended the launch session.
Transformation delivery improves when the middle layer has a shared review rhythm. Keep the question narrow: what changed in the work this week, what exception appeared and what decision is needed? A short record is enough if someone uses it.
- Remove administration that no decision depends on, so managers have time to translate the change.
- Agree an adaptation boundary: what may change locally, and what must remain consistent across the organisation.
- Use live customer, staffing and workflow cases in manager forums. Abstract change language rarely survives contact with a rota, backlog or customer escalation.
- Give managers a safe route for returning unpolished signals, including failed handoffs, workarounds and rules that are blocking delivery.
- Measure whether managers can make the new decision under pressure, not whether they can repeat the transformation narrative.
A lesson from The Leadership Shift
The book recounts a media organisation whose leaders did not understand the work or responsibilities of their peers. Requests that supported board reporting were dismissed as waste. The intervention began by making communication, connectivity and stakeholder management visible. That is the role I give middle managers in transformation: they translate a strategic request into work people can understand and act on.
Trace one request from start to finish
A manager can show where the design breaks by tracing one customer request from start to finish. Look for the handoff, the correction and the point where authority becomes unclear. Fix that point before adding another initiative to the portfolio.
The operating model should make room for managers to challenge a proposed change. They are close enough to see the cost and senior enough to act on it. Capture the challenge, decide what will change and tell the wider team why.
The result is visible when managers can explain the new way of working without waiting for an executive briefing. That is the evidence that the transformation has reached the organisation rather than stopping at the top. The wider point, that capability has to exist at every layer and not only at the top, is in leadership capability at every level.
Transformation delivery improves when middle managers are designed as an operating layer rather than treated as a message relay. That is the distinction I would test with sponsors and operational leaders.
If you want to see where your own managers carry the most weight, I would start with the Leadership Capability Architecture framework, which makes decision rights and routines visible layer by layer. CapabilityAI adds the practical intelligence layer once those routines are in place, and the organisational change and capability pathway describes how the same questions play out in a live programme.
Further reading: Why Employee Development Should Be a Top Priority
Further reading: Leadership Team Ready to Scale: How Do You Know?