Manage resistance in real time, not in the comms plan.

Resistance usually shows up in a transformation plan as a tidy box in a risk register, with a mitigation column and a RAG status. That is where most resistance management begins and ends, on paper, before anyone has actually resisted anything.

In reality, resistance is not a risk you plan away in advance. It is a live signal that surfaces during rollout, and how you meet it in the moment decides far more than any deck you wrote beforehand.

The plan is a hypothesis. Activation is where it meets the people, and the people always have something to say.

Plans meet reality at activation

You can anticipate resistance. You cannot fully predict it. The activation phase, when the redesigned process and the new system go into live operation, is where the human response you guessed at finally arrives in its real form.

A method that expected resistance and built room to handle it holds up here. A plan that assumed everyone would simply comply unravels, usually within the first few weeks, when the gap between the slide and the shop floor becomes impossible to ignore.

The teams that struggle most are the ones who treated the plan as a guarantee rather than a starting position.

Resistance is information, not an obstacle

The reflex is to treat resistance as a problem to suppress. Push harder, mandate more, escalate. That wastes the most useful signal you have.

People resist for reasons, and the reasons are data. Sometimes the new way genuinely makes part of the job harder, and that needs fixing, not overriding. Sometimes it is fear of looking incompetent, and that needs support. Sometimes nobody explained the why.

Each kind of resistance points at a different fix, and you can only tell them apart if you are listening in real time rather than managing from a slide.

The three kinds, and the three fixes

Broadly, live resistance comes in three flavors. The first is legitimate: the new process actually has a flaw, and the people closest to the work found it before you did. The fix is to change the process, fast, and visibly.

The second is fear: people worry they will look slow or incompetent in the new way. The fix is support and cover, making it safe to be a beginner for a while.

The third is meaning: nobody connected the change to anything the person cares about. The fix is a real why, delivered by someone credible. Override the first kind and you break something that was working. Confuse the third for the first and you redesign a process that was never the problem.

Why the comms plan cannot do this

A communications plan is written in advance, in the abstract, by people who do not yet know how the rollout will actually land. It is a guess dressed as a schedule.

Real resistance is specific, local, and live. It shows up in a particular team, around a particular step, for a particular reason, on a Tuesday. No pre-written message can answer that.

Only someone present, paying attention, and empowered to adjust can. The comms plan can support that person, but it cannot replace them.

Speed of response is the whole game

When someone raises a real problem and it gets fixed quickly, two things happen. The problem goes away, and the organization learns that raising problems is worth it. That second lesson is worth more than the first.

When a real problem gets logged, deferred, and buried in a backlog, people stop raising them. They go quiet, work around the system, and you lose your best source of intelligence about what is actually breaking.

Responsiveness during activation is not just problem-solving. It is how you keep the feedback channel open, and that channel is how you steer.

Stay in the room

Activation is not a date you hit and leave. It is a period you work through. That means being on the floor while the change is happening, watching where friction shows up, and adjusting in real time.

It means fixing the genuine problems quickly, so people see that raising them was worth it, and supporting the people whose resistance is fear rather than fault. The new way needs someone to keep it standing until it can stand on its own.

Leaders who parachute in for the launch and leave for the hard part are absent for the only phase that decides the outcome.

Manage the signal, not just the schedule

The teams that get through activation cleanly are not the ones with the best comms plan. They are the ones who treated resistance as live feedback and stayed close enough to act on it.

Resistance handled well does not just get overcome. It makes the change better, because the people closest to the work were finally heard, and a process improved by the people who run it is a process they will defend.

When resistance shows up in your next rollout, resist the urge to manage it from a distance with another message. Get closer.

It is telling you exactly where the change is not working yet, and that is the most valuable thing you will learn all quarter. The plan got you to the starting line. Listening is how you actually finish.