Most change management frameworks were designed for a world that doesn't exist anymore.
They assume you have eighteen months. None of those things are true. They assume people will read a 40-page communication plan and nod thoughtfully. Day to day, they assume leadership alignment. The average transformation now has a shelf life of six months before the next reorg, the next platform migration, the next "strategic pivot" lands on everyone's desk Nothing fancy..
People argue about this. Here's where I land on it.
And yet we keep teaching the same five-step models from 1995.
What Is Change Management (Really)
Strip away the certifications and the maturity models and the stakeholder maps. Change management is simply this: helping people do something differently tomorrow than they did today, without losing their minds — or their trust — in the process Worth keeping that in mind..
That's it. Everything else is scaffolding.
The problem is we've confused the scaffolding with the building. Useful frameworks, sure. Lewin's Unfreeze-Change-Refreeze. Kotter's 8 Steps. We've turned a human challenge into a compliance exercise. But they're maps. Which means aDKAR. And the territory has shifted Simple as that..
The map is not the territory
Here's what most certifications won't tell you: no framework survives first contact with a resistant middle manager who's been burned three times before. No communication plan fixes a culture where "feedback" means "tell me what I want to hear." No training deck compensates for leaders who say the right things in all-hands and do the opposite in budget reviews.
Real change management isn't a methodology. It's a set of judgment calls made under pressure, usually with incomplete information, often while the plane is being rebuilt mid-flight And that's really what it comes down to..
Why It Matters / Why People Care
Seventy percent of change initiatives fail. That stat gets tossed around so much it's lost its teeth. Let me put it differently: seven out of ten times, your organization spends money, burns political capital, exhausts people, and ends up roughly where it started — just more cynical.
Cynicism compounds. Every failed change makes the next one harder. Now, the passive resistance gets more creative. The eye-rolls start earlier. The best people — the ones with options — leave.
And here's the part nobody puts in the business case: failed change doesn't just waste money. It erodes the social contract. People stop believing leadership has a clue. That's why they stop offering discretionary effort. They start updating LinkedIn.
The hidden cost of "good enough" change
I watched a mid-sized SaaS company roll out a new CRM three times in four years. Practically speaking, first attempt: top-down mandate, zero input from sales. Adoption hovered at 23%. Second attempt: "we listened this time" — they added a few fields sales asked for, same mandatory workflow. Adoption hit 41%. Third attempt: they actually shadowed reps for two weeks, built the tool around the actual sales motion, and let the top performers design the rollout. Eighty-nine percent adoption in month one.
Most guides skip this. Don't.
The software didn't change. The approach did.
The first two attempts cost roughly $2.Here's the thing — 3M in licenses, implementation, training, and lost productivity. The third cost about $400K more in upfront discovery — and paid for itself in quarter one The details matter here..
How It Works (or How to Do It)
Forget the phases. Think in tensions instead.
Every change creates tension between what people know and what they're being asked to do. Between habit and intention. So between safety and risk. Your job isn't to eliminate tension — it's to make it productive.
Start with the honest assessment
Before a single slide deck, before a single stakeholder interview, ask the uncomfortable questions:
- Who loses status, budget, or autonomy in this change?
- What unwritten rules are we violating?
- Where has leadership credibility already been spent?
- What's the real reason this is happening now — not the reason on the slide, the real one?
I've seen change leads skip this because "we don't have time.Because of that, " You don't have time not to. The resistance you don't understand will ambush you in month three. The resistance you map in week one becomes your design constraint Took long enough..
Design for the resistors, not the enthusiasts
Enthusiasts need almost nothing. They'll figure it out. Here's the thing — they know the workarounds. They see the edge cases. Resistors — the thoughtful ones, not the reflexive naysayers — are your best designers. They've survived previous "transformations" and have the scar tissue to prove it.
Invite them in. Not for theater. Now, for real input. Think about it: "Here's where we're going. In practice, here's why. Day to day, where will this break for you? " Then actually use what they tell you.
One manufacturing plant I worked with brought the union stewards into the automation planning six months before go-live. Plus, the rollout went live on schedule with zero lost-time injuries. The stewards identified seventeen failure modes the engineers missed. Think about it: three of them would have caused safety incidents. The stewards became the strongest advocates on the floor.
Build the "minimum viable change"
Most rollouts try to change everything at once. Process, tools, roles, metrics, culture. That's not a change program. That's a hope strategy.
Pick one behavior that, if it shifted, would create visible momentum. Make it specific. Observable. Measurable in weeks, not quarters.
"Adopt the new CRM" is not a behavior. "Log every customer interaction in the CRM before end of day" is. "Be more collaborative" is not a behavior. "Include at least one cross-functional reviewer on every spec before dev starts" is.
Then remove every barrier to that one behavior. Celebrate the early wins publicly. Simplify the tool. Change the incentive. Give people time. Let the momentum do the heavy lifting for the next behavior Most people skip this — try not to..
Make the invisible visible
Change feels abstract until it's not. People need to see it working in their world, not in a pilot team three floors up Not complicated — just consistent..
Run shadow sprints. Pair skeptics with early adopters for two weeks. Worth adding: let them compare notes in a structured retro — not a survey, a real conversation. Consider this: capture the friction. Fix it. Repeat.
One healthcare system rolling out a new documentation standard paired resistant physicians with champions for "doc-along" shifts. The skeptics saw the time savings in real time. Think about it: the champions learned the workarounds that made the standard bearable. Both groups improved the template. Adoption hit 92% in eight weeks Simple, but easy to overlook..
Treat communication as a product, not a broadcast
If your change comms look like marketing — polished, one-way, full of "excited to announce" — people tune out. They've seen this movie Easy to understand, harder to ignore..
Instead: short, frequent, honest. "Here's what we're trying. " Weekly. Here's what's working. Here's what's broken. Here's the thing — here's what we're doing about it. From the people doing the work, not the VP of comms No workaround needed..
Slack channels beat town halls. Two-minute Loom videos beat PDFs. A leader admitting "we got the rollout sequence wrong and here's the fix" builds more trust than five "change champion" newsletters.
Common Mistakes / What Most People Get Wrong
Mistaking compliance for adoption
People doing the thing because they're measured on it isn't adoption. It's compliance. Compliance evaporates the moment the measurement stops — or when a workaround appears Simple, but easy to overlook..
Real adoption looks like people improving the
process on their own. It’s when a team member suggests a tweak to the workflow because they actually want it to work better. When you see employees teaching the "trick" to a new hire without being asked, you've moved from compliance to ownership.
Over-investing in the "What" and under-investing in the "How"
Organizations spend months perfecting the new strategy—the "What"—and then spend a single two-hour training session on the "How." They assume that if the logic is sound, the execution is automatic.
But logic doesn't overcome habit. Habits are rewritten through repetition and psychological safety. If the cost of trying the new way is a temporary dip in productivity or a risk of failure, people will default to the old way every time. But to fix this, build "safe-to-fail" zones where the goal isn't perfection, but experimentation. Reward the attempt, not just the outcome.
Ignoring the "Middle Management Squeeze"
The C-suite sets the vision, and the front line does the work, but the middle managers are the ones who actually decide if a change lives or dies. If a manager tells their team, "Corporate wants us to do this, so just play along," the rollout is dead on arrival Most people skip this — try not to..
You cannot delegate the change management to the middle. You must equip them with the tools to coach their teams through the friction. Give them the talking points, the troubleshooting guides, and the authority to make local adjustments. When managers feel like architects of the change rather than messengers of it, they stop being bottlenecks and start being accelerators Worth knowing..
The Final Shift: From Project to Practice
The biggest mistake in change management is treating the rollout as a project with a "completion date." A project ends; a practice evolves The details matter here..
The moment you declare "the rollout is complete" is the moment the regression begins. Here's the thing — the "rubber band effect" pulls people back toward their old habits the second the spotlight fades. Even so, to prevent this, transition from a "launch phase" to a "maintenance phase. " Establish a permanent feedback loop where the people on the floor can report friction and see those reports translated into updates.
At its core, where a lot of people lose the thread.
True organizational agility isn't about the ability to execute a single massive shift; it's about building a muscle for continuous, incremental improvement. When you stop treating change as a traumatic event and start treating it as a rhythmic process, you stop fighting the current.
By focusing on minimum viable changes, making the invisible visible, and treating communication as a two-way product, you move from forcing a change to facilitating a transition. That's why the goal isn't to get people to "accept" the new way—it's to make the new way the path of least resistance. When the new behavior becomes the easiest way to get the job done, you no longer have a rollout. You have a new culture And it works..
