The launch is not the change

A programme can launch on time, a new system can go live and every communication can be sent—while very little changes in the everyday work. Delivery matters, but change is only real when people understand what is different, can work differently and continue doing so after the programme team steps away.

That begins with specificity. “Transforming the employee experience” may sound compelling, but people need to know what they will stop, start or do differently. Managers need to understand the decisions they now own. Teams need to see how the new process fits the pressures of real work, including the difficult weeks when old habits feel faster.

Design for adoption from the start

Adoption is not the final workstream. It should shape the solution. Involve the people who do the work early enough to test assumptions and identify friction. Their role is not merely to approve a finished idea; it is to help make the change usable.

Communication should build understanding, not simply awareness. Training should reflect real scenarios, not only system navigation. Leaders should reinforce the change through their decisions and questions. If the formal message says one thing while incentives, workload or senior behaviour reward another, people will follow the stronger signal.

Measure what happens beyond launch. Are people using the new process as intended? Has the quality or speed of work improved? Where are teams creating workarounds, and what is that telling you? Early resistance is data. It may reflect uncertainty, missing capability, poor design or a genuine trade-off that was not understood.

Change becomes sustainable when the new way is built into routines, roles, measures and leadership attention. That requires continued listening and adjustment—not because the original plan failed, but because implementation reveals what a plan cannot fully predict. The launch creates a moment. Adoption creates the value.