The Two-Week Change That Takes Quarters
Six months ago, I got feedback about my own company that I want to share with you, because my reaction to it is the same reason your last process change took longer than it should have.
The feedback was: "I don't get it."
I rarely take feedback personally, but I did that one. Not because the feedback was wrong or cruel, but because my brain registered it as a threat. The brand was built from my interpretation, so a critique of the packaging felt like a critique of my taste.
I metabolized the discomfort and eventually went back to the drawing board to rebuild. I want to be precise about what I was experiencing between hearing the feedback and acting on it, because that gap is where organizational change struggles.
It wasn’t simply resistance to a technical change; I was attached to the original vision and strategy.
Now scale that up.
You approved a process change, and training has been delivered. The new system is objectively better for nearly everyone touching it.
Implementation estimate: two weeks. Actual: two quarters.
When the change is sound, and the resistance persists anyway, it’s no longer a process problem.
The people in that workflow didn't just operate from the old process. They were someone inside it. The person who knows where everything is. The one approval that matters. The veteran whose workaround keeps the whole thing running. The old process was the infrastructure of their competence, their status, their sense of security, and their answer to "what do I do here?"
Your new process removed those answers and didn't issue new ones.
So they aren't dragging their feet on the new process on purpose. They are still emotionally entangled with the identity the ‘old ways’ once held. And identity defense could show up as slipped timelines, endless clarifying questions, quiet reversion to the old way the moment leadership looks elsewhere, and a two-week change that ages into its second quarter.
Transformations fail at adoption because the identities of the people involved haven’t found home in the new structure.
The fix is not more training on the new steps. People learn steps in a week; that was never the real constraint.
The fix is structural and psychological: the new process has to assign new answers to the old questions. Who is the expert now? Whose judgment matters at which checkpoint? What does competence look like on the other side of this change? If the redesign doesn't answer those questions, every affected person either answers them alone or gets them through endless ‘alignment’ meetings. Consequently, all the delays accumulate, creating an epistemic lag for the leadership team.
It was never about the process.