How is leading change a skill you can practise?

Leading change is learning agility: acting well on incomplete and shifting information, and updating your plan when the evidence contradicts it. That is a behaviour, not a fact, so you build it by doing it under safe pressure and getting feedback, not by reading another framework. Simulations and serious games let managers rehearse adapting under uncertainty before the stakes are real.

Change Management for Managers: Leading Change Well

Q: What is change management for a manager?

For a manager, change management is the day-to-day work of taking a team from how things are done now to how they need to be done next, while keeping the people functional through the uncertainty in between. It is less about the project plan on the slide and more about absorbing fear, answering the real questions, and adjusting the route as conditions shift on the ground.

Q: Why do most change efforts fail?

Most change efforts stall because they are managed as a one-time announcement instead of a transition people have to live through. Leaders communicate the what and the when but skip the why, underestimate the dip in performance and morale, and treat resistance as defiance rather than as missing information or unaddressed loss. The plan is also usually frozen, so when reality contradicts it, nobody adapts.

Q: How do you lead a team through uncertainty?

Lead through uncertainty by being honest about what you do and do not know, naming the loss people are feeling, and giving them something concrete to act on this week so they are not stuck waiting. Repeat the why far more than feels necessary, make small decisions visible, and let the team see you change your own mind when the evidence changes. Stability comes from your behaviour, not from pretending you have all the answers.

Short answer: Change management for managers is the work of moving your team from how things are done now to how they need to be done next, while keeping people functional through the uncertain middle. Most of it is not project planning. It is communicating the why far more than feels necessary, leading people through the dip in confidence that every change creates, and adapting your plan as conditions shift instead of defending a route that reality has already contradicted. Do those four things well and the change lands. Skip them and you get a memo nobody acts on.

Key takeaways

The job	What it actually means	The failure mode
Communicate change	Repeat the why, not just the what and when	One announcement, then silence
Lead through uncertainty	Name the loss, give people something to do this week	Pretending you have all the answers
Adapt the plan	Update the route when evidence contradicts it	Frozen plan, defended past its expiry
Handle resistance	Treat it as missing information or unaddressed loss	Treating it as defiance

Why change efforts stall

Most change efforts do not fail loudly. They fade. The kickoff is energetic, the deck is good, and then six weeks later the team has quietly drifted back to the old way because nothing made the new way stick. After running leadership sessions on exactly this for years, the pattern is almost always the same, and it is rarely about the strategy being wrong.

Change stalls because it gets managed as an event instead of a transition. An event is a date on a calendar: the new system goes live, the reorg is announced, the process changes Monday. A transition is the messy human passage from competent-at-the-old-thing to competent-at-the-new-thing, and it runs for weeks after your event is technically done. Managers who only plan the event are surprised by the dip that follows: productivity drops, morale wobbles, and the people who were nodding in the room start raising objections in the corridor. That dip is not a sign the change is failing. It is a sign the change is real. The mistake is treating it as resistance to be crushed rather than a passage to be led.

The second reason efforts stall: the plan is frozen the moment it is approved. Conditions on the ground move, early evidence comes in, a key assumption turns out wrong, and yet the plan is defended as if changing it would be an admission of failure. It is the opposite. A change effort that cannot itself change is brittle. The managers who land change well are the ones who hold the destination firm and the route loose.

Communicating change: say the why, then say it again

The single most common gap is communication, and not in the way managers expect. You are probably communicating the what (here is the new process) and the when (it starts next month). What gets skipped is the why, repeated often enough to actually land. People do not resist change. They resist loss, and they resist confusion. Both are dissolved by a why they understand and believe.

A few things that work in practice:

Over-communicate the why. The rule of thumb leaders quote is that a change message needs to be heard seven times before it sticks. You will be bored of saying it long before your team is done hearing it. Keep going.
Lead with the problem, not the solution. "Here is the pain we kept hitting" earns more buy-in than "here is the new tool." People accept solutions to problems they recognise.
Be specific about what is not changing. Uncertainty expands to fill silence. Naming the stable ground ("your team, your manager, your core work stays the same") shrinks the fear to its actual size.
Make it two-way. A broadcast is not communication. Create a real channel for the questions people are already asking each other privately, and answer the uncomfortable ones out loud.

Leading people through uncertainty

This is where managing change becomes leading change. During the uncertain middle, your team is not looking at the plan. They are looking at you to decide how worried to be. Your visible behaviour is the stability they get, so it has to be honest, not performed.

