A company built on divisions decides it needs one technology owner
Disney has run technology as a federation for decades, with parks, studios, streaming and consumer products largely maintaining their own stacks and answering to their own segment leaders. That structure suited a company built through acquisition and division autonomy, but it also meant no single executive owned the infrastructure connecting them. On September 18, Disney confirmed a newly created role, senior executive vice president and chief technology officer, that reports directly to CEO Josh D'Amaro and spans enterprise technology, infrastructure, data and AI platforms, product, and engineering across every segment technology team, according to the company's own announcement.
The timing matters. Disney has pushed AI pilots across parks operations, content production and its streaming stack for two years, and those efforts surfaced the same problem most large enterprises eventually hit: pilots multiply faster than the governance and data foundations meant to support them. Consolidating ownership under one CTO is Disney's structural answer to that sprawl, and it echoes a pattern we track across asset-heavy and regulated industries this year, where the fix for stalled AI programs turns out to be organizational before it is technical. A media company with five distinct operating segments is a demanding test case for that theory, which is exactly why other CIOs should watch how it plays out.
Why Disney picked an outsider rather than promoting from within
Karandeep Anand joins from Character.AI, where he served as chief executive, after a career spanning Microsoft, where he spent 15 years in senior product and engineering roles tied to the Azure platform, Meta, where he was vice president of ads and business products for Facebook, and Brex, where he served as president and chief product officer. He also holds a computer science degree from the International Institute of Information Technology in Hyderabad. That resume runs through cloud infrastructure, consumer platforms and fintech product, not media, which suggests Disney weighted platform-building experience and AI fluency over industry familiarity when it defined the role, a tradeoff more boards will consider as technology leadership searches widen beyond the usual internal candidates.
D'Amaro framed the hire around exactly that breadth. "Karandeep brings a rare mix of experience across infrastructure, consumer technology and AI," he said in the company's announcement. "He is an expert builder and strategist with sharp instincts for what fans actually want." Anand called the opportunity an honor and said he looks forward to building on the company's existing technology capabilities, language that reads as deliberately modest given the scope of what he is inheriting. He starts October 2, giving him roughly two weeks from the announcement to prepare for a mandate that spans nearly every technical function Disney operates.
One executive now owns infrastructure, data, AI and product together
The mandate Disney published is unusually broad for a single role: enterprise technology, infrastructure, data and AI platforms, product, and engineering across segment technology teams, with an explicit goal of modernizing the company's technology infrastructure. That is four functions that, at most large enterprises, sit under four different executives with four different budgets and four different risk appetites. Putting them under one leader removes the coordination tax that usually shows up as duplicate AI tooling, inconsistent data governance and security policies that vary by business unit, a tax most CIOs can quantify in wasted vendor spend alone.
It also concentrates accountability in a way segmented org charts avoid. When a data pipeline failure blocks an AI feature, or a governance gap surfaces in one division's agent deployment, there is now one executive whose job is explicitly to have seen it coming. That is a harder job description, and a more honest one, than the diffuse ownership most enterprises still run with heading into next year's AI scaling push, where board pressure to show measurable AI returns will only intensify the coordination problem this role is meant to solve.
The organizational bet other CIOs will face this year
Disney is not alone in discovering that segment-level technology autonomy, useful for speed, becomes a liability once AI and data strategy need to work the same way everywhere. We expect more enterprises with strong divisional structures, retailers with regional operating companies, industrials with acquired subsidiaries, financial groups with product-line silos, to face the same choice this year: keep technology decisions close to the business unit, or centralize enough of the stack that AI investment does not get duplicated five times over across divisions that rarely compare notes.
The honest answer for most CIOs sits somewhere in between, and getting that balance wrong in either direction is costly. Full centralization slows the business units that move fastest and often move fastest for good reason. Fragmentation, which is closer to where most large enterprises sit today, means AI governance policy exists on paper in one division and nowhere in another, a gap regulators, auditors and boards are increasingly unwilling to tolerate as agentic AI deployments touch more regulated data and customer-facing decisions.
What this means for your own technology org chart
The practical move for any CIO reading this is an honest audit of where infrastructure, data and AI platform ownership actually sits today, not where the org chart says it sits on paper. Most enterprises will find AI governance answering to a different executive than data quality, which answers to a different executive than infrastructure spend, and that fragmentation is exactly what Disney's new role is designed to eliminate in one motion rather than through years of incremental committee work.
Disney's bet will not be right for every company, and a single CTO spanning four major functions creates its own concentration risk if the hire does not work out or the scope proves unmanageable for one person. But the underlying diagnosis, that scattered technology ownership has become a strategic liability rather than a tolerable inefficiency, is one every CIO managing a multi-division enterprise should take seriously before the next board cycle forces the question on someone else's timeline instead of their own.
