Operations teams don't resist change — they resist being ignored

"The operations team is resistant to change."

I hear this often when transformation initiatives stall. And after 20 years of leading complex transformations in regulated industries, I can tell you it's almost never the real story.

Operations teams don't resist change. They resist being handed a solution that was designed without their input, for a problem that wasn't fully understood, on a timeline that doesn't account for the complexity they manage every day.

Think about what that looks like from their perspective.

They've been running a process for years. They know every exception, every workaround, every fragile handoff that keeps things from falling apart. They know which steps exist because of a regulation and which exist because of a system limitation nobody ever fixed.

Then a project team shows up with a new tool or a redesigned workflow. And nobody asked them what actually happens on the ground.

That's not resistance. That's a rational response to being overlooked.

In regulated industries, this pattern is more than frustrating. It's risky. The people closest to the work often hold critical knowledge about compliance, quality, and risk that never made it into any documentation. When you bypass them, you don't just slow down adoption. You create blind spots. And in pharma, healthcare, and financial services, blind spots have real consequences.

The most successful transformations I've been part of all started the same way. By listening to the people doing the work before designing the solution.

Not as a courtesy. As a strategic necessity.

That's what human-centered transformation actually looks like. You start with the people, not the solution.

Something worth thinking about before your next initiative.