Readiness assessment in practice: how to know the operation is ready

Every project has a switch date. Few have an honest mechanism to answer whether the operation is ready for it. A readiness assessment is that mechanism, and it only works if it is allowed to come back bad.

The most common mistake

Turning readiness into a formality. If the question is "do you feel prepared" in a meeting with the sponsor in the room, everyone says yes, the report goes green, and the surprise arrives the day after go-live.

Readiness does not measure feeling. It measures evidence of capability.

What I measure

I split it into four blocks, and each has a question that can only be answered with fact:

• Knowledge. Can the person perform the task in the new system without help? Not "completed the training". Actually performed it.
• Process. Are the exceptions mapped and owned? Normal operation almost always works. What brings a go-live down is the exception with no owner.
• Tool and access. Does everyone have credentials, the right profile and the equipment the task requires? It sounds basic and it is what fails most.
• Support. Does the person know who to call in the first hour of a problem, and does that person know it is them?

Who I talk to

Never only leadership. Leadership knows the plan, and the plan is not the operation. I talk to whoever performs the task every day and, when a third party is involved, I talk to the third party. In a transportation project that means talking to carriers, who do not read internal announcements and do not attend corporate training.

What to do when the result is bad

Here is the part that has to be agreed in advance. If readiness cannot change the decision, it serves no purpose. I agree three exits with the sponsor before running it:

1. Go as is, with an explicit contingency plan for the weak point.

2. Go partially, starting with the group that is ready and phasing the rest.

3. Postpone, with a new date and clear action on what was missing.

Having all three on the table beforehand changes the conversation. Without it, a bad result turns into a debate about survey methodology rather than about the operation.

What the champion network has to do with this

A lot. The champion gives me the real signal before the form does. When four champions say in the same week that their team is uncomfortable with one specific step, that is more predictive than any aggregate percentage.

A reminder I keep repeating

Readiness is not an event. It keeps moving after the switch, which is why hypercare exists. Measuring once, the day before, and never again is the most elegant way to find out too late.