Driving change in an organization starts with a clear reason people can rally behind, a structured plan for getting there, and consistent follow-through that outlasts the initial enthusiasm. Whether you’re rolling out new technology, restructuring teams, or shifting company culture, the difference between change that sticks and change that fizzles comes down to how well you prepare people, involve them in the process, and measure progress along the way.
Start With a Clear Case for Change
Before announcing any initiative, you need a compelling answer to the question every employee will ask: “Why are we doing this?” People naturally fear change because it brings uncertainty, and employees who feel unsure about how changes will affect their job security or daily work tend to perceive the whole effort as a threat. That perception leads to stress and resistance, often before the change even begins.
Your case for change should connect the initiative to a problem people already feel or a goal they already care about. If your customer satisfaction scores have dropped, say so. If a competitor is outpacing you because of a capability gap, make that visible. Vague statements like “we need to be more innovative” don’t create urgency. Specific, honest descriptions of the current reality do. Transparency builds trust and reduces resistance, making employees more likely to engage rather than dig in.
Pick a Framework That Fits Your Scale
You don’t need to invent your approach from scratch. Three well-established models give you a structure to work from, and the right choice depends on your organization’s size and sophistication.
Lewin’s Three-Step Model is the simplest: unfreeze the current behavior, make the change, and refreeze the new behavior. It works well for smaller organizations or teams that haven’t gone through formal change management before. The value is in its clarity. You acknowledge that the old way needs to stop, you introduce the new way, and you lock it in through new routines and expectations.
Prosci’s ADKAR Model focuses on the individual employee’s journey through five stages: awareness of why the change is needed, desire to participate, knowledge of how to change, ability to implement the new skills or behaviors, and reinforcement to sustain the change over time. This model is especially useful when the change requires people to adopt new tools or workflows, because it forces you to address each psychological step rather than assuming a training session is enough.
Kotter’s Eight-Step Model is designed for larger organizations where change needs to move through multiple layers. It starts with creating a sense of urgency, then building a coalition of supporters, then developing a vision. Those first three steps are about unfreezing the organization and getting people ready before you even begin implementing. The remaining steps walk through communicating the vision, empowering action, generating short-term wins, building on gains, and anchoring the change in culture.
All three models share the same basic insight: you can’t skip the preparation phase. Jumping straight to implementation without building understanding and buy-in is the fastest route to failure.
Build a Coalition Before You Announce
Change driven by a single leader, no matter how senior, is fragile. You need allies at multiple levels of the organization who believe in the change and can influence their peers. Identify managers, team leads, and respected individual contributors who either already see the problem you’re solving or who have the credibility to bring skeptics along. Bring them into the planning process early, share your reasoning, and ask for their input on how the change will land with their teams.
This isn’t just a political move. Involving people in shaping the change makes them co-owners of it. When employees feel included in the process, they’re more likely to welcome the change rather than resist it. A coalition also gives you honest feedback about where your plan has blind spots, which is far better to discover before launch than after.
Communicate More Than You Think You Need To
Undercommunication is one of the most common reasons change efforts lose momentum. People need to hear the “why” repeatedly, through different channels, in language that connects to their specific work. A single all-hands meeting or company-wide email is a starting point, not a communication plan.
Leaders should communicate openly about why the change is necessary, what the benefits look like, and what the future state will feel like day to day. Be specific about what’s changing and what isn’t. Silence creates a vacuum that rumors fill quickly, especially if previous changes were poorly handled and employees already lack trust that new efforts will go any better.
For managers, Gallup recommends one meaningful conversation per week with each direct report. During a change initiative, these conversations become critical. They should cover progress toward goals, barriers the employee is facing, their wellbeing, and how the change is affecting collaboration and customer impact. These aren’t status updates. They’re the mechanism through which people process change and feel supported through it.
Lead by Doing, Not Just Directing
Successful change is often achieved through influence rather than command. If you’re asking teams to adopt a new process, leaders and managers need to use it visibly and consistently. If you’re shifting toward a more collaborative culture, senior leaders need to demonstrate collaboration in how they run their own meetings and make decisions. Employees are perceptive. They watch what leaders do far more closely than what leaders say.
Highlight people who are adapting well. When someone on a team embraces the new approach and gets good results, make that visible. Peer examples are more persuasive than top-down directives because they show what “good” looks like in practice, not just in theory. Building trust, credibility, and collaborative persuasion makes it far easier to gain buy-in than issuing mandates.
Equip People With Skills, Not Just Instructions
One of the biggest gaps in change initiatives is the jump from “here’s what we’re doing differently” to “now go do it.” The ADKAR model distinguishes between knowledge (understanding what to do) and ability (actually being able to do it), and that distinction matters. Telling someone to use a new software platform is knowledge. Giving them hands-on practice until they’re comfortable is ability.
Workshops, seminars, coaching sessions, and even gamified programs can help employees build new skills while also processing their feelings about the change. Training should be timed close to when people will actually use what they’ve learned. A training session three months before a launch date is largely wasted. Ongoing support after launch, whether through help desks, peer mentors, or quick-reference guides, matters just as much as the initial training.
Handle Hybrid and Remote Teams Intentionally
Driving change across distributed teams adds a layer of complexity that many leaders underestimate. Gallup research shows that 48% of hybrid workers cite communication as their top challenge and 44% cite collaboration. Nearly half of hybrid workers say their team has never discussed a formal or informal plan for how to collaborate effectively. When you layer a change initiative on top of that existing gap, the risk of miscommunication and disengagement multiplies.
Teams with a formal hybrid collaboration plan are 66% more likely to be engaged at work and 29% less likely to be burned out. Before rolling out a change, establish clear norms for how your distributed team will communicate about it: which updates happen asynchronously, which conversations need to be live, and how you’ll ensure remote employees are included in decision-making conversations, recognition moments, and informal relationship-building. Proximity bias is real. Only 54% of managers who supervise remote employees strongly agree they trust their teams to be productive when working remotely, and only 57% of employees feel trusted by their manager when remote. Change initiatives can widen that gap if you’re not deliberate about closing it.
When teams determine their hybrid schedule together, 91% say the policy is fair, compared with 73% when leadership determines it unilaterally. The same principle applies to change: involve distributed team members in shaping how the change will work in their context rather than designing it entirely around in-office assumptions.
Measure Adoption, Not Just Completion
Many organizations declare victory when a change is “launched,” but launch day is just the beginning. The real question is whether people are actually using the new process, tool, or behavior consistently. Prosci’s framework measures three human factors: speed of adoption (how quickly people start using the change), ultimate utilization (how many people are using it), and proficiency (how well they’re applying it).
Track specific data points at intervals. For a technology rollout, that might mean the number of people using the new system at launch, then 10 days later, then 30 days later, along with frequency of use and feature adoption. For a process change, you might track how many teams have incorporated new steps into their workflows versus how many have reverted to the old way. For a cultural shift, employee surveys and manager observations can gauge whether new behaviors are showing up in daily interactions.
Organizations that measure compliance and overall performance during change efforts see dramatically better results. Prosci’s research across thousands of change initiatives found that 76% of organizations that measured performance met or exceeded their project objectives, compared with just 24% of those that did not measure. What gets measured gets attention, and what gets attention gets done.
Reinforce Until It Becomes the Default
The final and most overlooked phase of any change initiative is reinforcement. New behaviors are fragile. Without sustained attention, people drift back to old habits, especially when the initial energy fades and day-to-day pressures reassert themselves.
Reinforcement takes many forms: updating performance expectations to reflect the new way of working, recognizing and rewarding people who model the change, adjusting onboarding so new hires learn the current approach rather than the old one, and revisiting the change in team meetings long after the official rollout period ends. Embed the change into company values, the organizational mission, and everyday practices so it stops being “the new thing” and becomes simply how work gets done.
Gather feedback continuously and adjust when needed. Knowing when to refine an approach is just as important as knowing when to push forward. Some resistance is rooted in legitimate concerns about how the change works in practice, and addressing those concerns strengthens the initiative rather than weakening it. Foster a culture where risk-taking and learning from mistakes are safe, and the next change effort will face less resistance before it even begins.