GXO Logistics Creates Its First CIO Role and Splits Technology Into Foundation and Acceleration Tracks
People & Leadership

GXO Logistics Creates Its First CIO Role and Splits Technology Into Foundation and Acceleration Tracks

GXO named a 30-year aerospace and ERP veteran as its first-ever CIO and kept its CTO on a separate innovation mandate, betting a 150,000-person logistics company needs two technology chiefs, not one.

PublishedSeptember 5, 2026
Read time5 min read
Share

A Technology Org Built for a 150,000-Person Company

On September 3, GXO Logistics announced it has created a new Chief Information Officer role, the company's first, and named Balaji Rangaswamy to fill it, reporting directly to CEO Patrick Kelleher. GXO calls itself the world's largest pure-play contract logistics provider, running more than 1,000 facilities across over 200 million square feet with more than 150,000 team members worldwide. At that scale, a single technology executive owning both the enterprise backbone and the innovation agenda had become an organizational bottleneck. GXO's answer was to split the job in two rather than hire one person to try to do both.

Rangaswamy takes what GXO calls the foundation mandate: enterprise systems, architecture, information strategy, risk, data governance, cybersecurity, digital resilience and service management. Existing CTO Nizar Trigui keeps the acceleration mandate, covering GXO IQ, agentic AI, physical AI, robotics and other emerging technologies aimed at transforming supply chain operations. CEO Kelleher framed the logic plainly: "A strong foundation enables execution, accelerates innovation and supports long-term growth." That is a deliberate sequencing argument. GXO is betting innovation work moves faster once the underlying systems are solid, not while they are still being fixed.

Who Is Balaji Rangaswamy

Rangaswamy brings 30 years in enterprise technology, with a resume built specifically around the foundation problems GXO is handing him: ERP consolidation, supply chain harmonization, operational resilience and M&A integration. He joins from Collins Aerospace, an RTX business with roughly 30 billion dollars in scope, where he served as Vice President of Digital Technology. Before that he held CIO roles at Ricoh Americas Corporation and KLX Aerospace Solutions, and spent time at Boeing in VP-level IT roles across Global Services and Supply Chain, leading ERP transformation and post-acquisition integration work.

That background is a close match for what GXO needs right now. GXO itself grew through a wave of logistics acquisitions, and a technology leader who has spent a career integrating ERP systems across acquired aerospace and manufacturing units brings a playbook GXO can apply directly to its own fragmented systems landscape. Aerospace and defense contractors also operate under tighter security and compliance regimes than most logistics companies do, which should translate cleanly into the cybersecurity and digital resilience pieces of Rangaswamy's new mandate from day one.

The CTO Keeps the Innovation Mandate

Nizar Trigui was not displaced by this announcement. He was given a narrower and more clearly scoped job. Splitting acceleration from foundation means Trigui's team can pursue agentic AI, physical AI and robotics work without also owning the enterprise architecture and cybersecurity responsibilities that used to compete for the same attention and budget. GXO explicitly places GXO IQ, its analytics and AI platform, inside the acceleration track, which tells us the company treats its data and AI products as innovation bets rather than baseline infrastructure to be maintained.

This division of labor mirrors a structure we are seeing more often across large industrial and logistics companies: a CIO who owns the plumbing and a CTO who owns the frontier technology sitting on top of it. The risk in that model is coordination overhead between two executives who both report to the CEO but own adjacent, overlapping domains. GXO is betting that risk is smaller than the alternative: a single executive stretched too thin to do either job well at 150,000-employee scale, where both mandates now demand full-time attention on their own.

Why Split Now

GXO's own framing puts the reasoning in plain terms. Foundation work, in its telling, enables and accelerates innovation rather than competing with it for resources. That is a clean argument for splitting CIO and CTO functions once a company crosses a certain scale threshold, and GXO put that threshold at 150,000 employees and more than 1,000 facilities. The underlying logic applies well before a company reaches that size, though, if its innovation agenda keeps losing budget and attention fights to core system maintenance and technical debt.

The timing also lines up with where GXO's business is headed. A logistics provider betting on agentic AI and physical AI, robotics deployed inside warehouses, needs a stable enterprise backbone underneath those bets, or the innovation work risks breaking on infrastructure that was never built to support it. Giving Rangaswamy a clean foundation mandate, separate from Trigui's innovation agenda, reduces the chance that a robotics pilot gets stalled by an unrelated ERP integration problem competing for the same engineering hours.

Why This Matters for Supply Chain Tech Leaders

GXO's move is a useful data point for any enterprise technology leader running both infrastructure and innovation under one title today. The company's rationale, that foundation work enables innovation rather than competing with it, is a clean argument for splitting the CIO and CTO functions once headcount and facility count reach a certain scale. GXO drew that line at 150,000 employees and 1,000-plus facilities, but the underlying tension, core systems work crowding out innovation budget, shows up in much smaller organizations too, well before they approach GXO's footprint.

For PE-backed logistics and supply chain operators watching GXO, the lesson is less about the specific headcount threshold and more about the sequencing. GXO is explicit that foundation comes first and acceleration second, and that the two mandates need separate accountable owners rather than one executive juggling both simultaneously. Any technology leader building a case for adding headcount at the top of their own org, or for splitting an overloaded CTO role in two, should borrow that framing directly when making the pitch to their own board.

Tagged#news#people#leadership#cio#cto#cxo#gxo-logistics#balaji-rangaswamy#nizar-trigui#supply-chain-technology#contract-logistics#chief-information-officer#collins-aerospace#agentic-ai