A director I was coaching got the call on a Tuesday afternoon. The company was restructuring. Her department was being merged with another. Three of her nine direct reports would be moved to different teams. One role was being eliminated. The announcement was going out on Friday, and she was expected to communicate the changes to her team on Monday.

She hadn’t been consulted. She didn’t agree with all of the decisions. She had questions that nobody had answered yet. And in 72 hours, she would be standing in front of nine people who were looking at her face to decide whether to be scared.

This is the change leadership scenario that nobody prepares you for. Not the executive who chose the restructuring — they had time to process, to shape the narrative, to see the strategic logic. The person who needs the most support is the middle manager or director who has to translate a decision they didn’t make into their team’s daily experience, while simultaneously processing their own reaction, managing their own uncertainty, and maintaining enough composure to lead.

The Middle Manager Is the Change

Prosci’s change management research identifies one finding that should reshape how organizations think about change: the single most important factor in whether employees adopt a change is the behavior of their direct manager. Not the CEO’s announcement. Not the town hall. Not the FAQ document. The direct manager.

Employees process organizational change through a deeply personal filter: what does this mean for me, my role, my team, and my future? The person they look to for answers is not the executive sponsor who made the decision. It’s the person they see every day — the person who runs their one-on-one, who knows their career aspirations, who they trust (or don’t) to tell them the truth. If that person is visibly supportive and equipped to answer questions, the team moves through the transition. If that person is visibly anxious, evasive, or uninformed, the team stalls.

This is why change initiatives fail more often at the management layer than at the executive layer or the front line. The executive decided. The front line will ultimately adapt. The manager in the middle is the translation layer — and most organizations give them the least preparation, the least information, and the least support, while expecting them to do the most difficult communication work.

The Three Things Your Team Needs From You

When change is imposed from above, your team needs three things from you. They don’t need you to love the change. They don’t need you to pretend everything is fine. They need you to be honest, informed, and present. Here’s what each of those looks like:

1. Honesty about what you know and what you don’t. The worst thing a manager can do during a change is pretend they have answers they don’t have. Your team can detect performative confidence instantly — and it destroys trust faster than admitting uncertainty. The honest version sounds like this: “Here’s what I know. The restructuring will combine our department with the analytics team. Three of you will move to new reporting lines. I’ll have conversations with each of you individually about what that means. Here’s what I don’t know yet: the timeline for the transition and exactly what the new team structure will look like. I’ve asked those questions and I’ll share the answers as soon as I have them.” That response gives people the information they need without filling gaps with speculation, and it signals that you’re advocating for clarity on their behalf.

2. A visible commitment to protecting what you can. You may not control the change, but you control how your team experiences the transition. That means fighting for things that matter: making sure the person whose role is being eliminated gets a fair severance and genuine career support. Advocating for your team’s input on the new structure rather than accepting it as handed down. Pushing back on unrealistic timelines when they would harm your team’s ability to deliver. You don’t need to win every battle. Your team needs to see you fighting them.

3. Space for their reaction — without requiring them to manage yours. People need to process change emotionally before they can process it logically. If your team is angry, scared, or frustrated, the most useful thing you can do is let them say so without fixing it, minimizing it, or matching it with your own reaction. “I hear you. That’s a reasonable reaction. Let’s talk about what we know and what we can influence.” That response validates the emotion and redirects toward action. What doesn’t work: “I’m frustrated too,” which makes your team responsible for your feelings in addition to their own, or “This is actually a good thing,” which dismisses the experience they’re having and erodes your credibility.

How to Lead a Change You Don’t Agree With

This is the question I get asked most often in coaching during organizational change, and it’s the one with the most nuanced answer.

The first distinction is between disagreement and misalignment. You can disagree with a decision and still support the execution. This is the “disagree and commit” principle: you voiced your concerns in the appropriate forum, the decision was made, and now your job is to execute it with the same commitment you’d give to a decision you fully endorsed. Your team doesn’t need to know that you lobbied against the restructuring. What they need is a leader who’s focused on making the transition work, not one who’s subtly signaling that leadership made a mistake.

The exception is when the decision crosses an ethical line or will genuinely harm people unnecessarily. In that case, disagreeing and committing is the wrong stance — escalating, pushing back formally, or in extreme cases, declining to participate is the right one. But most organizational changes don’t fall into that category. Most are reasonable strategic decisions that you would have made differently. The discipline of supporting a decision you didn’t make is a core leadership capability, not a compromise of integrity.

