Middle managers translate organizational strategy and change into local priorities, decisions, expectations, and behavior. Leaders often brief them only shortly before an announcement, even though employees will turn to them with detailed questions. Managers need time to understand the change, develop authentic support, practice the message, make appropriate decisions, and reach a staffed source of help.
Senior leaders may spend weeks or months discussing a change before announcing it. They know the history, alternatives, risks, compromises, and intended outcomes.
Middle managers may receive a slide deck the afternoon before the announcement.
The next morning, employees begin asking them questions.
This gap is one of the most predictable failures in organizational change. Leadership believes the change has been communicated because the announcement was delivered. Employees experience the change through their manager, who may still be trying to understand it.
Managers do more than repeat the message
A manager is not simply a distribution channel for executive communication.
Employees ask questions such as:
- What does this mean for our team?
- Which priorities are changing?
- What should we stop doing?
- Will our roles or schedules change?
- How will this affect customers?
- What happens if the new process does not work?
- Do you believe this is a good decision?
The official announcement rarely answers all of them. The manager must interpret the change within a local context and make daily decisions that either reinforce or weaken it.
That is why managers function as a translation layer. They turn organizational direction into practical meaning.
Small details can expose large gaps
During one merger, company logos needed to be added to vehicles across multiple locations. The implementation team planned the physical process carefully. Locations received the correct materials, tools, and instructions for applying the logos straight and centered.
What we had not considered was that managers in one of the merging companies had not previously been required to display company logos on their vehicles. Managers in the other company had.
The resistance was not about installation technique. It involved status, identity, expectations, and a difference in organizational practice. Regional managers began receiving objections they had not been prepared to address.
From a project perspective, the requirement looked minor. From an employee perspective, it signaled a meaningful change. The people closest to the concern had not been given sufficient context or authority to navigate it.
Managers need their own change experience
Before managers can lead others through a change, they need an opportunity to process it themselves.
They should understand:
- Why the change is occurring
- What alternatives were considered
- What has already been decided
- What remains flexible
- How their team will be affected
- What concerns leadership expects
- Which decisions managers can make
- Where unresolved questions should go
Managers also need space to express resistance or uncertainty before they are expected to sponsor the change publicly. If they do not believe in the direction, employees will know. A script cannot conceal disbelief.
Buy-in does not require pretending the change is perfect. It means understanding the rationale, seeing a credible path forward, and being able to discuss both benefits and difficulties honestly.
Give managers time before the announcement
Whenever possible, brief managers before communicating broadly. This is not about creating a privileged group or encouraging secrecy. It is about preparing the people employees will approach first.
Use that time to:
- Walk through the decision and expected effects
- Invite questions and objections
- Identify overlooked scenarios
- Practice explaining the change in plain language
- Clarify local responsibilities
- Test frequently asked questions
- Establish escalation paths
Managers often identify practical consequences that were invisible at the executive level. Their questions improve the implementation before the organization encounters those issues at scale.
Create a command post
Managers should not feel abandoned after the launch.
For a significant change, create a visible command post or support channel staffed by people who can answer questions, resolve problems, and identify patterns. This may be a dedicated chat, scheduled office hours, a shared question log, or a cross-functional response team.
The mechanism matters less than the promise: managers will not be left on an island.
Questions should also become organizational intelligence. If several managers ask the same thing, the problem is probably not manager comprehension. The communication, process, training, or decision may need improvement.
A command post converts local confusion into coordinated learning.
Give managers appropriate authority
Nothing undermines a manager faster than holding them responsible for implementation while denying them the authority to respond.
Leaders should clarify which elements are standardized and where managers can adapt. A manager might be able to adjust sequencing, schedule additional practice, assign local support, or temporarily change workloads. Other decisions may need escalation.
Clear decision boundaries help managers respond confidently without creating conflicting versions of the change.
Keep translating after launch
Change communication does not end when the initial announcement is sent.
Managers need updated information as implementation reveals new realities. They should receive revised guidance, emerging success stories, answers to common questions, and honest acknowledgment of problems. They also need opportunities to report what employees are experiencing.
Research on merger integration and organizational change repeatedly emphasizes the importance of direct supervisors in helping employees interpret change. For example, McKinsey’s work on supporting employees through mergers recommends making the organizational story personal and relevant to the colleagues receiving it.
That work occurs most consistently through managers.
Executives set direction. Project teams design systems. Communications teams create messages. Middle managers connect all of it to the people doing the work.
Treating managers as a translation layer does not diminish leadership. It makes leadership reach the organization.
Put the idea to work
### What could this make possible for your organization?
Bring Foster + Foundry the challenge, opportunity, or question. We will help clarify a practical next step.
