When change management doesn't feel like change management
There's this moment that keeps showing up in how organizations handle shifts in tools, processes, or workflows. It's not the kickoff meeting. It's not the training deck. It's something quieter.
It happens when someone on a team already knows how to do the thing, so they just... do it. They figure out the new tool or workflow because it makes sense to them, or because they had five minutes and got curious. Then someone else notices they're not struggling, asks how, and suddenly there's a small pocket of people who understand it without it feeling like mandatory learning.
That pocket grows. Naturally. Without a communication cascade or a change champion or a governance structure.
What's interesting is that this seems to work better than the alternative. The alternative being: designated change management, structured rollout phases, communication plans with messaging themes, and a bunch of compliance checking to make sure everyone sat through the training.
The difference between managing change and enabling it
There's a real difference in flavor between "we are going to change this and here's how it will happen" and "here's this thing, here's why we're doing it, figure out what works for your part of the world."
The first one needs oversight. It needs someone tracking adoption metrics and chasing people down about completion rates. It needs the change to look the same everywhere or at least the change management process needs to look the same everywhere.
The second one needs something different. It needs clarity about why. It needs at least some people to have access to help. It needs space for things to unfold a little bit messily.
Somewhere in the middle of these two approaches, something real is shifting. Organizations are noticing that the heavy machinery of change management feels out of proportion when everyone already knows something is happening. When people can see a Slack channel dedicated to the new tool. When they can watch other people figure it out in real time instead of attending a training that happened three weeks ago.
Speed versus smoothness
Here's where it gets weird though. The lighter touch approach isn't actually faster. It's not slower either. It just spreads differently.
With structured change management, you get everyone trained on day one, but adoption often stalls around day fifteen. With the lighter approach, adoption is slower to start but something different happens around week three. The people using it are actually using it for real. Not because they have to, but because it started making sense.
That distinction matters because tools and processes only stick when they become normal. When they're embedded in how work actually happens. Mandatory training can create the appearance of adoption without any of the stickiness.
The uncomfortable part
The thing that's sort of uncomfortable about this is that it requires tolerance for ambiguity during the transition. Someone has to be okay with the fact that different teams will figure things out at different times. Different parts of the organization might end up with slightly different workflows or workarounds. It's not neat.
But also, is it actually less neat? The neat version looks organized on a spreadsheet and falls apart after the change management budget runs out. The messier version self-organizes because people actually need it to work.
What's actually showing up
There's this middle ground that organizations are starting to inhabit. Still having change leadership and communication, but lighter. Still having training, but more just-in-time and peer-focused. Still tracking adoption, but in a less policing way and more in a "how can we help the people who haven't found it yet" way.
The best examples seem to have a few things in common. There's usually someone visible who understands both the change and the organization. There's a real, honest explanation of why it's happening. There's a way for people to ask dumb questions and get help without it being formal. And there's permission for the change to land differently in different places.
The reason this matters now
Change is just more frequent now. Organizations can't afford to treat every shift like a major transformation project. And people are frankly tired of the ceremony around it. They want to know what's happening, why, and then get to work.
So the interesting thing happening is that change management is getting less visible while somehow being more effective. Less project, more ongoing. Less announcement, more conversation.
Which might just be what happens when everything keeps changing. You stop making it such a big deal and it starts working better.