Change management is an ownership problem, not a comms problem

A transformation lead at a distribution company told me about the launch that taught her the difference. Her org rolled out an AI feature with a genuinely good communications plan. A crisp announcement, a demo video, a training session, a launch email everyone opened. Weeks later, adoption was near zero. She had assumed the problem was that the message had not landed, so they sent more messages. Adoption did not move. The real issue was that no one owned the change. Communications had a plan. The change itself, the work of getting people to actually shift how they did their jobs, belonged to no one, and messages do not do that work on their own.

She named it in a way that reframed the whole thing. They had staffed the announcement and not the adoption. A comms plan tells people a change exists. It does not own whether the change happens, and those are completely different jobs.

Adoption is work, and work needs an owner

Change management gets treated as communications, so teams over-invest in the message and under-invest in the ownership. But getting people to change how they work is active, ongoing effort: sitting with teams, removing the friction, handling the resistance, following up when the initial enthusiasm fades. That is a job someone has to own, day after day, long after the launch email. When no one owns it, adoption depends on the message being so good that behavior changes by itself, which almost never happens. This is why so many technically successful AI features are used by almost no one. The feature shipped. The change did not, because no one owned it.

The teams that get adoption right assign an owner for the change, distinct from whoever owns the technology. That person is accountable for usage, not for the announcement. They work with the teams that have to change, remove the obstacles, and stay on it past the launch, because adoption is a curve, not an event.

Owning the change, not just announcing it

Name an owner for adoption. Someone accountable for people actually using the feature, separate from the person who owns the technology.
Measure usage, not awareness. An opened launch email is awareness. The owner is judged on whether people changed how they work.
Own the friction, not just the message. Adoption fails on small obstacles. The owner’s job is to find and remove them, in person, over time.
Stay on it past launch day. Enthusiasm fades on a schedule. The owner is accountable for the weeks after the announcement, which is when adoption is actually won or lost.

How we approach it at Density Labs

In our AI Opportunity Assessment ($2,500), we treat adoption as owned work, not a communications deliverable. We name who owns the change, make sure they are measured on usage rather than awareness, and confirm they are resourced to do the ongoing work adoption actually requires. A feature no one uses is a failure whether or not the launch email was excellent. Assigning a change owner up front is far cheaper than a beautifully announced feature that nobody adopts.

A launch email tells people something changed. An owner makes the change happen. Confusing the first for the second is why so many good features go unused.