Short answer: your job is to get a team from how things work now to how they need to work next, without everyone falling apart in the middle. Very little of that is project planning. It is saying the why far more often than feels reasonable, staying steady while people wobble, and changing the route when reality tells you to. Do those things and the change lands. Skip them and you have written a memo.

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

Change efforts almost never fail loudly. They fade. The kickoff is good, the deck is good, everybody is nodding. Six weeks later the team has quietly slid back to the old way and nobody has said a word about it. I have run sessions on this for years and the shape is the same nearly every time. It is very rarely the strategy.

It stalls because change gets managed as an event when it is a transition.

An event is a date. The system goes live, the reorg is announced, the process changes on Monday. A transition is the messy business of going from good-at-the-old-thing to bad-at-the-new-thing to eventually good again, and it carries on for weeks after your event is officially finished.

Plan only the event and the dip blindsides you. Output drops. Mood wobbles. The people who were nodding in the room start doing their real talking in the corridor. And that dip is not the change failing, it is the change actually happening. Everyone treats it as resistance to be crushed when it is a passage to be walked through.

Then there is the second one. The plan gets frozen the moment it is signed off. The ground shifts, early evidence comes in, an assumption turns out to be rubbish, and the plan is defended anyway... because changing it would look like admitting something.

It is the exact opposite. A change effort that cannot itself change is brittle. Hold the destination firm and the route loose. That is the whole trick.

Communicating change: say the why, then say it again

The biggest gap is communication, though not in the way most managers assume. You are almost certainly communicating the what and the when. New process, starts next month, here is the deck.

What gets skipped is the why, said often enough to actually land.

Because people do not resist change. They resist loss, and they resist confusion. A why they understand and believe dissolves both.

Four things that work:

• Say the why until you are sick of it. The old rule of thumb is seven times before a message sticks. You will be bored of saying it around round three. Your team will still be on round one. Keep going.
• Lead with the problem, not the shiny new thing. "Here is the mess we kept walking into" buys you far more than "here is the new tool." People accept solutions to problems they recognise.
• Say what is not changing. Uncertainty expands to fill any silence you leave. Naming the stable ground - your team, your manager, most of your actual work - shrinks the fear back to its real size.
• Make it two-way. A broadcast is not communication. Your people are already asking each other the awkward questions in the pantry. Better to answer those out loud, badly, than not at all.

Leading people through uncertainty

This is where managing change turns into leading it. In the uncertain middle, nobody on your team is looking at the plan. They are looking at your face to work out how worried they should be. Whatever you visibly do is the stability they get. So it has to be honest rather than performed, because people can smell performed from across a room.

1. Tell the truth about what you don't know. Credibility is the only currency you have here, and nothing burns it faster than a confident answer that turns out to be wrong. "Here is what's decided, here is what's still open, here is when I'll know more" beats false certainty every single time.
2. Name the loss. Every change takes something off somebody. A skill they were the best at. A routine that worked. A bit of status nobody will say out loud. Say it out loud yourself. Loss that gets acknowledged can be grieved and got past. Loss that doesn't comes back later, wearing a costume, calling itself a process concern.
3. Give people one thing to do this week. The worst place to stand in a change is helpless waiting. One concrete action gives somebody their agency back even while the big picture is still fog. Shrink the whole thing down to the next real step.
4. Let them watch you change your mind. Take in new information, in public, and adjust. It gives everyone permission to do the same, and it is the exact behaviour the change needs from them anyway.

Adapting the plan as conditions shift

Here is the bit most change-management advice quietly skips. You will never have complete information at the start, and whatever you do have will be out of date by week three. Leading change is not executing a fixed plan beautifully. It is making decent calls on partial, moving evidence and correcting course without losing the room.

So build the review points into the change itself. Decide up front when you will look at early evidence and what exactly would make you change your mind. Then watch hardest for the signal that does not fit the pattern you expected, because that is almost always reality trying to tell you something.

And keep the destination and the route separate, in your head and out loud. A team will happily follow a leader who says "the goal holds, the path changed, here is why." They cannot follow one who insists the original path is fine while everyone can see it is on fire.

Handling resistance without a fight

Resistance is hardly ever defiance. It is information turning up in an annoying package.

The person digging their heels in usually has one of three things you need. Context you forgot to give them. A genuine hole in the plan you haven't spotted. Or a loss nobody has acknowledged, which is not a logic problem and will not respond to a better slide.

So treat it as a diagnostic instead of an obstacle, and ask what they can see that you can't. Your loudest sceptic is often one taken-seriously objection away from becoming your most credible advocate. Which is a much better outcome than winning the argument.

Leading change is a skill you build by practising it

Now notice something about everything above. Almost none of it is knowledge. You already knew to say the why. You already knew to adapt the plan. Nobody reading this page is learning that for the first time.

The gap is not information. It is behaviour under pressure. And you cannot read your way into different behaviour.

What we are really talking about is learning agility - acting well on incomplete, moving information, and updating when the evidence contradicts you. That is the muscle. Like every muscle, it grows on reps, not on theory.

Which is the whole idea behind how I run this. Rather than teaching managers about change in the abstract, I put them inside a situation where the information genuinely is incomplete and shifting. They commit. They get contradicted. They adapt, or they don't and the room watches. Then we debrief what their instincts actually did, as opposed to what they would have told you they'd do. The method is not complicated. Practise the behaviour, then make it visible enough to change.

The clearest one is Planetfall. Teams land on an alien planet with nowhere near enough data and have to keep deciding anyway. Which is a much better rehearsal for a reorg than it sounds.

Frequently asked questions

Basics

What is change management for a manager?
Getting your team from how things work now to how they need to work next, and keeping everyone functional through the bit in between. Much less about the project plan than people expect. Much more about saying the why, absorbing other people's fear, and changing the route when the ground moves.

What is the difference between change management and leading change?
Change management is the structured half. Plan, milestones, comms schedule. Leading change is the human half. Holding people steady through the dip, naming the loss, adapting when reality disagrees with you. You need both. Most managers do the first beautifully and skip the second entirely.

Common problems

Why do most change efforts fail?
Because they get run as an announcement instead of a transition. The why gets said once. The dip in performance and mood catches everyone off guard. Resistance gets read as defiance. And the plan is frozen the day it is approved, so nobody adjusts when the evidence turns.

How do I handle someone who keeps resisting?
Treat it as information, not opposition. They usually have missing context, a real hole in the plan, or a loss nobody has acknowledged. Ask what they can see that you can't. Taking one objection seriously is often what turns your loudest sceptic into your best advocate.

Building the skill

How do you lead a team through uncertainty?
Be honest about what you don't know. Name what people are losing. Give everyone one concrete thing to do this week so nobody is stuck waiting. Repeat the why. And let them see you change your own mind when the evidence changes, because that is the permission slip they are waiting for.

Can leading change actually be trained?
Yes, because it is a behaviour rather than a body of knowledge. You build it the way you build anything under pressure. Rehearse it somewhere the stakes are fake but the feelings are real, then get honest feedback on what you actually did.

Related reading

• Serious games for leadership development: the complete guide
• Planetfall: the learning-agility simulation
• The Put The Player First framework

See the games Write to me

With love from Bengaluru, this is Arvindh saying over and out.