What just happened
Martha Heller's CIO.com Movers and Shakers column for November 2026 reads differently than the same column a year ago. Laurie Douglas at Publix was promoted from SVP and CIO to chief information and digital officer, a title that formally absorbs customer-facing digital product work that used to sit elsewhere. Amaresh Siva joined Alaska Airlines as chief information and technology officer, arriving from a combined digital and technology role at CVS Health where he already ran both infrastructure and patient-facing digital products. Paxton McVoy left Veralto's CIO seat to become CIO at Woodward, an aerospace and industrial equipment maker, in a role the company is already describing in broader, more commercially oriented terms than the one he held before.
None of these are isolated rebrands confined to one company's HR department. They sit alongside a parallel wave of chief data and AI officer appointments tracked separately by CDO Magazine in the same two weeks, at Scotiabank, JPMorganChase, Commvault, and Michigan Medicine among others. Two different trade publications, tracking two different angles on the same executive bench, arrived at one underlying shift at almost the same time: the job description under the technology leader's name is getting wider across industries that rarely coordinate with each other on anything, let alone on org design.
The title inflation is not cosmetic
It is tempting to read CIDO and CITO as HR flourishes that change a business card and nothing else about the job. The actual mandates attached to these roles say otherwise, and the detail is in what each person inherits alongside the new letters. Douglas's CIDO scope at Publix adds digital products and customer-facing technology to a role that was previously focused on infrastructure and enterprise systems, a genuine expansion of what she is accountable for delivering, not a renaming of the same job. Siva's CITO brief at Alaska Airlines explicitly carries over the chief digital and technology officer scope he held at CVS Health, meaning the airline hired for the combined mandate on purpose rather than discovering it belonged together after the fact.
What is disappearing in both cases is the old split where a CIO ran systems and uptime while a separate chief digital officer or chief innovation officer owned growth-facing technology bets with a different budget and a different boss. Boards spent the last several years paying two leaders to coordinate on AI and digital investment, with predictably uneven results when their incentives diverged. They are now increasingly paying for one person to own both halves of that decision, for better or worse.
What boards are actually buying
The honest reason for this consolidation is accountability, not efficiency, and it is worth being precise about the failure mode it is meant to fix. When digital transformation and core IT sat with two executives, an AI pilot that touched both domains, a customer-facing chatbot built on infrastructure neither leader fully controlled, for example, had no single owner if the rollout stalled or the model behaved badly in production. Combining the roles gives the board exactly one name to call when a production AI initiative underdelivers, and exactly one name to credit publicly when it works as promised.
It also reflects a hiring market reality that boards are responding to whether they say so explicitly or not. CVS Health, Veralto, and the airlines and aerospace firms hiring this wave are competing for a genuinely small pool of technologists who have actually run AI and digital products at commercial scale, not administered a help desk and a data center contract. Paying for a combined CIDO or CITO title, with the compensation band that implies, is partly how these employers signal the role is strategic enough to attract that scarce candidate pool at all.
The authority gap nobody is pricing in
A wider title is not the same thing as a wider budget or a clearer reporting line, and that gap is where these combined roles most commonly stall out after the announcement fades. A CIDO who inherits digital product ownership without the P&L authority that used to sit with a separate chief digital officer will spend the first year negotiating for resources a narrower, traditional CIO role never had to fight for in the first place. Several of November's appointees are stepping into newly created or newly expanded titles, which means the authority that comes with them is still being negotiated in practice inside the organization, not settled on paper before the press release went out.
This is the same failure pattern we have tracked in prior chief AI officer appointments across other sectors: a title that implies enterprise-wide mandate, attached to a budget and reporting line that still reflects the narrower job it replaced. Boards that want this consolidation to actually work need to resolve the authority question in the new hire's first ninety days through an explicit budget allocation and a clear reporting line, rather than leaving the new executive to discover the limits of their own mandate the hard way, in the middle of a stalled initiative.
The decision for your own roadmap
If your organization still separates a CIO from a chief digital or innovation officer, this wave is a reasonable prompt to decide deliberately rather than let the next departure resolve the question by default. A combined CIDO or CITO mandate can genuinely speed AI-era decisions when the person holding it has both the technical credibility to run infrastructure and the commercial fluency to own product and growth bets at the same time. It can also concentrate real operational risk in one executive who cannot realistically own infrastructure reliability and digital product strategy at the same depth, especially during a period when both demand full attention.
Either choice is defensible, and reasonable leadership teams will land in different places depending on their talent bench and risk tolerance. What is not defensible is discovering, eighteen months into a combined role, that nobody actually widened the budget, the reporting line, or the decision rights to match the new title on the org chart. Price that question out now, while you are still writing the job description and setting expectations with the board, rather than during the retention conversation that follows a frustrated executive's resignation letter.



