The new process is better. Everyone agrees it’s better. Six months later, half the team is still doing it the old way.

This isn’t stubbornness or sabotage. It’s human nature. People have habits, comfort zones, and mental models built around how things work. Change requires effort: learning new steps, building new habits, accepting temporary incompetence while getting up to speed. Without deliberate change management, the path of least resistance is the old way.

Process improvement that doesn’t get adopted isn’t improvement. The technical work of designing better processes is often easier than the human work of getting people to actually use them. Understanding why adoption fails, and what to do about it, is as important as designing the process itself.

Why People Don’t Adopt New Processes

Resistance to new processes is predictable. Common causes:

The old way works. It may not be optimal, but it’s familiar. People know how to do it. They’re competent at it. The new way requires them to feel incompetent again while they learn. That’s uncomfortable.

Change wasn’t explained. People were told to do something different but not why. Without understanding the reason, they lack motivation to push through the discomfort of change.

Training was insufficient. A one-hour training session doesn’t create proficiency. People try the new process, struggle, and revert to what they know. They’re not resisting; they’re unable.

The new process is actually worse. Sometimes the people doing the work see problems that the designers missed. The new process looks good on paper but fails in practice. Resistance is information.

No accountability for adoption. The old way still works technically. No one checks whether people are using the new process. Without accountability, adoption is optional, and optional change doesn’t happen.

Leaders don’t use it. If managers keep asking for things in the old format, using the old systems, following the old process, why would anyone else change?

The Elements of Successful Change

Adoption doesn’t happen automatically. It requires deliberate work across several dimensions:

Compelling reason. People need to understand why the change matters. Not “management decided” but a genuine reason that makes sense to the people being asked to change. What problem does this solve? What benefit does it create? Why is the old way no longer good enough?

Adequate training. Training needs to build actual competence, not just awareness. This means hands-on practice, not just presentations. It means follow-up support, not just initial sessions. It means training matched to different learning needs, not one-size-fits-all.

Early support. The first few times people use a new process, they’ll have questions. If help isn’t available, they’ll fall back to the old way. Intensive support during the transition period (available, responsive, patient) makes the difference.

Clear accountability. If adoption is optional, it won’t happen. Define what adoption looks like. Measure it. Follow up on it. Make clear that the old way is no longer acceptable, and mean it.

Leadership modeling. Leaders need to visibly use the new process themselves. Ask for information in the new format. Use the new system. Follow the new workflow. When leadership keeps operating the old way, they signal that the change isn’t serious.

Feedback loops. Listen to what people experience with the new process. Some complaints are adjustment friction that will pass. Some are legitimate problems that need fixing. Distinguishing between them, and responding appropriately, builds trust and improves the process.

The Adoption Curve

Not everyone changes at the same pace. Expect variation:

Early adopters. Some people embrace change quickly. They’re curious, adaptable, or see clear benefit. They’ll start using the new process immediately and help others.

Pragmatic majority. Most people wait to see if the change is real before investing effort in adapting. They’ll change once they see it’s mandatory and working for others.

Resisters. Some people resist any change. A few may have legitimate concerns worth hearing. Others simply prefer the familiar. They need clear accountability and persistent follow-up.

Understanding this distribution shapes your approach. Don’t expect universal adoption immediately. Do expect resistance from some. Plan your effort accordingly: support early adopters, demonstrate to the majority, hold resisters accountable.

Practical Change Management

Making change stick:

Communicate before, during, and after. Announce the change in advance. Explain the reason. Communicate timeline and expectations. Follow up during rollout. Reinforce after initial adoption. One announcement isn’t communication; it’s a starting gun.

Make the new way easier than the old way. If possible, disable the old process or make it harder to access. Remove the old forms. Redirect the old links. Eliminate the old options. When the old way is unavailable, the new way becomes the only way.

Provide support resources. Quick reference guides, FAQs, help contacts, peer mentors. Make it easy to get help. The goal is to reduce the cost of learning the new process.

Celebrate early wins. When the new process works, when it delivers the benefits that were promised, make that visible. Share success stories. Recognize people who’ve adopted effectively. Early wins build momentum.

Address problems quickly. When issues emerge, fix them fast. Nothing undermines change faster than problems that go unaddressed. Responsiveness builds trust; unresponsive “roll with it” messaging breeds cynicism.

Follow up persistently. Check adoption after a week, a month, three months. Identify who’s using the new process and who isn’t. Address non-adoption directly. Persistence signals that the change is permanent.

When the Process Needs to Change

Sometimes resistance reveals problems with the new process itself:

Listen to specific complaints. Vague “I don’t like it” is different from “This step doesn’t work because X.” Specific feedback often identifies legitimate issues.

Watch what people actually do. If everyone finds the same workaround, that’s a design problem, not an adoption problem. The process needs to change.

Distinguish friction from failure. Some discomfort is normal during transitions. But if the process doesn’t work in practice (it can’t handle real situations, it takes twice as long, it produces worse results), that’s not an adoption problem to push through. That’s a design problem to fix.

Good change management includes the humility to recognize when the change itself needs changing.