Why split the CIO and CTO roles at all
Most companies that create a dedicated innovation track for agentic AI and robotics still run it through the same technology leader who owns ERP, warehouse management systems, and cybersecurity. GXO chose the opposite structure, explicitly separating Foundation from Acceleration and giving each its own executive owner. CEO Patrick Kelleher described the goal as building a scalable, resilient technology foundation while accelerating innovation, language that only makes sense if the two tracks genuinely compete for the same budget and the same engineering talent.
That competition is the real reason to split the roles. Enterprise systems work rewards stability, long planning cycles, and risk aversion. Robotics and agentic AI work rewards fast iteration and tolerance for failed experiments. Asking one executive to optimize for both simultaneously tends to produce compromise outcomes on both sides, and GXO's restructuring reads as an explicit rejection of that compromise.
What Rangaswamy inherits as the new CIO
Rangaswamy's Foundation mandate covers enterprise systems, cybersecurity, data governance, and risk, which at a contract logistics provider means the systems that keep warehouses, transportation networks, and client-facing operations running without interruption. His own comments on continuously modernizing and integrating ERP, WMS, and other core enterprise systems point to a job defined by uptime and integration quality rather than headline-grabbing product launches.
His background suits that mandate closely. VP of Digital Technology at Collins Aerospace, a Raytheon Technologies business, means experience running mission-critical systems in a highly regulated aerospace environment. Earlier CIO stints at Ricoh Americas and KLX Aerospace Solutions, plus a VP role in IT and data analytics at Boeing, round out a career built almost entirely around large-scale enterprise systems in asset-heavy, operationally intensive industries, a close match for what logistics actually is.
What stays with Trigui on the Acceleration side
Nizar Trigui keeps the CTO title and the Acceleration track, covering GXO IQ and the company's agentic and physical AI robotics work. Keeping this track under the existing CTO rather than folding it into the new CIO's remit is itself a signal: GXO wanted continuity on its innovation roadmap rather than restarting robotics strategy under a new leader at the same time it onboards a new CIO.
That continuity matters for a logistics company specifically, because physical robotics deployments carry long lead times and capital commitments that do not tolerate frequent strategy resets. Protecting that track from the same transition affecting Foundation suggests GXO is treating its robotics program as a maturing, protected bet rather than something still being defined from scratch.
The dual-reporting structure and what it prevents
Both Rangaswamy and Trigui report directly to CEO Patrick Kelleher rather than to each other in either direction. That reporting line matters because it prevents either track from becoming subordinate to the other's priorities. A CIO reporting into a CTO tends to see enterprise systems funding squeezed in favor of innovation headlines; a CTO reporting into a CIO tends to see robotics experiments throttled by risk-averse systems governance.
Keeping both as peers under the CEO forces Kelleher personally to adjudicate the tradeoffs between stability and experimentation, rather than delegating that tension down to one or the other executive. We think that is a deliberate choice about where accountability for the balance between the two sits, and it puts real pressure on quarterly planning conversations at the top of the organization.
What this means for other logistics and industrial technology leaders
GXO's split offers a concrete template for other asset-heavy enterprises wrestling with the same tension between core system reliability and AI-driven innovation. Rather than appointing a single Chief AI Officer to sit above or alongside an existing CIO, GXO cleanly partitioned the work by risk profile and gave each side a dedicated executive with a matching background.
For CIOs at other logistics, manufacturing, and industrial companies watching how peers structure AI governance, this is worth studying less for the specific hire and more for the organizational design choice it represents: separating the systems that must not break from the systems built to experiment, with a CEO sitting directly above both to keep the tradeoff honest.
