Your organisation has just announced a restructure, a new system, a merger, or a strategic pivot. Your team found out roughly forty-five minutes after you did. They are looking at you for signals, and the honest answer — that you do not yet know what this means for them either — is both the most accurate thing you can say and the hardest to deliver convincingly. This is the daily reality of managing through change, and no amount of change theory fully prepares you for the human texture of it.
The frameworks that exist — Kotter’s eight steps, Lewin’s unfreeze-change-refreeze model, Fisher’s Personal Transition Curve — are genuinely useful for understanding why change is hard. They are less useful for the Tuesday afternoon when two of your team are anxious, one is quietly furious, and your senior manager has asked you to “keep people positive.” This guide is about the practical work of the manager in the middle.
Why change fails at team level — even when the plan is good
Most change failure is not caused by a bad strategy. It is caused by the gap between what the organisation communicates and what people actually experience. Organisations announce change; teams live it.
The research behind John Kotter’s eight-step model points to a finding that still rings true: organisations consistently underestimate the effort required to build a genuine sense of urgency — and then assume that communicating the change is the same thing as landing it. It is not. A well-written email announcing a restructure is processed by most people as threat, uncertainty, and noise, not as the compelling narrative its authors believe they have sent.
At team level, this plays out in a specific way. Your people have questions the organisation cannot yet answer: Will my job change? Will I still work with these people? Will I have to prove myself again? The formal communication answers the strategic questions. It almost never answers the personal ones. And the personal ones are the only ones that matter to anyone actually sitting in your team.
Your job as the manager in the middle is not to be a corporate mouthpiece. It is to be the person who takes the official position seriously, fills in the human gaps, and is honest when the gaps cannot yet be filled.
What your team goes through — the emotional arc
Understanding that resistance to change is not irrationality is probably the single most useful reframe for a manager. People who are resistant to change are usually people who have something to lose — or who believe they do. That belief may be incorrect, but it is not irrational.
John Fisher’s Personal Transition Curve maps the stages individuals typically move through when faced with significant change at work: from the initial anxiety of uncertainty, through denial, fear, and depression, eventually toward acceptance, integration, and — if things go well — confidence in the new state. The timing varies enormously by person and by the severity of the change. Some people move quickly through the early stages; others get stuck in anxiety or depression for much longer.
What this means practically:
- Not everyone will be in the same stage at the same time. The team member who appears to have accepted the change in week two may be in denial rather than genuine resolution. The one who seems most resistant in week three may be working through something real and will land well — eventually.
- The people who go quiet are often the highest-risk. Visible anger and complaint are annoying to manage, but they signal engagement. The people who disengage silently are often the ones most likely to leave or to undermine the change passively.
- You will go through the curve yourself. Managers often suppress their own processing of change — there is an implicit expectation that you are the stable point in the storm. The problem is that unprocessed uncertainty leaks out as irritability, over-control, or excessive cheerleading that nobody believes. Find somewhere — your own manager, a peer, your own reflective practice — to work through it.
Before you communicate: do your homework
There is a version of managing change that involves announcing it to your team before you have done the basic preparation. It goes badly. The team asks a perfectly reasonable question — “What does this mean for the Smith project?” — and the manager does not know. That moment damages your credibility in ways that take weeks to repair.
Before you communicate anything to your team, be clear on what you know, what you do not know, and when you will know it. This sounds obvious. It is consistently underestimated.
What you need before you call the meeting:
- The clearest possible version of what is being changed and why — in language your team will understand, not the language of the announcement document.
- A realistic sense of the timeline, even if that timeline includes uncertainty.
- An honest list of the questions you cannot yet answer.
- A commitment on when you will update people — and ideally a mechanism for them to ask questions they are not ready to raise in a group.
On the last point: some people will not ask difficult questions in a team setting. They will ask them one-to-one, or they will not ask them at all and will draw their own conclusions. A brief one-to-one round in the first week after an announcement — not a formal check-in, just a short informal conversation — gives you far better information about where people actually are than anything a group meeting will show you.
Running the announcement conversation
Assuming the announcement is yours to communicate — which is not always the case — there are a few principles that matter.
Lead with the what and the why, in that order. People need to know what is changing before they can process why it is changing. The instinct to front-load rationale — “we need to do this because of X, Y, Z” — actually makes it harder to listen, because people are still trying to work out what X, Y, and Z are leading to. State the change clearly, then explain the reasoning.
Do not oversell it. The manager who presents a restructure as unambiguously good news loses credibility immediately, because everyone in the room can see the costs even if they cannot yet articulate them. Acknowledging that this is a significant change, that there will be a difficult period, and that some things people value will be disrupted is not weakness — it is the kind of honesty that builds trust. The team will remember that you were straight with them when they eventually land in the new state and find it genuinely fine.
Tell people what will not change. In a period of significant uncertainty, anchors matter. The team’s values, its way of working together, the relationships people have built — these are often not on the table, and saying so explicitly gives people something to hold onto.
Give people time before you ask for questions. The immediate question in most group settings is not the most important one. It is the one the most confident person in the room is willing to ask publicly. The important questions emerge over days. Set up a mechanism — a shared document, a short open-door period, or a follow-up note asking people to send questions by a deadline — that captures the ones that matter.
The weeks after: when resistance peaks
The first announcement is usually not the hardest part. The hardest part is weeks three to six, when the novelty of the change has worn off, the promised benefits have not yet arrived, and the disruption to people’s daily work is at its most acute. This is the point at which Kotter’s model identifies the risk of regression — teams that appeared to be moving forward stall or slide back.
At this point, a few things help:
Visible, consistent presence. You do not have to have answers. You have to be available. The manager who disappears into their own workload during the difficult middle weeks of a change is one of the most common and most avoidable failure modes. Brief, regular contact — even a ten-minute catch-up over coffee — signals that this is still a priority and that you have not moved on.
Short-term wins that are real, not manufactured. Kotter is correct that visible progress sustains momentum — but the wins have to be genuine. Announcing a “win” that your team can see is not actually a win breeds cynicism faster than no announcement at all. If a real early win exists, name it, acknowledge who contributed to it, and be specific.
Dealing with the resistors directly and privately. There will usually be one or two people whose resistance is visible and vocal enough to affect team morale. The instinct is to manage around them or hope they come round on their own. The better approach is a direct, private conversation: not a challenge, but a genuine attempt to understand what is driving the resistance and whether there is anything legitimate in it. Sometimes there is. Sometimes the most resistant person in the room is also the one who can see a real problem with the implementation plan, and the organisation benefits from hearing it.
Not pretending the change is complete before it is. There is pressure — from above and from the exhaustion of a long change process — to call the change done and move on. Declaring victory prematurely is a trap Kotter identifies specifically, because the change has not yet been embedded in culture, process, or the way new people are onboarded. A restructure is not finished when the new org chart goes up. It is finished when the new ways of working have become unremarkable.
Your role: translator, not cheerleader
The manager in the middle of a change is asked to serve two principals simultaneously — the organisation, which needs the change implemented, and the team, which needs honest support through it. These are not always the same thing. Sometimes the organisation’s message is unrealistically optimistic, the timeline is compressed, or the rationale is weaker than the communications team’s version of it.
You cannot pretend to believe something you do not believe. Your team will know. What you can do is be honest about the limits of your own certainty, maintain genuine respect for the organisation’s direction even where you have doubts, and be a consistent source of reliable information — including “I don’t know yet, but I will find out.”
This is a harder position than pure advocacy or pure scepticism. It requires you to hold complexity with some composure, and to communicate that complexity without either frightening people or glossing over the difficult parts. It is also, done well, the thing that earns you trust you will still have when the next change arrives. And there will be a next change. There is always a next change.
Related reading
- Kotter’s 8-Step Change Model — the foundational framework for understanding why organisational change efforts stall.
- John Fisher’s Personal Change Stages — an in-depth look at the emotional arc individuals move through during change.
- Building and Rebuilding Trust — trust is the currency change runs on; this covers how to maintain and repair it under pressure.
If you manage people through change regularly and want a structured development pathway — rather than another framework to read and file — SkillsCircle (part of Accipio) offers CPD programmes built for working managers who need something they can actually use.