How to lead change at work: a practical playbook for managers

To lead change well, you make a decision understandable, doable and worth the effort for the people who have to live with it. In practice that means six moves: get clear yourself, translate the why, let the team shape the how, equip people and clear blockers, reinforce the new way, and adjust in the open. Tools such as internal communications software help you reach everyone with the same message, but people decide whether to change based on what their own manager says and does.

The manager's role is hard to overstate. Gallup estimates that managers account for at least 70% of the variance in employee engagement scores across business units. Change rarely arrives one at a time, either: in a 2024 Gallup survey of 18,665 U.S. employees, seven in 10 reported disruptive change in their organization in the past year. Leading change is now part of the ordinary job, not a rare project.

You may have heard that 70% of change initiatives fail, but a 2011 review in the Journal of Change Management traced five published sources of that figure and found no valid and reliable empirical evidence behind it. That matters, because a team told that most change fails has an easy reason to wait this one out.

What the evidence does show is where change breaks down. Prosci's research names five main reasons employees resist: they do not know the reason for the change, their job role changes, they fear the unknown, they lack support from or trust in leaders, and they were left out of change-related decisions. Almost all of these sit within a manager's reach.

Many teams have also learned a pattern: a change is announced with energy, the new way half-lands, attention moves on, and a year later a similar change is announced again. After watching that cycle, skepticism is a conclusion from experience, not a character flaw. Four behaviors keep it going:

• Announcing instead of explaining. A single email or all-hands treats the change as information, when people need a conversation about what it means for them.
• Deciding everything at the top. When every detail is fixed before the team hears about it, people have nothing to own.
• Stacking changes. Several initiatives land on the same team at once, with no one deciding what can pause.
• Declaring victory at launch. Support disappears on go-live day, before the new way has become a habit.

These moves fit a new tool, a reorganized team, a new process or a new strategy. Scale the effort to the change, but skip none.

1. Get clear before you talk

Before you tell your team anything, write down four things in plain language: what is changing, why now, what is not changing, and what is still undecided. If you cannot fill in all four, ask whoever made the decision before you face your team. People listen for gaps, and "I don't know why" in the first meeting is hard to recover from.

Also name the behavior you expect. "We are moving to a new CRM" is an event; "every customer call is logged in the new system the same day" is a behavior you can support and check.

2. Translate the why into your team's terms

Leaders often explain change in company terms: market pressure, cost, strategy. Your team needs the next layer down. What problem does this solve for our customers or for us? What happens if we do not change? What gets easier, and what gets harder for a while?

Then explain it again. One announcement is never enough, so plan to repeat the core message in team meetings, one-on-ones and written follow-ups over several weeks. If your team already struggles to share information well, fix that first; our guide on how to improve team communication covers the basics. Communication pays off during disruption: among employees who reported significant disruption, those who strongly agreed their leaders communicate effectively were 4.3 times as likely to be engaged and 65% less likely to feel frequently burned out.

3. Let the team shape the how

The what may be decided above you. The how usually is not. Ask the people who will do the work to design the details: the rollout order, the checklist, the way exceptions are handled, the date the old process retires.

This is the single most underused move. A longitudinal study of a reorganizing workplace found that information about the changes, confidence in coping with them and participation in the change decision process all predicted employees' openness to change. Gartner reported in 2020 that organizations engaging employees in all facets of change, rather than leading it top-down, can raise the probability of change success by as much as 24 percentage points.

4. Equip people and remove blockers

People can want a change and still be unable to do it. Give them training at the moment they need it, time to practice before the stakes are high, and someone to ask. Then remove what is in the way: duplicate reporting, a workaround that is faster than the new process, a target that rewards the old behavior.

Ask yourself what your team can stop or postpone. A change added on top of a full workload competes with everything else and usually loses.

5. Reinforce the new way

New habits fade without reinforcement. Notice the new behavior and say so, specifically and soon. Share early wins with the team, including small ones. Retire the old way on a set date so two systems do not run in parallel forever. And check that what you reward, measure and praise matches what you asked for.

6. Adjust out loud

Your first plan will be partly wrong. Hold a short check-in every week or two during the change: what is working, what broke, what we change next. When you adjust, say so and say why. A visible correction shows the change is being steered, not abandoned, and it gives people permission to report problems early.

Most managers lead changes decided by someone else, and they are often in the thick of it themselves. Gallup found in 2024 that leaders and managers are 56% more likely than individual contributors to experience extensive disruptive change in their organization. Managers also resist: in Prosci's research, participants named mid-level managers as the group they experienced the most resistance from, followed by front-line employees.

That is a reason to treat alignment as part of the job, not as loyalty theater. A workable sequence:

1. Get the reasoning, not only the decision. Ask your own manager what problem the change solves, what alternatives were considered and what success looks like. You cannot translate a reason you have not heard.
2. Raise concerns early, privately and with a fix. "I see a risk with the March date because of quarter-end. Could we pilot with two people first?" is useful. A complaint without a proposal rarely changes anything.
3. Decide what you can commit to. If the decision stands, you can still commit to making it work and reporting honestly what you learn.
4. Be honest with your team without undermining the decision. "I raised a concern about timing; we are going ahead, and I will make sure we get support for quarter-end" is truthful and keeps you credible. Faked enthusiasm is easy to spot, and so is open disdain.
5. Report back up. Pass what your team learns to the people who decided. That turns you from a messenger into a source of evidence.

