People don't fear change. They fear loss.

William Bridges has a line I keep coming back to: change is the external event, but transition is the internal thing people actually go through. And what they resist isn't the change, it's the loss buried inside it.

When I introduced KafkaHost (a standard framework for our Kafka consumers) at Hubtel, the pushback wasn't about the framework. People were defending something. The control of writing their own. The craft of it. Being the one who knew the plumbing. And nobody wants to pay a learning curve when their code already works.

Except a lot of it didn't. Engineers would lift a consumer code sample off StackOverflow. We had little to no internal standards and the code ran fine until one unhandled exception in the business logic. Then it just hung. A "sleeping consumer", quietly dead, nobody watching. The thing they were afraid to lose was already failing them, they just couldn't see it yet.

Bridges says most of us spend 90% of our energy selling the solution and almost none selling the problem. So we flipped that. We named the loss honestly, sat with people one-on-one through the switch, then showed them the bigger loss they'd been carrying all along. We ran a drive to move every non-KafkaHost consumer over. It became the standard, and it seeded our Enablement team: 30+ SDKs and templates and counting.