10 Change Management Activities That Move Work Forward

A change plan becomes useful when it tells leaders and managers what to do next, not when it fills a shared drive with polished slides. The activities below create the conditions people need to understand a change, make room for it, practice it, and keep moving when the first wave of energy fades.

No two changes need the exact same playbook. A new tool, a reorganization, and an operating-model shift carry different risks. Still, most successful efforts require the same essentials: a clear reason for the work, visible leadership, capable managers, honest communication, practical support, and a way to learn as the organization moves. Use these change management activities as a sequence, then scale them to the real load on your people.

1. Clarify the change and why it matters now

Start with the business decision before building the communication plan. What is changing? Why is it important now? What problem will this solve, and what happens if the organization stays where it is? Leaders need crisp answers before they ask anyone else to commit time and energy. Vague language about transformation, innovation, or efficiency will not carry a team through the hard parts.

Make the explanation specific enough for a manager to use in a team meeting. It should cover what will change, what will remain steady, and what people can expect in the next phase. That does not mean pretending every detail is settled. It means separating the decisions already made from the choices that are still open. This foundation keeps later messages from sounding like a moving target.

2. Map who is affected and what changes for them

Change is experienced through work, not through an org chart. Identify the groups affected, the routines that will shift, the systems they use, the new decisions they will make, and the moments when the change will feel most demanding. A team may be asked to learn a new platform, follow a new approval path, change a customer conversation, or let go of a familiar metric. Those are different experiences and require different support.

Use the map to identify collisions early. When one group is carrying three major shifts at once, the answer may be better sequencing, a clearer priority, or more capacity. Walt's guide to enterprise change management explains why looking across the whole portfolio matters when several initiatives are competing for the same leaders and teams.

Blank planning cards arranged in lanes to map the path of organizational change

3. Build visible sponsorship into the work

People watch what senior leaders do when a change becomes inconvenient. A sponsor who only appears in the launch email is not enough. Effective sponsors connect the change to real priorities, make choices that reinforce it, answer difficult questions in their own words, and stay present as teams begin using the new approach.

Give sponsors a practical rhythm: the decisions they need to make, the audiences they need to address, the messages they should reinforce, and the feedback they need to hear. This is not about turning leaders into spokespersons. It is about making leadership behavior consistent with the future they are asking others to build. For organizations preparing a high-stakes leadership conversation, Walt's change management keynote creates useful shared language before the work spreads through the organization.

4. Equip managers to lead local conversations

Managers are where a broad message becomes a Tuesday morning conversation. Their teams will ask what the change means for priorities, workload, performance, customers, and job security. A manager who has only received a polished deck will either repeat it without confidence or fill the gaps with guesswork.

Prepare managers with a short, plain-language narrative, the questions they are likely to hear, honest answers to what is known and unknown, and a way to escalate issues. Give them permission to make the change relevant to their own teams. The goal is not perfect consistency in every sentence. The goal is a shared direction that still respects the local realities managers understand best.

5. Create communication people can use

Communication is an activity, not an announcement. Plan a sequence of messages that answers the questions people naturally ask: Why now? What changes for me? What should I do first? Where can I get help? When will I hear more? Repeat the central message through the channels teams already trust, then vary the details for the audiences carrying different parts of the work.

Good communication also creates a way back. Listening sessions, manager check-ins, office hours, and simple feedback prompts reveal where the message is unclear or the plan is colliding with the work. Prosci's overview of change management emphasizes preparing and supporting people through a transition. That support is much more credible when people can see their questions changing the guidance they receive.

6. Give people time and support to practice

Training is only one form of readiness. People may need a demonstration, a job aid, a chance to try a new process in a low-risk setting, a manager available for questions, or room in the schedule to learn without falling behind on everything else. Match the support to the behavior that must change, not to a generic training calendar.

Make the first use of the new approach as easy as possible. Clarify where the old method stops, who can help, and what good looks like. When a change involves new technology, that also means naming expectations around quality, accountability, and escalation. Walt's keynotes and workshops help leadership teams move from abstract intent to the choices that make those expectations usable.