Tell the truth about what you do not know. Credibility is the currency of change, and nothing burns it faster than confident answers that turn out to be wrong. "Here is what is decided, here is what is still open, here is when I will know more" beats false certainty every time.
Name the loss. Every change asks people to give something up: a skill they were good at, a routine that worked, a bit of status or comfort. Say it out loud. Acknowledged loss can be grieved and moved past. Unacknowledged loss leaks out as resistance.
Give people something to do this week. The worst position in a change is helpless waiting. One concrete action restores a sense of agency even when the big picture is still foggy. Shrink the change to the next real step.
Show your own adjustment. Let the team see you take in new information and change your mind. It gives them permission to adapt too, and it models the exact behaviour the change requires.

Adapting the plan as conditions shift

Here is the part most change-management advice underplays. You will almost never have complete information when you start, and the information you do have will change as you go. Leading change is not executing a fixed plan flawlessly. It is making good decisions on partial, shifting evidence and correcting course without losing the room.

Practically, that means building review points into the change itself. Decide in advance when you will look at early evidence and what would make you adjust. Watch for the signal that does not fit your expected pattern, because that is usually where reality is trying to tell you something. And separate the destination from the route in your own head and out loud, so that changing the route reads as competence, not as the change collapsing. A team can follow a leader who says "the goal holds, the path just changed, here is why." They cannot follow one who pretends the original path is still working when everyone can see it is not.

Handling resistance without a fight

Resistance is almost never simple defiance. It is information arriving in an inconvenient form. The person digging in usually has one of three things you need: a piece of missing context you forgot to share, a real flaw in the plan you have not seen yet, or an unaddressed loss that has nothing to do with logic. Treat resistance as a diagnostic, not an obstacle. Ask what they are seeing that you are not. Sometimes you convert your loudest sceptic into your most credible advocate simply by taking their objection seriously enough to either answer it or act on it.

Leading change is a skill you build by practising it

Notice that almost none of the above is knowledge. You already know you should communicate the why and adapt the plan. The gap is not information, it is behaviour under pressure, and behaviour is not changed by reading. What we are really describing is learning agility: the capacity to act well on incomplete, shifting information and to update your plan when the evidence contradicts it. That is the core muscle of leading change, and like any muscle it grows through reps, not theory.

This is the thinking behind how we run leadership development at Put The Player First. Instead of teaching managers about change in the abstract, we put them inside a decision environment where the information is genuinely incomplete and shifting, let them feel what it is to commit, get contradicted, and adapt, and then debrief what their instincts actually did under pressure. The method behind it is simple: you practise the behaviour you want to build, then make it visible enough to change.

The clearest example is Planetfall, a simulation where teams land on an alien planet by gathering and acting on incomplete data, building exactly the learning agility leading change demands: deciding under uncertainty, and adapting when the evidence contradicts the plan they walked in with.

Get practical leadership and facilitation notes by email

One short email when there is something worth using: a technique for leading change, a debrief method, or a behind-the-scenes look at a real session.

Frequently asked questions

Basics

What is change management for a manager?
It is the day-to-day work of taking a team from how things are done now to how they need to be done next, while keeping people functional through the uncertainty in between. Less about the project plan, more about communicating the why, absorbing fear, and adjusting the route as conditions shift.

What is the difference between change management and leading change?
Change management is the structured side: plan, milestones, comms schedule. Leading change is the human side: holding people steady through the dip, naming loss, and adapting when reality contradicts the plan. You need both, but managers usually over-invest in the first and skip the second.

Common problems

Why do most change efforts fail?
Because they are run as a one-time announcement instead of a transition people have to live through. Leaders skip the why, underestimate the dip in performance and morale, treat resistance as defiance, and freeze the plan so nobody adapts when the evidence changes.

How do I handle someone who keeps resisting?
Treat the resistance as information. The person usually has missing context, a real flaw in the plan, or an unaddressed loss. Ask what they are seeing that you are not. Taking the objection seriously is often what converts a sceptic into an advocate.

Building the skill

How do you lead a team through uncertainty?
Be honest about what you do and do not know, name the loss people feel, and give them one concrete thing to do this week so they are not stuck waiting. Repeat the why, make small decisions visible, and let the team see you update your own thinking when the evidence changes.

Can leading change actually be trained?
Yes, because it is a behaviour, not a body of knowledge. You build it the way you build any skill under pressure: by rehearsing it in a safe environment and getting feedback. Simulations and serious games let managers practise deciding and adapting under uncertainty before the stakes are real.