The technology leader conversations I find most interesting aren't about the next AI model or the next platform. They're about a harder question: how do you run a complex, regulated, mission-critical technology operation reliably, cost-efficiently, and compliantly, while simultaneously building the next generation of capability?
"The best CIOs I've known don't choose between running the business and transforming it. They do both — with the same urgency, the same rigor, and the same accountability to results."
In the pharmaceutical industry, this tension is particularly acute. The systems that manage government pricing, payer contracts, wholesaler inventory, and patient services cannot go down, cannot be out of compliance, and cannot be slow. That operational discipline isn't a constraint on innovation. It's the precondition for it. Organizations trust technology leaders with transformation precisely because they have demonstrated they can run things well first.
What "Running It Well" Actually Means
There's a tendency in the executive technology community to treat operations as the unglamorous half of the job: something to be delegated, outsourced, or optimized away so that leaders can focus on the "strategic" work. This is a mistake, and I've seen it cost organizations dearly.
Running a global pharmaceutical commercial technology organization means being personally accountable for the platforms that process billions of dollars in transactions every day. It means knowing with precision the uptime of your order management system, the accuracy of your government pricing calculations, the reliability of your chargeback processing. When something fails, patients may not get their medication. Wholesaler relationships fracture. Regulatory exposure follows.
The operations I led over 25+ years included more than 500 FTEs managing platforms supporting a $41B U.S. commercial engine. My measure of success wasn't only innovation delivered. It was 100% audit success across SOX, HIPAA, GxP, and CMS over multi-year periods. In a zero-tolerance regulatory environment, that consistency doesn't happen by accident. It happens through disciplined architecture, rigorous change management, and a team culture where compliance is structural, not ceremonial.
Before a single AI model goes into production, before any ERP transformation begins, before any platform modernization is launched, the organization needs to trust that you can keep the lights on. Operational credibility is the permission structure for transformation.
The Transformation Half
Once that foundation is established, transformation becomes possible in a way it simply isn't for leaders who haven't earned that trust. When I led a board-endorsed enterprise AI program targeting $5B–$7B in recurring value, the governance model we built was grounded in the same principles as our operational frameworks: stage-gates, explicit success criteria, rigorous ROI accountability. By 2025, we had realized $1.5B in direct, measurable value.
That result didn't come from exciting technology alone. It came from applying operational discipline to innovation: treating each AI investment as a business case that had to clear a >25% ROI hurdle, building a value realization engine that tracked outcomes from initiation through measurement, and maintaining the organizational credibility to kill or pivot investments that weren't performing.
The Conference Circuit Version vs. the Real Version
If you spend time at CIO conferences, you might conclude that the job is primarily about digital transformation, AI strategy, and the future of technology. There's a reason those topics dominate the agenda: they're compelling, they're forward-looking, and they're the conversations technology leaders want to have.
But the organizations doing the best work, the ones actually delivering on their transformation agendas, are almost uniformly the ones that have the operational house in order. Their platforms are stable. Their compliance record is clean. Their shared services model is running efficiently. Their teams trust the technology organization to deliver what it commits to.
That trust is earned in the day-to-day, not in the keynote. And it's what makes everything else possible.
What I've Learned About Doing Both
1. Treat operations as a strategic asset, not a cost center
The language you use about operations shapes how your organization thinks about it. When you consistently frame operational excellence as the foundation for strategic agility rather than as overhead to be minimized, you attract different talent, build different culture, and make different investment decisions. The 40%+ reduction in delivery and operating costs I achieved through Global Business Services consolidation wasn't about cutting corners. It was about building a more capable, more sustainable delivery model that freed resources for higher-value work.
2. Use the same governance rigor for transformation as for operations
The frameworks that make operations reliable work equally well for transformation programs: stage-gates, clear accountability, measurable outcomes, and escalation paths. The AI governance model we built was modeled on clinical development principles: you don't advance a program without meeting explicit criteria, and you don't keep investing when the data says stop. This is not a constraint on innovation; it's what makes large-scale innovation sustainable.
3. Build a team that can do both
The hardest organizational challenge is building a team with the discipline to run operations at the highest standard while simultaneously having the curiosity and creative capacity to drive innovation. These are not mutually exclusive traits, but they require intentional cultivation. The leaders I've seen do this best are those who make operational excellence genuinely aspirational rather than just a compliance obligation, and who create explicit pathways for their best operational talent to contribute to transformation work.
The CIO who only transforms will eventually run out of road. The CIO who only operates will eventually be left behind. The ones who build lasting value are the ones who learn to do both: not alternately, but simultaneously, with the same energy and the same standards applied to each.
That's the job. All of it.