The adoption gap nobody budgets for

Look at almost any transformation budget and you can see where the organization thinks the work is. There is money for design, money for build, money for the launch. There is a communications plan and a kickoff. And then the budget, and the attention, drop away right at the point where the change actually has to happen.

The launch is not the change. The launch is the moment you ask people to work differently. Whether they do is decided in the weeks after, when the novelty has worn off, the old way is still available, and the plan needs someone senior to keep it moving. That stretch is the adoption gap, and it is the part nobody budgets for.

It is also where most transformations quietly stall. Not with a decision to stop, but with a slow return to how things were, because the people who could have held the change in place went back to their day jobs the week after go-live.

I have watched the same organization run the same kind of change twice, once as an announcement and once with the weeks after actually resourced. The difference was not the plan. The plan was better the first time. The difference was that the second time someone owned the messy middle, worked the resistance rather than overriding it, and stayed until the new way was the normal way.

The cheapest thing you can do to improve the odds of a transformation is to move some of the budget from the launch to the eight weeks after it. Fund a community of practice, name an owner for adoption specifically, and measure the change in behaviour rather than in slides delivered.

A pilot proves something can work. Adoption is whether it does. The gap between those two is not a talent problem or a technology problem. It is a resourcing choice, made before the work starts, and it is usually made in the wrong place.