Most change programmes are judged from the day they are announced. By then, leadership may already be behind.
A new operating model, technology platform or reporting structure can be well designed on paper, yet still falter because employees were not adequately prepared to work differently. The problem is often framed as resistance to change. In some cases, however, what looks like resistance may be uncertainty, limited capability, unclear decision rights or concern about how existing workloads will be managed.
Reactive leadership tends to respond after the announcement. Questions emerge, managers receive inconsistent messages, training is arranged late, and teams are expected to adapt while continuing to meet business-as-usual demands. This can create avoidable pressure and expose dependencies that should have been identified much earlier.
Readiness is not simply about communicating a change clearly. It includes whether people understand why the change matters, what will be expected of them, where they can access support and whether they have the practical capability to apply new processes in real working conditions.
Consider a business introducing a new customer management system. Technical training may explain the system’s functions, but readiness also requires supervisors to understand how performance expectations will change, teams to know how customer issues will be escalated, and leaders to make time for practice and adjustment.
The most resilient organisations do not treat preparation as a communication activity at the end of a project plan. They assess it as a capability requirement from the outset.
Awarditor’s People Resilience Index examines readiness alongside knowledge, application, distribution and resilience, helping organisations identify where people may need support before change becomes disruption.
Before your next announcement, ask a harder question: are your people merely informed, or genuinely ready?