The meeting ends, the deck closes, and you walk out holding a change you didn’t choose. A reorg. A new tool. A policy that lands on Monday. Nobody asked your opinion, and now you’re the one who has to sell it to a team that will look at you and ask, “Wait, why are we doing this?”
That gap is where most change management actually happens. And it’s the part the famous frameworks skip.
Kotter’s 8 steps and Prosci’s model are written from the change office, the altitude where someone designs the rollout, sets the timeline, and crafts the messaging. They’re useful. But they assume the person delivering the change helped decide it. You usually didn’t. You’re the middle manager handed a decision from above, expected to carry it down, often without the full reasoning and sometimes without your own buy-in.
This post is about that job. Not the strategy of change. The execution of a change you’d never have picked yourself.
What is change management for a manager in the middle?
Change management for a manager is the work of translating a decision made above you into something your team can actually do. Leadership decides the what. You own the how it lands.
That makes you the translation layer. The plan exists on a slide somewhere, but your team doesn’t experience the slide. They experience you: how you explain it, whether you flinch when they push back, and what you do when the launch hype fades and the work gets hard.
The frameworks aren’t wrong. They just stop at the org level, and the manager is left holding everything they don’t cover: the questions you can’t answer yet, the resentment from someone who’s been here longer than you, and the slow drift back to the old way three weeks in. The rest of this is how to handle each of those.
How do I get the real “why” before I cascade it down?
Go up before you go down. Before you say a word to your team, get the actual reasoning from whoever handed you the change.
You need three things from that conversation. The real problem this change solves. What happens if nothing changes. And which parts are fixed versus still open to input. A reorg framed as “we’re aligning to customer segments” means nothing to your team until you can say what’s broken about the current setup and what it costs to leave it alone.
Most managers skip this step because asking feels like dissent. It isn’t. It’s the difference between cascading a decision and parroting a slogan. Your team can tell the difference instantly, and the slogan version destroys your credibility on day one.
The uncomfortable part: sometimes you ask for the why and there isn’t a good one, or nobody can give it to you. That’s real information. A change you can’t explain isn’t ready to cascade, and the honest move is to go back up and say so, in private, before you stand in front of your team with nothing.
Managing up well is a leadership skill in its own right. If you want a structured read on where yours stands, the leadership self-assessment is a useful place to start.
What do I say when I don’t agree with the change either?
Separate your private opinion from your public job, and be honest about both without undermining the decision. This is the trap that catches the most managers, so it’s worth slowing down.
You have two real options, and a fake one. The fake one is venting to your team, the “look, I know this is dumb, but they’re making us” routine. It feels like solidarity. It’s actually you handing your team permission to disengage while keeping your own hands clean. They’ll remember that you bailed on them the first time it got hard.
The two real options are these. Before the decision is final, push back upward with specifics, in private, hard. After it’s final, you commit to running it well even if you’d have voted no. Committing doesn’t mean faking enthusiasm. Your team can smell a forced sell. It means you say something like, “This wasn’t my call, and I had questions too. Here’s what I asked, here’s what I learned, and here’s why we’re going to give it a real shot.”
That sentence does a lot of work. It’s honest, so you keep your credibility. It models disagreeing without sabotaging, which is exactly what you need from them. And it draws a clear line: opinions were welcome before the decision, execution is the job now.
The skill underneath this is adapting to change while staying true to what you actually think. It’s one of the harder balances in management, and it’s learnable.
How do I handle resistance from people who outrank me in tenure?
Treat the senior holdout as a partner, not an obstacle. The person who’s been on the team eight years and is quietly unimpressed with your reorg is not your enemy. They’re your most valuable, most dangerous ally.
Valuable because their resistance usually carries real history. They’ve watched changes like this one fail before, and they often know exactly why. Dangerous because the rest of the team watches them. If the senior IC checks out, half your floor checks out with them, and no launch email outranks that.
So go to them first, privately, before the all-hands. Three questions do most of the work:
| What to ask | What you’re actually learning |
|---|---|
| ”You’ve seen changes like this before. What went wrong last time?” | The failure modes the rollout plan ignored |
| ”What would you lose if this goes through as planned?” | The real, specific cost driving the resistance |
| ”If you were running this, what would you change?” | A way to give them ownership instead of a target |
That last one matters most. People who help shape a change rarely fight it later. Give your senior holdout a visible role, a piece of the rollout they own, and you convert your biggest risk into your loudest advocate. Resistance is rarely stubbornness. It’s almost always information you didn’t have yet.
This is also where you lean on the team’s strengths rather than against them. Not everyone will be on board at the same pace, and that’s normal. The managers who do this well work with people’s real concerns instead of steamrolling them, and they stay calm while doing it.
How do I carry the emotional load without burning out?
Name it, manage it, and don’t try to absorb it silently. A change you didn’t choose puts you in a strange spot: you’re expected to be the steady one for your team while you’re processing your own uncertainty about it.
That load is real, and pretending it isn’t is how managers crack mid-rollout. The pattern is familiar: the manager holds it together in every team meeting, then quietly runs themselves into the ground because they’ve got no outlet and no one above them is checking. You can’t pour calm into your team from an empty tank.
Two things help. First, give yourself one place to be honest about the change that isn’t your team. A peer manager, a mentor, a coach. Somewhere you can say “this is hard and I’m not sure about it” without it becoming team-facing. Second, watch your own reactivity. The day you’re snapping at questions is the day your team learns the change isn’t safe to ask about. Staying emotionally steady through change is a skill, not a personality trait, and it’s the one that keeps the rest from collapsing.
How do I make the change stick after the launch email fades?
Build it into the routines people already have. The launch is the easy part. Week one runs on novelty and leadership attention. Week four is where changes quietly die, when the new tool sits unused and the old workflow creeps back because nobody’s watching anymore.
Sustaining a change is less about motivation and more about plumbing. The change has to show up in the routines that were already going to happen:
- Put it in your one-on-ones. Ask how the new way is going, specifically, not as a throwaway line.
- Bake it into how work gets reviewed. If the old process still gets work approved, the old process wins.
- Make the new way the path of least resistance. People revert because reverting is easier. Close that gap.
- Catch quiet reversion early. Around week three you’ll see the first slides back. Name it kindly and immediately, before it becomes the norm again.
Phasing helps here too. Breaking a big change into stages with small, visible wins keeps momentum alive long after the announcement, and it gives you checkpoints to adjust before problems compound. Celebrate the early wins out loud. Not as a morale gimmick, but because people need proof the change is producing something, or they’ll conclude it was pointless and drift back.
The honest test of whether a change stuck: come back in two months and see if anyone still thinks about it. If it’s just how things work now, you did the job the framework couldn’t.
How this looks across a few common changes
The middle-manager job changes shape depending on what landed on your desk. A quick map:
| The change you were handed | Where the real friction sits | Your first move |
|---|---|---|
| Reorg or team merge | People fear lost status, relationships, and clarity on who does what | Get clarity on new roles fast, then have the hard conversations one-on-one before the group hears anything |
| New tool or system | The old way still works, so adoption stalls | Make the new tool the only way the work gets reviewed and approved |
| New policy from above | Team reads it as distrust or extra surveillance | Get the genuine reason, name the concern out loud, don’t pretend it’s nothing |
| Leadership change | Uncertainty about whether everything’s about to be redone | Hold steady, protect the team from churn, don’t speculate about what the new boss will do |
None of these run on the org chart. They run on whether one manager, you, can translate intent into reality for a small group of real people who didn’t choose this either.
Where Merlin fits
If you’re staring down a change right now, talking it through helps more than reading about it does. Merlin is Risely’s AI coach, and managers use it to rehearse exactly these moments: the all-hands where you explain a decision you have questions about, the one-on-one with the senior holdout, the honest “this wasn’t my call” sentence you can’t quite phrase yet.
It lives inside Slack and Microsoft Teams, so you can run a quick rehearsal before the meeting instead of winging it. It’s the kind of practice the change office can’t give you, because they’re not the one in the room when your team pushes back.
The job the frameworks leave to you
Kotter and Prosci are right about the org-level moves. But none of them stand in your meeting and field the question you can’t answer. That’s your job, and it’s the one that decides whether the change actually happens.
Get the real why before you cascade it. Be honest when you disagree without torching the decision. Turn your senior holdout into a partner. Carry the emotional load without hiding it. And build the change into the routines that outlast the launch email.
Do those five things and you’ve done what the frameworks structurally can’t. If you want to go deeper on the leadership skills underneath all of this, our guide to leadership development programs is a good next read. And when you’ve got a specific change to deliver this week, practice the hard conversation with Merlin before you have it for real.
Frequently asked questions
How do I manage a change I disagree with? Separate your private opinion from your public job. You can voice the disagreement upward, in private, with specifics. But once leadership has decided, your team needs you to deliver it with a straight face, not to undermine it. You don’t have to pretend you love it. You do have to commit to running it well and to surfacing real problems as data, not as I-told-you-so.
What do I do when I can’t explain the why behind a change? Go back up before you go down. Ask whoever handed you the change for the actual reasoning, the problem it solves, and what happens if nothing changes. If they can’t tell you, that’s a signal the change isn’t ready to cascade. Don’t invent a why or parrot a slogan. Tell your team what you know, what you don’t, and that you’re getting answers.
How do I handle resistance from someone who outranks me in tenure? Treat the senior holdout as a partner, not an obstacle. Their resistance usually carries real institutional knowledge about why past changes failed. Meet privately, ask what they’d lose and what they’d protect, and give them a visible role in shaping the rollout. People who help build a change rarely fight it later.
How do I make a change stick after the launch email fades? Build the change into the routines people already have. Bake it into one-on-ones, status updates, and how work gets reviewed, so it stops being an event and becomes the default. Watch for quiet reversion in week three or four and name it early. A change only sticks when doing it the new way is easier than going back.
What is the manager’s role in change management? The manager is the translation layer between leadership intent and team reality. Frameworks like Kotter and Prosci set the org-level plan, but the manager is the one who explains the change to real people, fields questions the plan didn’t anticipate, absorbs the emotional load, and decides daily whether the change lives or dies on their team.