Readiness is desire and ability, not a training deck.

A training session a week before go-live is the most common substitute for change management, and one of the least effective things an organization can do with its money.

It checks a box. It feels like preparation. And it almost never produces the thing it is supposed to produce, which is people who actually work the new way once the launch energy fades.

The training is not the problem. The belief that training is the whole job is the problem.

Awareness is not adoption

Knowing a change is coming is not the same as wanting it, and neither one is the same as being able to do it. These are different states, and most rollouts only ever address the first.

People can sit through every session, pass the quiz, nod in all the right places, and still slide straight back to the old way the moment the pressure is off. Attendance is not behavior.

A full training room tells you people showed up, not that anything changed. The gap between knowing and doing is exactly where most transformations quietly fail.

The question nobody answers

The hardest question in any change is also the quietest one. What is in this for the person you are asking to work differently?

If that never gets answered, no amount of instruction lands. People are not resisting because they are slow. They are resisting because, from where they sit, the change makes their job harder, or riskier, or simply different for no reason they can see.

Until you address that, you are training people to comply, not to adopt. And compliance evaporates the moment nobody is watching.

Desire and ability, in that order

Real readiness is built on two things. Desire, the genuine want to make the change, and ability, the actual skill and capacity to do it. Training only touches the second, and only if the first is already there.

Build desire by making the why personal and credible, not corporate and abstract. Build ability with support that lasts past launch, not a one-time download.

Skip the desire and the ability never gets used. Skip the ability and the desire curdles into frustration. You need both, and you need the desire first, because no one builds a skill they do not want to use.

Make the why personal, not corporate

The reason a change matters to the enterprise is rarely the reason it will matter to the individual. A line about strategic alignment does nothing for the person whose daily work is about to change.

Readiness means translating the why down to the level of the actual job. What gets easier for this person. What stops being a headache. What they will be able to do that they could not before. If you cannot answer that for each affected role, you have not done the work.

People adopt changes that make their own work better. They tolerate changes imposed for reasons that only matter upstairs, and tolerance is not adoption.

Ability has to outlast the launch

The one-time training session fails partly because skill does not form in a single sitting. People learn the new way by doing it, getting stuck, and having support available at the moment they are stuck.

That means the ability side of readiness is not an event before go-live. It is a presence after it: people who can answer the real question at the real moment, not a recording of a session from three weeks ago.

Support that fades the day after launch leaves people to fail quietly, and quiet failure is how the old way comes back.

Why this is the phase that gets cut

Readiness work is invisible until it is missing. It does not produce a deliverable you can point to in a steering review, so when the timeline tightens, it is the first thing to get compressed into a single session near the end.

Then activation becomes a fight, because the organization was never actually made ready. The cost of skipping readiness does not disappear. It just moves to go-live, where it is far more expensive and far more public.

What looks like saved time in the plan is borrowed time, repaid with interest during the hardest weeks of the rollout.

Align before you activate

The work of building sponsorship and genuine human readiness has to happen before the change goes live, not alongside it as an afterthought.

Get it right and the change has somewhere to land. People want it and they can do it, so activation is a matter of support rather than struggle. Get it wrong and you are pushing a system onto people who never had a reason to catch it.

Alignment is the difference between a launch that the organization meets halfway and one it merely endures.

So before your next go-live, look past the training schedule and ask the real questions. Do these people want this? Can they actually do it, with support that lasts?

If you are not sure, you are not ready, and a deck will not make you ready. Readiness is built in the weeks before, in desire and ability, or it is not built at all.