What matters most before the change starts
- Engagement turns change from passive compliance into active ownership.
- People usually resist uncertainty, weak communication, and loss of control more than the change itself.
- Line managers are the main interpreters of the change story, so they need early support.
- Measurement should combine behaviour, sentiment, and business outcomes.
- UK employers need to account for consultation, flexibility, and hybrid-working realities.
Why engagement makes or breaks change
I treat engagement as an execution layer, not a nice-to-have. If people are engaged, they ask better questions, flag risks earlier, and keep learning after the first wave of novelty fades. If they are not, leaders get polite nods, slower adoption, and a growing gap between the slide deck and the reality on the floor.
That matters because disengagement is already the norm in many workplaces. Gallup’s 2026 global workplace report puts global engagement at 20% in 2025, which tells me the challenge is not a lack of strategy documents; it is a lack of emotional connection, local ownership, and managerial consistency.
During change, that difference becomes visible fast. An engaged team will usually tell you when a new process is clumsy, when a system is slowing them down, or when a policy conflicts with how work actually gets done. A disengaged team may stay quiet until adoption fails. In practice, that means engagement is not just about morale. It is about whether the organisation has enough trust and energy to carry the transition through the messy middle.
Once you see engagement as a driver of adoption rather than an afterthought, the next question is obvious: what do people need in order to trust the change in the first place?
What employees need before they trust a change
People do not need a perfect plan as much as a believable one. The biggest trust gaps usually appear when leaders announce a change before they have explained the logic behind it, the impact on day-to-day work, and the support people will actually receive. In my experience, that is where rumours start doing the work that leadership should have done earlier.
Before trust is strong enough for commitment, employees usually look for five things:
- Clarity about why the change is happening now.
- Role impact so they know what will change in their own work.
- Voice so they can shape practical details, not just receive instructions.
- Support in the form of training, time, and manager availability.
- Fairness so the process does not feel arbitrary or political.
What leaders often underestimate is the value of saying what will not change. Stability matters. When people know which priorities, standards, or team rhythms will remain in place, they can handle the uncertainty around the new parts more effectively. That is especially important in larger organisations, where change tends to arrive in waves rather than one clean event.
There is also a human cost to vague communication. If employees are left to infer what the change means, they usually assume the worst for their workload, status, or flexibility. That is why the quality of the early message is not a branding issue; it is a trust-building mechanism. From there, the real work is sequencing the engagement effort through the life of the change.
How to keep people engaged through the change lifecycle
I prefer to treat engagement as a sequence, not an event. The conversation before launch is not the same as the conversation after go-live, and people need different kinds of reassurance at each point.
| Phase | What people need | What leaders should do | Common failure |
|---|---|---|---|
| Before launch | Context, rationale, and a sense that their experience matters | Explain the case for change, brief managers first, and test assumptions with front-line teams | A polished announcement with no room for questions |
| During rollout | Training, quick answers, and visible support | Use short check-ins, publish a clear timeline, and fix friction quickly | Too much information at once and too little follow-through |
| After go-live | Stability, recognition, and proof that feedback changed something | Track adoption, remove blockers, and reinforce the new behaviour in routine management | Declaring victory before the new way of working has stuck |
The pattern is simple: front-load honesty, maintain contact during uncertainty, and reinforce the new behaviour after the launch noise fades. I have seen teams lose confidence not because the change was wrong, but because leaders went quiet at the exact point when people needed visible attention most. That is why managers matter so much.
Why people managers carry most of the load
Managers are the translation layer. They turn strategy into day-to-day meaning, and they are usually the first people employees approach with concerns that are too practical for a town hall and too specific for an email. If the manager layer is weak, the whole change effort feels abstract.
I would never ask managers to “cascade the message” without giving them a usable kit. At minimum, they need:
- a one-page explanation of what is changing and why
- answers to the hard questions they are likely to hear
- clear boundaries on what is decided and what is still open
- a timeline for team briefings and one-to-ones
- an escalation path when they hit resistance or confusion
They also need time to process the change themselves before they are expected to coach others through it. That sounds obvious, but it is one of the most common mistakes I see. Leaders brief managers late, then expect confidence immediately. In reality, a manager who is unsure or overloaded will usually sound cautious, inconsistent, or defensive, and teams read that instantly.
The best change programmes treat managers as participants, not messengers. Once that support is in place, the next issue is whether the organisation can actually tell if engagement is improving or merely being talked about.
How to measure whether engagement is actually improving
I would rather see five useful indicators than one glossy engagement score. CIPD cautions against relying too heavily on broad composite measures because they can hide distinct problems, and I think that warning is practical rather than academic. If you flatten everything into a single number, you can miss the real blockers: poor line management, workload pressure, confusion about the new process, or lack of trust in the purpose of the change.A better approach is to track engagement in three layers:
| Measure | What it tells you | Why it matters |
|---|---|---|
| Pulse confidence | Whether people understand the change and believe it is manageable | Low confidence usually shows up before low adoption |
| Adoption behaviour | Whether the new process, tool, or habit is actually being used | Training completion is not the same as behavioural change |
| Manager activity | Whether line managers are having the conversations that keep people steady | Consistent local support is often the difference between progress and drift |
| Friction signals | Where people are getting stuck, frustrated, or slowed down | Helpdesk tickets, rework, and repeated questions reveal hidden resistance |
| Retention and absence | Whether the change is creating pressure that people are voting against with their feet | Useful as a lag indicator when change fatigue starts to build |
For the first few weeks of a transition, I prefer short pulse checks and open-text comments over long surveys. People are more candid when the questions are simple and the feedback loop is visible. The real test is whether leaders respond to the signals and then tell people what changed because of them. That kind of responsiveness keeps engagement from becoming a measurement exercise with no practical effect.
In the UK, that measurement also has to sit inside a flexible and often hybrid reality, which changes how people experience the change in the first place.
What UK organisations need to factor in
The UK context matters more than many change plans admit. CIPD’s 2025 report on flexible and hybrid working found that 74% of organisations had hybrid working in place, and employers were most likely to say the model had a negative impact on managers’ ability to lead teams effectively and on employees’ connection to organisational purpose. That is a clear warning for any change programme that depends on shared understanding, cultural alignment, or rapid behaviour change.
It also means that “one announcement to everyone” is rarely enough. A transition may need to work across offices, home-working days, shift patterns, and different levels of access to managers. If the message only lands well in the room where it was first spoken, it has not really landed at all.
There is another UK-specific point: employee voice and consultation cannot be treated as administrative extras. If a change affects flexibility, attendance, workload, or role design, people need a real chance to ask questions before the decision is frozen. In practical terms, that means building in consultation points, not just a communications campaign.
I also think UK leaders should be careful about interpreting presence as commitment. In hybrid teams, the more useful question is whether people understand the change, can work with it, and have the tools to make it succeed wherever they are located. That is where a lot of engagement work either becomes credible or falls apart.
The first 30 days are where engagement is won or lost
If I had to reduce the whole subject to one rule, it would be this: people support what they can understand, influence, and survive. The first month of a transition is where those three conditions are either built or broken.
- Write the reason for change in one plain paragraph, not a deck full of slogans.
- Brief managers before staff hear the message, so they can answer questions with confidence.
- Invite practical feedback before full rollout, especially from the people doing the work every day.
- Track adoption weekly at the start, then move to a steadier rhythm once the new behaviour is visible.
- Remove one real obstacle each week and tell people what changed because of their input.
That is the part I keep coming back to: engagement is not something you add after the change plan is written, it is part of the plan itself. When people can see the logic, influence the details, and get support from their manager, change stops feeling done to them and starts feeling built with them.
