Restructures, new systems, new leadership and new policies all create disruption. A practical framework for communicating change, supporting people through it, and measuring whether the change actually landed.
Change is the one constant in every organisation, and the one thing most organisations do badly. Not because the change itself is wrong, but because the people side is treated as an afterthought. A new system is procured, a restructure is announced, a policy is updated, and then everyone is surprised when productivity drops and people leave. Managing change is not about preventing disruption, it is about reducing the damage and shortening the recovery.
Say why before saying what
People resist change they do not understand. Before announcing what is changing, explain why. What problem is the change solving? What happens if nothing changes? When the reason is clear and honest, people may not agree with the decision but they can at least understand it. When the reason is hidden or vague, the most generous interpretation is that management does not trust the team with the truth.
Communicate more than you think you need to
Most change communications under-share. One all-hands meeting and an email is not a communication plan. People need to hear the message multiple times, in different formats, from different voices. They need the chance to ask questions, and the answers need to be honest, including "we do not know yet" when that is the truth. Silence during a change creates rumour, and rumour is always worse than the reality.
Give people something to hold onto
Change disrupts routines, relationships and sometimes roles. The most effective change programmes identify what is staying the same and say so explicitly. The team structure may be changing, but the mission is not. The tools may be new, but the standards are not. Anchoring people to what is stable reduces the anxiety that comes with what is not.
Support the transition
Training, time and patience are the three things most change programmes under-resource. People need time to learn the new system, the new process or the new structure before they are expected to perform at their previous level. A change that goes live on Monday with training on Friday will fail. Build the transition period into the plan, and measure performance against the transition, not against the old baseline.
Measure whether it landed
A change is not complete when it is announced. It is complete when the new way of working is normal. Measure adoption, not just rollout. Are people using the new system? Are the new processes being followed? Are the old workarounds creeping back? A simple check 30, 60 and 90 days after the change tells you whether it stuck or whether it needs reinforcement. A change that nobody follows is not a change, it is a memo.