Change management: How to actually do it?

Workplace changes land differently for every person in a team. One employee may feel energised by a new system or structure. Another may feel worried about their role, frustrated by extra workload, or unsure how to keep up.

For managers, the challenge sits in the middle of all that. You’re asked to keep work moving while also helping people make sense of what’s changing.

Change management gives that process a structure. It helps managers explain decisions clearly, involve employees early, reduce avoidable stress, and support people as they move into a new way of working. 

What change management means in practice

Change management means helping people move from the current way of working to the next one with less confusion, less avoidable harm, and a better chance of success.

That sounds straightforward, but many workplace changes stall because leaders confuse an announcement with implementation. Telling people a change will happen creates awareness, but it doesn’t automatically create understanding, trust, skill, or commitment.

A good change process helps employees answer practical questions, such as:

When these questions aren’t answered, people usually fill the gaps themselves. Rumours spread, anxiety increases, and managers end up spending more time correcting misunderstandings than leading the change.

Tip1. Start with the impact on people

Project plans usually start with dates, deliverables, and milestones. Those are useful, but they don’t show how the change will affect people’s daily work.

Before announcing a change, pause and map the human impact. Think through what will alter for each group in the team. Will workloads increase for a few weeks? Will people need to learn new software? Will reporting lines shift? Will employees lose familiar routines, team relationships, or decision-making authority? Will customers or clients experience disruption and bring that pressure back to staff?

These details matter because employees respond to the lived reality of change, not only the official version. A new process may look minor on a slide, but it may add extra steps, reduce autonomy, or leave people worried about their competence.

Managers should also consider the emotional load. People may feel relieved, angry, nervous, sceptical, or fatigued. Some may have been through previous changes that were handled badly. Others may worry about job security, performance expectations, or being left behind.

A measured response from a manager helps. You don’t need to fix every feeling. What you do need is to listen properly, avoid dismissing concerns, and separate genuine resistance from reasonable uncertainty.

Tip 2. Consult before decisions are locked in

Consultation works best when people still have room to influence how a change is put into practice. Asking for feedback after every key decision has been made can feel tokenistic, especially if employees are already under pressure.

Consultation doesn’t mean every decision becomes negotiable. It means the people affected by a change have a fair chance to raise risks, ask questions, and offer practical insight. 

Frontline employees often see problems leaders miss. They know where a process slows down, which customers may be affected, and what support will actually be useful.

Depending on the kind of change that’s being considered, you may try different consultation methods:

The follow-up also matters. Tell employees what you heard, what you’ve changed, what you’re still considering, and what can’t be changed. People are usually better able to accept a difficult decision when they can see they were treated with respect.

Tip 3. Build a one-page change plan

A change plan doesn’t need to be long to be useful. In many teams, a simple one-page plan gives managers more value than a dense document no one opens after the first week.

At a minimum, your plan should cover five areas:

• First, define the purpose. Use plain language to explain why the change is happening and what problem it’s trying to solve.

• Second, identify the people affected. Name the teams, roles, and working relationships that will change. Include indirect impacts too, such as teams who may receive more questions, extra admin, or temporary delays.

• Third, list the risks. Include operational risks, such as service delays or training gaps, and psychosocial risks, such as high workload, poor role clarity, low job control, or uncertainty around job security.

• Fourth, document the support. This may include training, time to practise, manager check-ins, written instructions, peer support, HR guidance, and EAP or employee wellbeing services.

• Fifth, decide how you’ll review progress. Choose a few practical indicators, such as employee understanding, adoption rates, workload pressure, error rates, absenteeism, pulse survey results, and feedback from team meetings.

A short plan is easier to update as the change unfolds. It also helps managers stay consistent when employees ask the same question in different ways.

Tip 4. Communicate more than once, and more clearly than feels necessary

One announcement won’t carry a team through change. People may be distracted, worried, sceptical, or focused on what the change means for their own role. Important details need to be repeated in different formats.

Clear communication answers four questions every time: what’s changing, why it’s happening, what it means for the team, and what happens next.

Try to avoid vague language. A sentence like “We’re entering a period of transformation” doesn’t tell people what to do. A clearer version would be: “From 1 September, the team will use the new client management system. The current system is causing duplicate work and reporting errors. Training will run in August, and we’ll reduce non-essential reporting during the first two weeks after launch.”

Employees also need honesty about uncertainty. Waiting until every detail is final can leave too much space for rumours. A manager can be transparent without overpromising.

For example: “We know reporting lines will change. We don’t have the final structure yet. We expect to confirm it by Friday, 18 October. Please send questions through your team lead so we can respond to common themes in writing.”

That kind of message helps because it gives people something firm to hold onto, even when not everything has been resolved.

Tip 5. Reduce psychosocial risks as the change unfolds

Managers have an important role in noticing when change is placing extra strain on people. You’re not expected to act as a therapist, but you are expected to take reasonable steps to manage work-related risks.

Common risk points during change include rising workload, unclear roles, inconsistent messages from leaders, rushed training, reduced control over work, and long periods of uncertainty. Redundancy processes, restructures, mergers, and major system changes need particular care.

Practical controls should focus on the way work is organised. Managers can pause lower-priority tasks, extend deadlines, reduce duplicate reporting, allocate time for training, clarify decision rights, and check that employees know where to get help. After a restructure, it’s worth confirming role responsibilities in writing, because uncertainty often persists after the formal announcement.

