Certainly. One of the most difficult decisions I had to make as a CIO was leading the early retirement of a legacy ERP system that had been deeply embedded in the organization for over a decade. It was a mission-critical platform, familiar to staff, and tightly woven into multiple departments -- but it had become a major bottleneck for scalability, data integration, and compliance.
The challenge wasn't just technical -- it was emotional and cultural. Many teams were resistant to change, citing concerns about disruption, retraining, and potential downtime. But the risks of staying -- including security vulnerabilities, rising maintenance costs, and limited flexibility -- outweighed the comfort of the status quo.
To approach it responsibly, I began with extensive stakeholder engagement, conducting impact assessments and listening sessions across departments. This helped us identify pain points, surface hidden dependencies, and bring key users into the conversation early. I also collaborated with finance and operations to model the long-term ROI of a modern, cloud-based system -- not just in dollars, but in agility, resilience, and future-readiness.
We rolled out a phased migration plan that prioritized high-risk areas first, invested heavily in change management and training, and maintained parallel systems during the transition to avoid business disruption. While it wasn't easy, the result was a more unified, data-driven infrastructure that ultimately empowered faster decision-making and improved cross-functional collaboration.
The key lesson? Sometimes, leadership means making the hard call not because it's popular -- but because it's necessary for long-term growth. Change is uncomfortable, but when you bring people along and align the tech decision with business value, the organization emerges stronger.