Significant change comes with ambiguity: the org chart is not final, nobody knows yet which roles change. You do not need every answer, but you need a way to talk about what is unknown.

• Split known from unknown. Say plainly what is decided, what is not, and when the open questions will be settled.
• Give a date for the next update, even if it brings no news. Silence fills with rumor faster than any update.
• Share principles when you cannot share details. "Whatever the final structure, nobody loses their current client relationships without a conversation first" gives people something to hold on to.
• Shorten the planning horizon. When the long-term picture is foggy, agree on what the team does in the next two weeks and review it.
• Model steadiness, not certainty. People take their cue from how you handle the unknown. Calm, specific and honest beats confident and vague.

Trust is what carries a team through this stretch. Among employees who reported significant disruption, those who strongly agreed they trusted their organization's leadership were 4.5 times as likely to be engaged and 62% less likely to feel burned out. Gartner reported that employees with high trust have an average capacity for change 2.6 times greater than those with low trust.

Wording matters most in the first conversations. These are starting points; adapt them to your voice.

"Resistance" covers very different situations, and the right response depends on what is missing. Prosci's ADKAR Model breaks individual change into five elements: Awareness, Desire, Knowledge, Ability and Reinforcement. Use it as a diagnostic: find the first element a person lacks and work on that one.

Two cautions. Some objections are right: the person closest to the work may see a flaw the decision-makers missed, so listen for content before treating anything as resistance. And describe behavior, not people. "Raised three concerns in the meeting" is useful; "negative" is a label that ends the conversation.

Some teams push back on almost any change. Usually that comes from history, not temperament: earlier changes cost them effort and delivered little, or arrived with no warning. A few practices help.

• Name the history. "The last two tool rollouts were rough, and I understand why you're skeptical" earns more goodwill than pretending this time is different.
• Start with a pilot. Let two or three volunteers try the change for a few weeks and report back to the team in their own words.
• Keep what works. Be explicit about the parts of the current way that stay. Change feels smaller when people can see what is not moving.
• Sequence and subtract. If several changes hit the team at once, ask your manager which can wait, and stop something before you add something.
• Make progress visible. A simple tracker of what is done and what is next shows that the change is moving and that their input changed it.

Models are useful as checklists, not scripts. Pick the one that matches the question in front of you.

Kotter Inc. describes the 8 Steps for Leading Change as success factors John Kotter extracted from observing organizations, and says the firm has since evolved the linear sequence into the 8 Accelerators. The three-step model credited to Kurt Lewin has a twist of its own: a 2016 paper in Human Relations compared Lewin's writing with later accounts and argues that he never developed such a model; it took form after his death. Both are still useful vocabulary. Neither replaces the six manager moves.

• Selling instead of explaining. Enthusiasm without reasons sounds like spin. Lead with the problem, not the pitch.
• Hiding the costs. If the change makes some work harder for a while, say so. People find out anyway, and then they doubt everything else you said.
• Promising what you cannot control. "Nobody will lose their job" is a promise only some people can make. Commit only to what is yours to deliver.
• Going quiet after launch. The weeks after go-live are when support matters most and attention usually drops.

Announcements and training completions show the change was delivered, not adopted. Measuring adoption helps: in Prosci's research, 76% of participants who measured compliance with the change and overall performance met or exceeded objectives, compared with 24% of those who did not.

Adoption signals (pick two or three that fit your change):

• Share of the work done the new way, such as tickets in the new system or calls logged the same day.
• Use of the old path, such as spreadsheet edits, side channels or exceptions requested.
• Time to proficiency: how long until people are back to their usual pace.
• Errors, rework and escalations linked to the change.

Pulse items (five-point agreement scale, three to five minutes to complete):

• I understand why this change is happening.
• I know what I need to do differently.
• I have the training and time I need to work the new way.
• My concerns about this change have been heard.
• I believe this change will stick.

The first item maps to awareness, the second and third to knowledge and ability, the fourth to involvement and the fifth to trust in follow-through, so low scores tell you which of the six moves to revisit. Engagement is a different measure from contentment with the change, and the distinction matters when you read results; see employee engagement vs. satisfaction for how the two differ. If your organization already tracks employee Net Promoter Score, watch for a dip during the change, but do not use it as your only signal.

Cadence:

Software can make the mechanics of change easier. Internal communications tools let you send each team a targeted message, give managers talking points and keep questions and answers in one place. Survey tools run the pulse checks above and show results by team. A learning management system assigns role-based training and shows who has completed it.

What software cannot do is the part that decides whether the change sticks: the conversation in which a manager explains why it matters for this team, listens to an objection and changes the plan because of it. Use tools to free time for those conversations, not to replace them.