Why People Resist Change: A Lesson from Retiring Access 97
A strong business case can explain why an organization needs to change. It may still leave employees wondering why they should let go of something that works for them.
I learned this early in my project-management career. In 2008, I joined the City of Portland’s PMO. One of my first projects involved retiring Microsoft Access 97.
Yes, Access 97.
The organization had tried several times over nearly ten years to move away from it. The software had become part of how people did their work, and asking them to give it up meant much more than replacing an application.
Find out what people are protecting
Think about someone who has spent years building applications and queries. Colleagues come to that person for help. They know the system, understand its workarounds, and have earned a reputation for solving problems.
A replacement system can put that sense of expertise at risk. Another employee may be worried about learning an unfamiliar tool. Someone else may be concerned about losing an application that supports an important process.
Those are different concerns. Repeating the same announcement will not answer all of them.
Before deciding that someone is being difficult, ask what the existing system gives them. Is it confidence? Control over their work? A useful capability? Recognition? The answer helps you understand what the transition needs to preserve or replace.
Urgency needs practical support
The Windows 7 migration eventually helped create urgency for moving away from Access 97, driven by security and compliance requirements. But urgency was only part of the solution.
People also needed updated tools, training, and help transitioning their existing applications to supported systems. A deadline can make change necessary. It does not automatically make people ready.
This experience connects to five readiness questions I use through VIRSA: Vision, Incentives, Resources, Skills, and an Action Plan.
Vision: Can people explain the problem the change is meant to solve?
Incentives: What improves for the people expected to work differently, and what are they worried about losing?
Resources: Are the replacement tools, support, and time available?
Skills: Can people practice the new work and get help when they struggle?
Action Plan: Do they know the next step, who owns it, and what happens to the old process?
Have the individual conversation
For your next change initiative, speak with people who depend on the current way of working. Ask them what would become harder if it disappeared tomorrow.
Listen before defending the new solution. Some concerns may reveal a training need. Others may expose a requirement the project team has missed. You may also find an experienced employee who could help shape the transition if their knowledge is respected.
The organization’s reason for changing and an individual’s reason for supporting it may be different. Both deserve attention.
Understanding those differences gives a leader a more useful place to begin than another reminder that change is coming.
Explore the SCARE to CARES leadership framework for practical ways to communicate, build relationships, empower people, and stay calm during change. For a session built around your organization’s challenges, learn about the SCARE to CARES keynote.
Adapted from my original LinkedIn reflection.

Comments