Three people placing wooden pieces together on a shared path

7. Remove barriers before they become workarounds

People usually do not resist a change simply because it is new. They get stuck when the new process takes longer, conflicts with an existing policy, requires a tool they cannot access, or creates a risk nobody has addressed. Ask managers and frontline teams what will be harder on a busy day, then address the biggest obstacles before expecting widespread adoption.

Keep a visible list of barriers, owners, and decisions. Some issues will be small fixes. Others will expose a real tradeoff that senior leaders need to resolve. Either way, speed matters. When teams see the organization respond to practical friction, they are more willing to give the change a fair test. When nobody responds, they build their own workaround and the intended change quietly loses momentum.

8. Reinforce the behaviors that make the change real

New habits hold when the surrounding system supports them. That can mean updating a scorecard, changing a meeting agenda, revising a handoff, recognizing a manager who is leading the work well, or retiring an old report that sends the wrong signal. Reinforcement turns a launch into an operating pattern.

Look for places where leaders still reward the old behavior. If a team is asked to use a new customer process but is measured only on the speed of the old one, the organization has delivered two conflicting instructions. Reinforcement is where stated priorities become visible choices, which is why it cannot be delegated entirely to a communications or project team.

9. Measure adoption and listen for what the numbers miss

Count activities, but do not confuse them with progress. Sending a message, holding a town hall, or completing training may be necessary, yet none proves that people are using the new way of working well. Pair activity measures with adoption signals such as usage, quality, manager observations, customer handoffs, or the time it takes to complete the changed process.

Then add listening. A dashboard may show that a new system is being used while managers are still relying on spreadsheets to make it work. A few well-run conversations can reveal uncertainty, training gaps, or policy conflicts before they become a wider problem. Gallup's research on employee resistance points to the importance of involving people in change rather than treating them as passive recipients of it. Measure the work, then pay attention to the experience behind the numbers.

10. Adapt the plan as the organization learns

A change plan should be disciplined, not rigid. Use sponsor check-ins, manager feedback, adoption data, and frontline observations to decide what needs to change next. You may need to slow a rollout, clarify a decision, add a support resource, remove lower-priority work, or repeat a message in a more useful way.

This is where many teams lose confidence. They mistake adjustment for a sign that the original plan failed. In reality, responsible leaders expect to learn once a change meets the real operating environment. The standard is not whether every detail stayed fixed. It is whether the organization kept the destination clear while improving the path people had to take to get there.

A bright meeting room prepared for a leadership feedback session

A practical starting point for the next 30 days

If the work feels large, begin with the first four activities. Clarify the case for change, map the people and behaviors affected, set a visible sponsor rhythm, and equip managers for the next conversation. Those moves expose the real gaps quickly and give the organization a stronger foundation for communication, learning, and reinforcement.

Then keep the work connected to the moment leaders are trying to create. Walt has led technology and operating transformations from executive roles including CIO, CDO, COO, and CMO. His programs for event planners, video library, and direct conversations with his team are built for organizations that need a message people can carry back into the work.

Frequently asked questions

What are change management activities?

Change management activities are the practical actions that help people understand, adopt, and sustain a new way of working. They include clarifying the case for change, preparing sponsors and managers, communicating, training, gathering feedback, removing barriers, and reinforcing the new behaviors.

Which change management activities should happen first?

Start by clarifying the business reason, the decisions already made, the people affected, and the leaders who will visibly sponsor the work. These early activities give the rest of the plan a credible foundation and prevent teams from treating communication or training as a substitute for leadership alignment.

How many change management activities does a project need?

A simple change may need only a focused sponsor plan, manager conversations, a few communications, and practical support. A larger transformation may need all ten activities in this guide, repeated across phases. The right question is not how many boxes a team can check, but what people need to make the change real in their day-to-day work.

Who should lead change management activities?

Senior sponsors own the business direction and visible choices. Change leaders coordinate the work, managers translate it for their teams, and employees provide essential feedback about what is working or getting in the way. The strongest approach gives each group a clear role instead of handing the entire responsibility to one project team.