Change is inevitable. It’s the tax every project pays for existing in the real world. You can plan, predict, and polish your charts until they shine, but the moment you involve people, budgets, and deadlines, change walks in the door and sits down at the table. Invited or not.
Some project managers spend their entire careers trying to resist change, as if they can fight it into submission. Others bend so much that they break, letting every new request or demand blow their project off course.
Both approaches fail. Often gloriously.
The truth is simple: you can’t eliminate change, but you can master how you deal with it. And mastering change doesn’t require a 400-slide deck or some trendy consulting framework with an acronym nobody remembers after the kickoff call.
It requires a mindset. A way of operating that never forgets the human side of projects, never lets SOS (shiny object syndrome) drive decisions, and never assumes people just magically understand what’s happening.
That’s where the ABCs of Change come in.
A: Always understand that change impacts people more than you know.
B: Be deliberate in what you change and tie it directly to achieving success.
C: Communicate the status and the why more times than you think necessary.
That’s it. Three fundamentals. If you get these right, you’ll lead your team through the chaos of change with clarity and authority.
When you ignore them, you join the long line of project managers whose initiatives failed, not because the plan was bad, but because the execution fell apart under the weight of unmanaged change.
Let’s break this down.
A: Always Understand That Change Impacts People More Than You Know
Every change, no matter how small, lands heavier than you think. I don’t think it’s an understatement to say most people hate (even small) change with a white-hot passion.
But project managers often treat change as mechanical. A line item moves, a timeline shifts, a new requirement gets added. To us, it’s just another adjustment to the plan. But, for the people who have to live with the outcome, those changes feel personal.
Think about it: when you change a workflow, you’re not just changing steps in a process. You’re changing how someone does their job every day. That means retraining, uncertainty, slower performance at first, and maybe even a fear that they won’t measure up anymore.
A “simple” reporting tweak could mean hours of relearning.
A “minor” tool change could force someone to rethink years of muscle memory.
Leaders who ignore this reality create resentment and quiet resistance. I’ve seen executives roll out new systems with a wave of the hand (and sadly, I’ll admit I’ve done it myself): “It’s just an upgrade, people will adapt.”
That’s fantasy. People don’t “just adapt.” They struggle. They complain. They feel disrespected because nobody considered how it hit them. And if you don’t acknowledge that, they’ll fight you in silence. They’ll drag their feet, cut corners, or cling to the old ways.
Why People React Stronger Than You Expect
Fear of losing competence. People hate feeling stupid. Change makes them feel like beginners again, and beginners make mistakes. Mistakes lead to people feeling stupid all over again.
Loss of control. Even a small shift strips away comfort. What was once predictable becomes uncertain. Uncertainty drives fear, and fear leads to inaction and delays.
Identity threat. For many, their job isn’t just a paycheck; it’s their pride. If change makes them feel irrelevant, you’ll get pushback.
What Strong PMs Do
Acknowledge the disruption. Don’t pretend it’s easy. Say out loud: “I know this changes your day-to-day, and it’s not simple.” Validation goes much further than you think.
Ask where it hurts. You’ll be shocked at how one tweak at the leadership level can cause a dozen pain points downstream. But you won’t know unless you ask. Also, this may seem like common sense, but LISTEN to the answers they give you (whether you like them or not).
Support adaptation. Build time, training, and breathing room into your change plan. People need a runway, not a cliff. Breathing room gives your people comfort, and I’ll argue that 9 times out of 10, the urgency you feel to enact the change isn’t real.
The best project managers know that change management is people management. Ignore the human side, and your best-laid plans collapse. Respect it, and even tough change becomes survivable.
B: Be Deliberate in What You Change (and Tie It to Success)
Not all change is created equal. Some changes make your project stronger. Some kill it slowly. And some are just noise. Your job is to know which is which.
Too many teams treat change like a buffet. “Let’s add this feature.” “Let’s shift that deadline.” “Let’s tack on this improvement while we’re at it.” Before you know it, the project is bloated, the team is overwhelmed, and leadership is frustrated that you’re late and over budget.
Every change comes with a price tag: money, time, morale, credibility. If you’re not deliberate, you’ll go bankrupt on all four.
The Deliberate Change Filter
Here’s the blunt test I use for every proposed change:
Does it directly tie to achieving project success? If yes, consider it. If no, kill it immediately.
Is the value worth the cost? If not, reject it, no matter how shiny it looks.
Does it align with mission priorities? If it’s a distraction, don’t touch it.
You’d be surprised how many change requests fail this filter. And yet, weak project managers let them slide because they’re afraid to say no.
“No” is a leadership skill (and a full sentence).
Every new change looks small to the person requesting it. But to your team, it means more rework, more stress, more late nights. They won’t push back, they’ll just get buried quietly until quality drops or deadlines slip.
That’s on you.
Being deliberate isn’t about being rigid. It’s about protecting your team and keeping the mission in focus. When you approve change, it should be because it makes the project undeniably better, not because someone higher up thought it would be “nice to have.”
Tie every change you accept to a success metric. “We’re pivoting here because it eliminates a major risk.” Or, “This adjustment adds cost, but it directly increases customer satisfaction.”
If you can’t draw a straight line from the change to project success, don’t do it.
Projects fail when leaders confuse motion with progress. Deliberate change keeps you moving toward the finish line, not spinning in circles.
C: Communicate the status and the WHY more times than you think necessary
If there’s one rule that separates great project managers from mediocre ones, it’s this: you can never communicate too much.
Most leaders think communication is sending an email or giving a status update at the weekly meeting. Wrong. That’s the bare minimum. People don’t absorb information the first time they hear it. They’re busy, distracted, and skeptical.
When change is on the table, you need to communicate more, not less. And you need to hammer two things relentlessly: the STATUS (what’s happening right now), and the WHY (why this is happening and why it matters).
Over-communication works because:
Repetition builds clarity. People rarely get it the first time. By the seventh, it clicks.
Silence breeds fear. If you don’t fill the gap with facts, people fill it with rumors.
The “why” drives buy-in. Status updates alone don’t inspire action. When people understand why change matters, they stop resisting and start engaging.
I’ve never seen a project collapse because the leader communicated too much. I’ve seen dozens collapse because leaders assumed one announcement was enough.
Here’s your communication playbook:
Multiple channels. Email, dashboards, meetings, one-on-ones. Don’t rely on only one format.
Say it different ways. Some people need detail. Others need big-picture. Mix it up.
Don’t stop when you’re tired of saying it. Stop when people can repeat it back to you without hesitation.
Over-communication is not a weakness. It’s discipline. And if your team starts rolling their eyes because you’ve repeated the same why for the tenth time? Congratulations: you’ve finally broken through.
Let’s put this into a real-world scenario.
Imagine you’re leading a digital transformation project for a regional bank. Leadership sees it as “just” a technology upgrade. You know better.
A: Always understand people are impacted. You sit with frontline staff and realize the new system changes how they serve customers at the window. What leadership thought was a technical swap is (in reality) a massive shift in how tellers do their jobs. You acknowledge this, invest in training, and show empathy instead of brushing it off.
B: Be deliberate in change. Midway through, someone proposes adding new mobile features. Sounds great, but it doesn’t tie to the core mission of stabilizing internal systems. You reject it, thereby protecting your timeline and resources.
C: Communicate. Instead of sending one corporate memo, you hold weekly Q&A sessions, send short video updates, and make sure every employee hears the “why” seven different times. Adoption skyrockets.
Result? The bank transformation launches successfully, staff buy in, and customers never feel the turbulence.
That’s the ABCs of Change at work.
Here’s the No BS bottom line: Change will always hit harder than you expect. It always costs more than you plan. It always stirs up more emotions than leaders want to admit. But you can control how you lead through it.
The ABCs of Change are your compass:
A: Always understand the human impact.
B: Be deliberate, not reckless, about what you change.
C: Communicate more than feels comfortable.
Ignore these, and your projects will drown in resistance, scope creep, and confusion.
Master them, and you’ll stand out as a leader who doesn’t just manage projects; you guide people through uncertainty and deliver results when others fall apart.
Because project management isn’t about keeping a spreadsheet updated. It’s about leading people through the storm of change. And if you can do that with clarity, empathy, and discipline, you’ll win every time.
