The technical decision was easy. The human decision was not.
Years ago, I was leading the integration of a newly acquired middleware product. The acquired business was dependent on a costly third-party tool that no longer made strategic sense for us, so the logical answer seemed obvious: build our own cloud-based integration platform and retire the legacy system.
On paper, it was a technology migration.
In reality, it was much bigger.
We had inherited a team whose expertise, credibility and everyday work were built around that legacy platform. Asking them to move to our new solution could easily sound like we were asking them to leave behind the very expertise that had made them valuable.
That was the moment I realised we weren’t simply changing technology.
We were changing the business.
The initiative meant redefining integration within our product portfolio, entering the cloud integration space, reshaping an entire team’s responsibilities and moving from a cost-centre mindset towards product ownership.
So we changed how we approached it.
We co-created the vision: the team wasn’t losing its function; it was becoming the organisation’s integration platform team.
We changed the incentives: success was measured through adoption, reliability and value from the new platform rather than maintaining the old one.
We transferred ownership: the people closest to the legacy system became central to building its successor.
We connected technology to outcomes: internal teams and customers could see why the new capability mattered.
The biggest lesson for me was simple:
Implementation changes what the organisation uses. Transformation changes what the organisation is capable of doing.
Since then, I have used a simple test.
If we describe an initiative primarily through technology, timelines and deliverables, we may be implementing something.
If we begin with the business outcome we need to create, and technology is one of the levers to get there, we are probably transforming.
The distinction matters because a successful transformation does not just deliver a new platform.
The team that once felt replaced by the new platform became the people who built it, and it now serves customers who’d never have adopted the old one.