Support services also matter, though they shouldn’t be the only response. Telling people to look after themselves while leaving workloads unchanged is unlikely to work. The work itself needs attention.

A mental health day may help an employee recover from acute stress, but it won’t solve a change process that keeps creating unreasonable workload, unclear expectations, or constant disruption. Managers should view leave, EAP access, and employee wellbeing services as part of a wider support plan, not a substitute for good work design.

Tip 6. Use check-ins to spot issues early

During a change, some employees will speak up quickly. Others will wait, minimise their concerns, or try to push through until stress starts affecting their work. Regular check-ins matter greatly here, as they help managers notice issues before they become harder to manage.

Team check-ins are useful for shared issues, such as a confusing process, a training gap, or a workload bottleneck. One-on-one check-ins are better for personal concerns, such as anxiety about role changes, frustration with uncertainty, or reduced confidence after a new system goes live.

A good manager check-in doesn’t need to be long. The tone matters more than the calendar invite. Try asking thoughtful questions, such as:

• “How are you finding the change so far?”

• “What’s been harder than expected?”

• “Is anything unclear about your role or priorities?”

• “What would help you manage the next week?”

• “What do you think we should stop, pause, or simplify?”

The final question is often the most useful. During change, people are frequently asked to add new tasks before old ones are removed. That creates pressure fast. Managers who are willing to stop lower-value work send a clear message that employee wellbeing is part of implementation, not an afterthought.

Tip 7. Prepare managers before employees hear the news

Middle managers often carry pressure from both sides. Senior leaders expect them to implement the change. Employees expect them to explain it, make it workable, and respond to concerns. That’s a difficult position when managers haven’t had time to process the change themselves.

Before a major announcement, managers need a proper briefing. They should understand the reason for the decision, the expected impact, the timing, the likely questions, the limits of what they can promise, and the support available. They also need a clear escalation path for questions they can’t answer.

Briefing managers only moments before employees is risky. It leaves them unprepared for emotional conversations and makes the organisation look disorganised. Give managers time to read the material, ask hard questions, and practise how they’ll speak with their teams.

Tip 8. Continue managing after launch day

The launch date is rarely the end of a change. It’s often the point where employees start dealing with the practical consequences.

The first month after implementation should have a steady rhythm. In the first week, focus on orientation. Make sure people know what has changed, where instructions are kept, and how to raise issues. In the second week, look for friction. Ask what’s slowing people down, which steps are unclear, and what needs fixing quickly.

By the third week, check confidence. Some employees may need extra training or coaching after they’ve tried the new way of working. By the fourth week, review workload, team routines, and any unintended consequences.

A short weekly team check-in is often enough. Ask questions like: What’s working? What’s getting in the way? What support would help this week? Then act on at least one visible issue. Small fixes show employees that feedback isn’t disappearing into a spreadsheet.

Tip 9. Measure people outcomes, not only project outcomes

A change can meet its deadline and still harm morale, increase workload, or create confusion. Managers need to track both operational results and people outcomes.

Useful measures include employee understanding, training completion, adoption of new processes, workload pressure, error rates, customer or client impact, absenteeism, turnover, confidence levels, and use of support options, such as EAP or employee wellbeing services. 

Short employee pulse surveys can help, but they should be paired with real conversation.

The questions don’t need to be complicated. Try asking: “Do you understand why this change is happening?” “Do you know what’s expected of you?” “Do you have the training and support you need?” “Is anything about this change creating unnecessary stress or confusion?”

Measure before, during, and after the change where possible. A baseline helps you see what has shifted. Follow-up shows employees that the organisation is still paying attention after the announcement.

Tip 10. Know when extra support is needed

Some changes are complex, sensitive, or emotionally heavy. Restructures, redundancies, mergers, major conflict, traumatic events, and changes involving job insecurity may need support beyond the immediate manager.

That support may come from HR, work health and safety advisors, organisational psychologists, external change specialists, EAP providers, therapists, or broader employee wellbeing services. Managers should know the available pathways before employees ask for them.

For individuals, speaking with a therapist can provide a private space to process stress, uncertainty, anxiety, or loss of confidence linked to workplace change. Therapy can also support managers who are trying to care for their teams while managing their own pressure.

Seeking support doesn’t mean someone has failed to cope. It’s a practical step when change starts affecting sleep, mood, concentration, relationships, or daily functioning.

A practical change management checklist for managers

Before announcing or implementing a change, managers should be able to answer these questions clearly.

If several answers are unclear, the change needs more preparation. That may mean slowing down, improving consultation, clarifying roles, adjusting workloads, or giving managers better support before the next step.

Final thoughts

Change management doesn’t require perfect certainty. It requires honesty, structure, consultation, and care in the way decisions are carried out.

For managers, the most helpful shift is to look beyond the announcement. People need time to understand what’s changing, ask questions, practise new behaviours, and feel supported when the first attempt feels clunky. The work will go more smoothly when employees know what’s expected, why it matters, and where to turn when things feel difficult.

If workplace change is affecting your stress levels, sleep, mood, or confidence, speaking with a therapist can help you understand your response and work through the pressure in a confidential setting.