Most organizations don’t fail at change because they picked the wrong strategy. They fail because the people expected to carry out that strategy never truly got on board. Research from McKinsey consistently shows that roughly 70% of change initiatives fall short of their goals, and the root cause almost always traces back to employee resistance and lack of leadership alignment, not flawed planning.
If you’re searching for change management best practices that go beyond theory, you’re already asking the right question. The gap between a well-designed change plan and one that actually transforms how a team operates is enormous. It’s the difference between a memo people skim and a mission people own.
That gap is exactly where Robyn Benincasa’s work lives. As a world champion adventure racer, veteran San Diego firefighter, and founder of a leadership consulting practice built on real-world high-stakes teamwork, Robyn has spent decades studying what makes groups of people commit to hard pivots, not because a slide deck told them to, but because they believe in the team carrying it out. Her framework has helped organizations across industries like pharmaceuticals, finance, and aerospace navigate mergers, break down silos, and sustain momentum through major transitions.
This article lays out 11 change management practices drawn from frontline experience, not just boardroom theory, so you can build transitions that hold up long after the initial rollout excitement fades.
1. Define the why and rally people around it
Before you send a single announcement or hold your first town hall, you need to answer one question clearly: why is this change happening, and why does it matter beyond cost savings or efficiency gains? People don’t resist change itself. They resist change that feels arbitrary or disconnected from something they care about. When you ground an initiative in genuine purpose from the start, you give people a reason to engage rather than simply wait for the disruption to pass.
Turn the business case into a clear purpose
Most executives can articulate the business case for a change. Fewer can translate that case into a purpose that resonates with someone on the shop floor or in a customer-facing role. Your job is to bridge that gap. Take the financial rationale and convert it into a statement that answers: what does this change make possible that wasn’t possible before? That statement becomes the foundation for everything your communication strategy builds on, and it needs to survive skeptical questions in a hallway conversation, not just sound good in a boardroom.
A clear purpose is not a slogan. It is a specific answer to "why are we doing this" that holds up under pressure and honest pushback from the people most affected.
Make the purpose personal for each impacted group
A single overarching message rarely lands equally across a workforce with different roles, concerns, and daily realities. You need to segment your audience and translate the core purpose into language that speaks to each group’s specific situation. A sales team cares about how a new system affects their quota attainment and customer relationships. An operations team cares about workflow disruption and learning curves. Identify what each group stands to gain and lose, and build your messaging around those realities rather than offering generic reassurance that everything will be fine.
Keep the message consistent from kickoff to sustainment
One of the most common failures in change management best practices is message drift. Leadership sends a strong opening statement, then updates slow down, rumors fill the vacuum, and people construct their own narratives. You need to reinforce the core purpose at every project milestone, not just at launch. When leaders, managers, and project team members all deliver the same foundational reasoning in their own authentic words, the purpose becomes something your organization genuinely internalizes rather than begrudgingly tolerates.
2. Secure active, visible executive sponsorship
Research from Prosci consistently identifies active and visible executive sponsorship as the single most critical factor in change success. Yet most organizations treat sponsorship as a title rather than a role. Signing off on a project charter is not sponsorship. Showing up at the kickoff meeting is not sponsorship. People watch leaders during uncertainty, and what they see either builds confidence or confirms their suspicion that the change is not truly serious.
Pick the right sponsor and define their job
Your sponsor needs real authority over the people and resources affected by the change, not just a senior title. A sponsor who lacks the power to remove roadblocks or make final calls creates bottlenecks that frustrate everyone downstream. Define their role in writing: what decisions are theirs, how often they engage with the team, and which stakeholder relationships they personally own.
The right sponsor is not the busiest executive who says yes. It is the leader with the right authority, the right relationships, and the genuine belief that this change needs to happen.
Equip sponsors with talking points and a cadence
Most sponsors want to lead well but lack structured support for doing so. Build a simple communication cadence for your sponsor: what to say at each phase, which audiences need to hear from them directly, and how to respond to common pushback. Prepared leaders communicate with more consistency and confidence.
Hold sponsors accountable with simple metrics
Track whether your sponsor is actually showing up. Visible participation metrics like town hall attendance, one-on-one conversations with skeptical leaders, and timely decision-making give you objective data to work with and reinforce that sponsorship is a real job, not a ceremonial one.
3. Use a structured change approach from day one
Improvising your way through a major transition is one of the fastest routes to confusion and lost trust. A structured approach gives your team a shared language and a repeatable process so that decisions, activities, and resources all point in the same direction. Without it, change management best practices become a loose collection of good intentions that never add up to a coherent plan.
Choose a framework and scale it to the change
Several proven frameworks exist, from Prosci’s ADKAR model to Kotter’s 8-Step Process. Your job is not to pick the most sophisticated one but to select a model your team will actually use and then scale it to match the size and complexity of your initiative. A small process update does not need the same machinery as a company-wide system rollout. Match the tool to the task, and you avoid both under-managing and over-engineering.
A framework is only useful if the people running the change understand it well enough to explain it to someone who has never heard of it.
Build a change plan that matches the project plan
Your change plan and your project plan need to run side by side, not sequentially. When training activities, communication milestones, and readiness checks align with technical go-live dates, you eliminate the common failure mode where systems go live but people are not prepared to use them. Build a single integrated timeline that treats the human side of change as equal to the technical side.
Set decision rules so you do not improvise under stress
Before pressure hits, define who makes which calls. Clear decision rights prevent the paralysis that stalls initiatives at the worst possible moments. Document your escalation path, your risk thresholds, and your criteria for delaying a go-live so your team acts on pre-agreed logic rather than reacting emotionally when things get difficult.
4. Map impacts and stakeholders before you communicate
Sending communication before you understand who is affected and how is one of the most common mistakes in change management best practices. People immediately ask "what does this mean for me?" and if your messaging cannot answer that specifically, you lose credibility fast. Run your impact analysis first, and build your communication strategy from what you find.
Identify who changes, what changes, and when
Start by mapping every role, team, and process that the initiative touches. Document what each group currently does, what they will need to do differently after the change, and when that shift happens. This gives you a concrete picture of scale and scope rather than vague assumptions about who needs support.
The more specific your impact map, the more targeted and credible your support plan becomes.
Segment audiences and tailor support
Not every group needs the same message, the same training, or the same timeline. Once you know who is impacted and how deeply, group your stakeholders by role type, location, or level of change burden. A team facing a complete workflow overhaul needs far more hands-on support than one with minor process adjustments. Tailored support signals respect for each group’s real situation rather than offering generic reassurance.
Spot resistance early and plan responses
Use your impact map to flag the audiences most likely to push back before your rollout begins. High-impact groups with little input into the decision carry the highest resistance risk. Build specific responses to their likely objections, assign owners to those conversations, and treat early resistance as useful information rather than a problem to suppress.
5. Co-create with frontline employees
Top-down change rarely sticks. When frontline employees have no say in how a change is designed or rolled out, they feel like recipients rather than participants, and their resistance becomes your biggest obstacle. One of the most underused change management best practices is bringing the people closest to the work into the process before decisions are final.
Involve end users in design, testing, and rollout
Pull end users into working sessions during the design phase, not just the training phase. People who help shape a solution have a personal stake in its success.
During testing, ask them to stress-test workflows against their actual daily tasks rather than scripted scenarios. Their input surfaces practical gaps that a project team working in isolation will never catch.
The people doing the work know where the friction lives. Involve them early and you solve real problems instead of imagined ones.
Build a network of champions and peer helpers
Identify respected, credible people within each affected team and give them a formal role in the change. Champions translate new processes into familiar language and provide peer-level support that a project team cannot replicate. Equip them with talking points, early access to training, and a clear channel back to the project team for escalating issues.
Close the feedback loop so people feel heard
Collect input through structured surveys, team huddles, or open-door sessions, but treat that input as a commitment, not a courtesy. When people see their feedback reflected in real adjustments, trust in the process grows steadily, and future input becomes far easier to gather.
6. Communicate frequently and with the right senders
Communication volume is rarely the core problem in failed change initiatives. The real issue is who delivers the message and whether the content matches what people actually need to know. A well-timed message from the wrong person lands with far less force than the same message delivered by someone with direct credibility in that relationship.
Build a message map for what, why, and what changes
A message map gives your team a single reference point for every communication decision. Document the answers to three questions: what is changing, why it is changing, and what shifts for each affected audience. This document prevents conflicting messages from spreading across departments and gives every sender a consistent foundation to work from, regardless of format or channel.
- What: the specific change happening
- Why: the purpose behind the decision
- What changes: the concrete impact on each audience’s daily work
Use leaders for direction and managers for local impact
Senior leaders carry organizational authority, which makes them the right voice for communicating strategic direction and overall commitment. Direct managers carry relational credibility, making them more effective for translating change into what it means for daily tasks. Brief both groups separately so their messages reinforce rather than contradict each other.
The most effective change management best practices treat communication as a two-sender system: leaders for the why, managers for the how.
Repeat, reinforce, and correct rumors fast
People rarely absorb new information on the first pass during a period of uncertainty. Plan to repeat core messages across multiple channels and formats. When rumors surface, address them directly and quickly with factual responses rather than waiting for the noise to fade on its own.
7. Equip people managers to lead the change locally
People managers sit at the most critical pressure point in any change initiative. They receive direction from senior leadership and field questions, concerns, and skepticism from their direct reports, often with little preparation for either. When managers are left to figure it out on their own, they either go quiet or improvise, and both outcomes hurt adoption significantly.
Clarify manager responsibilities and boundaries
Your managers need to know exactly what they’re expected to do during the transition, and equally important, what falls outside their scope. Document a simple one-page summary of their role: which conversations to lead, what decisions they can make locally, and where to escalate issues they cannot resolve. That clarity reduces the anxiety that pushes managers to avoid the topic entirely.
Give managers a toolkit for coaching and pushback
Equip managers with practical materials they can use in team huddles and one-on-one conversations. That means FAQ documents, conversation guides for handling common objections, and talking points that connect the change to their team’s daily work. When managers have concrete tools in hand, they approach difficult conversations with confidence rather than avoidance.
A manager who understands the change and has a toolkit to address it becomes one of your most powerful reinforcement channels across the entire initiative.
Support managers who feel squeezed or skeptical
Some of your managers will be personally uncertain about the change while still being expected to champion it. Acknowledge that tension directly by building regular touchpoints where managers can share concerns, get updated information, and feel genuinely supported before they’re asked to support others. This is a core element of change management best practices that organizations consistently underinvest in.
8. Integrate change management with project management
Change management and project management solve different parts of the same problem, and when they operate in separate lanes, the gaps between them become the failure points of your initiative. Treating them as a single integrated effort from the start is one of the change management best practices that separates smooth transitions from costly restarts.
Align milestones, dependencies, and go-live readiness
Build one shared timeline that maps technical deliverables alongside training completion, communication waves, and readiness assessments. When a go-live date shifts on the project side, your change activities need to shift with it. Keeping both plans synchronized ensures that people are prepared before systems go live, not scrambling to catch up afterward.
Readiness is not a checkbox. It is a verified state where the right people can perform the right tasks in the new environment before the cutover happens.
Define roles so work does not fall through gaps
Ambiguity about who owns which activities produces duplicated effort in some areas and complete neglect in others. Create a simple RACI-style responsibility document that distinguishes project management tasks from change management tasks. Shared ownership of the overall outcome does not mean shared ownership of every deliverable, so assign clear leads for each stream.
Run joint risk reviews and issue escalation
Schedule regular joint sessions between your project manager and change lead to surface risks that neither would catch alone. A technical delay carries people-side consequences, and a resistance spike in one department can create downstream project risk. Reviewing both sets of risks together lets your team respond with coordinated solutions rather than isolated fixes.
9. Dedicate time, budget, and owners for change work
Change work does not happen by willpower alone. One of the most consistent failures in change management best practices is treating the people side of change as a task that existing staff can absorb on top of their regular responsibilities. Without dedicated resources, explicit funding, and named owners, your change activities compete against operational priorities every single day, and operations win.
Staff the change roles you actually need
Identify the specific roles your initiative requires and fill them before the project gets moving, not after you notice gaps. A change lead, a communications owner, and a training coordinator are distinct functions that one person cannot effectively cover simultaneously. Document each role’s responsibilities so nothing defaults to "whoever has time."
Understaffed change teams do not just move slowly. They create the conditions for resistance to grow unchecked because critical touchpoints get skipped entirely.
Fund training, comms, and reinforcement explicitly
Build change management costs into your project budget as a distinct line item, separate from technical and implementation costs. That means funding for training development, communication materials, champion networks, and post-launch reinforcement activities. When these costs are visible in the budget, they carry the organizational commitment that prevents them from being cut when pressure hits.
Protect capacity so change work does not become extra work
Talk with your change team members’ direct managers before the project starts. Confirm that realistic capacity is reserved for change activities and that competing demands get actively managed. When your change team is buried in their day jobs, your reinforcement and communication plans collapse quietly long before anyone notices.
10. Train for real work, not just knowledge
Generic training programs teach people what a system does. Effective training teaches people how to do their specific job in that system, starting on day one. When you design training around real tasks rather than feature walkthroughs, adoption rates climb because people leave the session able to work, not just informed.
Build role-based training tied to daily tasks
Start by listing the five to ten most critical tasks each role performs in the new process or system. Build your training modules around those exact tasks in the order people will encounter them. This approach cuts learning time and removes the guesswork that slows people down when they return to their desks.
Training that mirrors real work converts classroom time into immediate on-the-job capability, which is the standard every strong set of change management best practices should hold.
Practice in the tools and processes people will use
Give your learners hands-on practice time in the actual system, not a slide deck that screenshots it. Sandbox environments, simulated scenarios, and guided walkthroughs of real workflows build the muscle memory and confidence that classroom instruction alone never produces. People need to make mistakes in a low-stakes environment before they make them in a live one.
Verify readiness with checks before and after go-live
Run short competency checks before go-live to confirm that each role can complete their core tasks independently. After launch, schedule follow-up assessments within the first two weeks to catch gaps that surface only under real conditions and close them before they become lasting workarounds.
11. Reinforce, measure, and prevent backsliding
Most change initiatives declare victory at go-live and then wonder why old habits resurface within weeks. Reinforcement is where your investment either compounds or evaporates. Without a deliberate plan to sustain new behaviors, people default to what they know, and your project results fade quietly in the background.
Define adoption and performance metrics that matter
Measuring system logins or training completion tells you very little about whether the change is working. Define metrics that reflect actual behavioral change, things like how often people use the new process correctly, how quickly they resolve issues in the new system, and whether performance outcomes are trending in the direction the change was meant to produce.
The right metrics reveal whether people have genuinely shifted behavior, not just whether they sat through a training session.
Remove barriers and reward the new way of working
After go-live, collect data on where people get stuck and treat those friction points as a priority, not a nuisance. Removing a single persistent barrier often unlocks adoption across an entire team. Pair that barrier removal with visible recognition for teams and individuals who demonstrate the new way of working consistently.
Run a post-change review and bake lessons into the next change
Schedule a structured review 30 to 60 days after go-live to assess what worked, what slowed adoption, and where your change management best practices held up under real conditions. Document those findings in a format your team can reference for the next initiative. Organizational change capability builds only when lessons from each project feed directly into the next one.
Your next move
Every one of these change management best practices requires intentional effort, and none of them works in isolation. The organizations that navigate transitions successfully do not rely on a single tactic. They build a connected system where purpose, leadership, structured planning, and sustained reinforcement all point in the same direction at the same time.
You now have a concrete checklist to work from. Start by identifying which of these eleven practices your current initiative handles well and which ones have visible gaps. Pick two or three of those gaps and assign an owner to each one this week. That is a more durable starting point than redesigning your entire approach from scratch.
If you want to accelerate that process with expert-led guidance rooted in real-world high-stakes teamwork, connect with Robyn Benincasa to explore how her frameworks can help your organization lead change that actually holds.