What this looks like in practice: you present the change to your team without editorial commentary (“they decided” creates an us-vs-them dynamic that undermines the change). You frame it as “we’re doing this because” and share the strategic rationale as accurately as you understand it. You acknowledge what’s difficult about it without dramatizing. And you direct your team’s energy toward the things they can influence rather than the things they can’t.

The Communication Cadence That Works

During change, under-communicating is the default. Leaders share the announcement and then go quiet, hoping the absence of new information means things are going smoothly. It doesn’t. It means people are filling the information vacuum with their worst assumptions.

The communication cadence that works during a change initiative follows a simple pattern:

Communicate early, even when the picture is incomplete. People would rather hear “here’s what we know so far, and here’s what we’re still figuring out” than hear nothing and assume the worst. The fear of communicating without having all the answers keeps most leaders silent — which is the most damaging choice.

Communicate often, even when there’s no new information. “There’s no update this week, but I wanted to check in” is a communication. It tells your team you haven’t forgotten about them and that you’re paying attention. During active change, weekly check-ins are the minimum. The frequency signals that the change is being managed, not ignored.

Communicate in person (or live) for anything emotional. Role changes, team restructurings, layoffs, and significant policy changes should never be communicated by email first. The medium is the message: if it’s important enough to affect someone’s career, it’s important enough for a face-to-face conversation. Email can follow with the details, but the initial communication should happen where the person can ask questions and see your face.

Communicate the “why” at least three times more than you think is necessary. Research on change communication is consistent: people need to hear the rationale for a change five to seven times before it feels like a real explanation rather than corporate messaging. If you’ve explained the “why” once, you’ve barely started. Repeat it in different settings, different formats, and different conversations until your team can articulate the rationale back to you. That’s when it’s landed.

What Your Organization Owes You as a Change Leader

If you’re reading this as a middle manager or director being asked to lead change, it’s worth being explicit about what you have a right to expect from the leaders above you:

Advance notice before the announcement. You should never learn about a change that affects your team at the same time your team does. You need time to process your own reaction, prepare your talking points, and anticipate questions. If your leadership is announcing changes to your team without briefing you first, that’s a failure of the change process — and it’s worth naming.

The strategic rationale, clearly articulated. You can’t explain the “why” to your team if nobody explained it to you. If the best you can do is “leadership decided,” you’ve been set up to fail. Push for the strategic rationale before the announcement, and if it isn’t forthcoming, say so: “I need to explain this to my team. I can’t do that without understanding the reasoning.”

A toolkit for the conversations you’ll need to have. Talking points, anticipated FAQs, escalation paths for questions you can’t answer, and clarity on what you’re authorized to say. If the organization expects you to lead the change communication, the organization should equip you to do it. If they don’t, ask.

Three Things You Can Do This Week

1. If you’re currently leading your team through a change, schedule individual conversations with each direct report. Not a team meeting — individual one-on-ones. Ask each person: “How are you processing this? What questions do you have that haven’t been answered? What’s your biggest concern?” The answers will tell you where the resistance is, what information gaps are creating anxiety, and who needs the most support.

2. Identify the one thing about the change that you can genuinely support — and lead with it. Even in a change you disagree with, there’s usually an element that’s defensible or genuinely beneficial. Find it, name it, and use it as your anchor when communicating with your team. Authentic support for one aspect of the change is more credible than manufactured enthusiasm for the whole thing.

3. Ask your boss for the three things you’re owed: advance notice, the strategic rationale, and a toolkit. If you’re not getting them, ask directly. Not as a complaint — as a request: “I want to lead this change well. To do that, I need the reasoning, the talking points, and enough lead time to process my own reaction before I’m standing in front of my team.” Most executives will respond well to that request. They’re usually not withholding information deliberately — they just haven’t thought about what the middle layer needs.

The people side of change is what determines whether a strategically sound decision becomes a successful outcome or an expensive stall. The restructuring that makes strategic sense fails if the managers who need to carry it aren’t equipped. The system rollout that will improve efficiency stalls if nobody addressed the adoption challenge. The acquisition that creates value on paper destroys it in practice if the cultural integration isn’t managed.

We provide structured change management for organizations navigating system rollouts, M&A integration, restructurings, and leadership transitions. Our approach draws on Prosci (ADKAR) and Blanchard’s Leading People Through Change, adapted for mid-market companies where speed and people retention both matter. From readiness assessment through implementation and adoption measurement, we handle the people side so the business side can deliver. Learn about our Change Management Consulting →

Navigating a change and need help with the people side? A discovery call is the right starting point. Schedule a discovery call →