Managing change in the workplace starts with clear communication, structured planning, and a focus on the people affected. Whether you’re rolling out new technology, restructuring teams, or shifting to a hybrid work model, the process follows a predictable pattern: prepare people for what’s coming, support them through the transition, and reinforce new behaviors until they stick. Here’s how to do each of those well.
Start With a Clear Framework
You don’t need to reinvent the process. Several proven models give you a roadmap, and the right one depends on the size and complexity of your change.
The simplest approach comes from psychologist Kurt Lewin, who broke change into three phases: unfreeze (recognize the need and prepare the organization), change (carry out the implementation), and refreeze (solidify new behaviors into company culture). This works well for straightforward changes where the goal is clear and the timeline is short.
For changes that affect individuals deeply, like new roles, tools, or workflows, the Prosci ADKAR model is more granular. It maps five building blocks each person needs to move through: Awareness of why the change is happening, Desire to support it, Knowledge of how to do things differently, Ability to put that knowledge into practice, and Reinforcement to keep the new behavior from slipping. If you notice a team struggling, ADKAR helps you diagnose exactly where they’re stuck. A team that understands the change but resists it has an awareness problem solved but a desire problem unaddressed.
For large-scale organizational transformation, Kotter’s 8-step model offers the most comprehensive structure. It begins with creating a sense of urgency and building a coalition of influential advocates, then moves through forming a strategic vision, enlisting volunteers, removing barriers, generating short-term wins, sustaining momentum, and finally embedding the change into daily operations. The emphasis on early wins is especially useful for long initiatives where people can lose motivation before results appear.
Communicate Early, Often, and Honestly
Poor communication is the single fastest way to turn a manageable change into an organizational crisis. People don’t resist change as much as they resist being surprised by it. The goal is to get ahead of uncertainty before it turns into anxiety.
Use a mix of channels: emails for formal announcements, team meetings for discussion, short videos for complex explanations, intranet posts for reference material, and messaging platforms for quick updates and questions. Different people absorb information differently, and a single all-hands email won’t reach everyone effectively. Research from Harvard Business Review suggests that a message needs to be repeated five to seven times before it truly sinks in, so plan for ongoing reinforcement rather than a one-time announcement.
Transparency matters more than polish. Acknowledge what you know and what you don’t. Set clear expectations about timelines and potential obstacles, and explain how future updates will be shared. Sugarcoating bad news or hiding difficult information damages trust in ways that are hard to repair. Employees consistently respond better to leaders who tell the truth, even when the truth is uncomfortable, than to leaders who seem evasive or overly optimistic.
One detail that’s easy to overlook: match the messenger to the message. Senior leaders should communicate big-picture business reasons for the change. Direct supervisors should handle the personal side, answering “what does this mean for my day-to-day work?” People trust their immediate manager more than a CEO they rarely interact with when it comes to understanding how a change will affect them personally.
Understand Why People Resist
Resistance isn’t a character flaw. It’s a signal that something in the process needs attention. When you understand what’s driving it, you can respond effectively instead of just pushing harder.
The most common triggers are predictable. Fear of job loss or compensation changes creates anxiety that no amount of motivational messaging can overcome on its own. Feeling excluded from the decision-making process makes people feel blindsided, which kills any sense of ownership. Uncertainty about what’s expected of them after the change leaves people clinging to familiar routines. And when leaders themselves appear disengaged or skeptical, it sends a signal that the change isn’t worth taking seriously.
Each trigger calls for a different response. For job-security fears, be direct about what will and won’t change regarding roles and compensation. For feelings of exclusion, invite feedback, hold open discussions, and make sure affected employees have a voice in how the change is implemented. For uncertainty, provide concrete details about what day-to-day work will look like after the transition. For leadership skepticism, build a coalition of sponsors who visibly support the change and model the new behaviors themselves.
The most effective intervention across all of these is answering the question every employee is silently asking: “What’s in it for me?” Until people see a personal benefit, or at least understand how the change connects to something they care about, compliance will be surface-level at best.
Build Buy-In Before You Need It
The best time to address resistance is before the change launches. During the planning stage, examine how your organization has responded to past changes. If the last software rollout was chaotic, people will expect this one to be too. Conduct readiness assessments and engage stakeholders early so you’re not fighting uphill from day one.
Involve affected employees in shaping the implementation. This doesn’t mean putting every decision to a vote. It means identifying the people closest to the work, asking them what obstacles they foresee, and incorporating their input where it makes sense. People who help design a process feel ownership over its success. People who have a process imposed on them look for reasons it won’t work.
Align the change with your organization’s existing culture and values whenever possible. A company that prides itself on innovation will absorb a new technology initiative more naturally than one that values stability and tradition. When there’s a gap between the change and the culture, name it explicitly and explain why the shift is worth making. Recognizing and rewarding employees who embrace the change early encourages others to follow.
Handle Hybrid and Remote Teams Differently
Managing change across distributed teams adds layers of complexity that in-office changes don’t have. When employees independently choose their office days, teams can experience co-location imbalance, where key people are rarely in the same place at the same time. This makes collaborative rollouts, training sessions, and informal knowledge-sharing harder to coordinate.
Structured “anchor days,” where teams come together in person on set days, help solve this by aligning schedules around collaboration goals. For the portions of change management that happen digitally, provide clear learning pathways that address the unique dynamics of hybrid work: giving feedback across locations, choosing the right communication channel for different types of updates, and establishing shared etiquette norms so remote employees aren’t left out of important conversations.
Regularly assess what’s working through surveys and other feedback tools. Remote employees are more likely to disengage quietly than to voice concerns in a group setting, so create low-friction ways for them to share honest feedback. Make sure your systems and environment reinforce the behaviors you want. If you’re asking people to use a new project management tool but every important decision still happens in hallway conversations, the change won’t stick.
Generate and Celebrate Early Wins
Large changes lose momentum when results take too long to materialize. People need evidence that the effort is worth it, and the sooner they see it, the more willing they are to keep going. Break the initiative into phases and identify quick, visible victories you can achieve in the first few weeks.
These wins don’t have to be dramatic. If you’re implementing a new workflow, highlight a team that completed a process in half the time using the new system. If you’re reorganizing departments, share positive feedback from a client who noticed faster response times. The point is to create tangible proof that the change is producing results, then make sure everyone knows about it.
Celebrating wins also gives you a natural opportunity to recognize the people who made them happen. Public recognition reinforces the behaviors you want to spread and shows fence-sitters that embracing the change leads to positive outcomes.
Measure Whether the Change Is Sticking
Too many change initiatives are declared successful the moment they launch. Real success is measured weeks and months later by whether people are actually using the new processes, tools, or behaviors.
Track three categories of metrics. First, speed of adoption: how quickly are employees learning and applying new skills? How many people are using the new system 10 days after launch, 30 days after, 90 days after? Second, ultimate utilization: what percentage of affected employees are actually using the new process consistently? You can measure this through system logins, process audits, or simply observing how people work post-implementation. Compare the number of employees actively using the new system to the total number who should be.
Third, proficiency: are people using the new tools or processes correctly and effectively? Track the number of support tickets and help desk calls, which should decline over time as competence grows. Compare work performance against established benchmarks. For hands-on roles, “show me” testing, where employees demonstrate their proficiency, gives you a clearer picture than self-reported confidence surveys.
When the numbers show adoption lagging in a particular team or department, circle back to the ADKAR framework. Are they aware of the change? Do they want to adopt it? Do they know how? Can they actually do it? Have you reinforced it enough? The answer tells you exactly where to focus your next intervention.