The biggest concern for CIOs may not be the recruiting of a chief AI officer (CAIO). It’s what happens to their responsibilities afterward.
Consider a CAIO who reports directly to the CEO and takes responsibility for enterprise AI strategy, investments, workforce transformation, and business outcomes. The CIO continues to manage infrastructure, applications, cybersecurity, and daily technology operations.
The CIO hasn’t been demoted, at least not officially. The title remains unchanged. But much of the strategic responsibility has moved to another executive.
Companies don’t need to eliminate the CIO position to reduce its influence. They can gradually redefine it as a traditional, infrastructure-focused CTO role while assigning enterprise transformation to the CAIO.
The Data Points To A Changing Leadership Structure
IBM’s 2026 CEO study found that 76% of surveyed organizations have a CAIO, compared with 26% in its separate 2025 research. IBM’s 2025 report, Solving the AI ROI Puzzle, also found that 57% of surveyed CAIOs reported directly to the CEO or board.
These findings don’t mean CIOs are losing their jobs. They do suggest that CEOs increasingly see AI as important enough to warrant dedicated executive leadership.
An October 2026 Thoughtworks survey of 3,200 CIOs offers another perspective. Thirty-five percent said their CAIO operated independently, with equal or greater influence across the organization. Another 29% reported friction or unclear responsibilities between the two positions.
At the same time, 89% said their responsibilities were shifting toward redesigning workflows and workforce models rather than managing infrastructure.
CIOs are being asked to take greater responsibility for business transformation just as companies are hiring another executive to lead it.
There are legitimate reasons to appoint a CAIO. AI initiatives often span multiple departments, require substantial investment, and demand more attention than one executive can provide. The concern for CIOs is whether the company has clearly defined how the two executives will work together.
How The CIO Role Gets Redefined
The change rarely happens overnight. The CAIO begins setting AI priorities, managing the investment portfolio, and presenting progress to the board. The CFO works with the CAIO to establish financial targets. HR looks to the CAIO to determine how automation will affect staffing and job responsibilities.
The CIO continues running the EHR, cloud infrastructure, networks, enterprise applications, and cybersecurity program. The CIO remains responsible for keeping critical systems available, connecting new technologies, and protecting company data.
Those are substantial responsibilities. But if the CIO is no longer involved in deciding how technology will change the business, the position has become primarily operational.
For years, CIOs have worked to move beyond managing IT infrastructure and gain a stronger voice in enterprise strategy. A separate CAIO position could reverse that progress if the CEO transfers transformation responsibilities without reconsidering the CIO’s role.
The CIO might still attend executive meetings and oversee a significant budget. What matters is whether the CIO participates in the decisions that shape the company’s future.
What CIOs Should Look For In A CAIO Job Posting
A CAIO job description can tell CIOs a great deal about how their company intends to divide executive responsibilities.
Reporting structure. If the CAIO reports directly to the CEO, will the CIO have the same access to discussions about business strategy, technology investments, and organizational change?
Responsibilities. Does the CAIO own enterprise transformation, workflow redesign, and technology-driven business outcomes? If so, what strategic responsibilities remain with the CIO?
Budget authority. Who approves AI investments, selects vendors, and decides which initiatives receive funding? An executive who controls investment priorities often has more influence than one responsible for implementing those decisions.
Accountability. Who takes responsibility when an AI initiative fails or creates a security problem?
IBM’s June 2026 technology leadership study found that approximately two-thirds of surveyed CIOs and CTOs were accountable for AI systems they did not fully control.
Thoughtworks also found that 90% of surveyed CIOs expected central IT to be held responsible for security or compliance failures involving AI purchased independently by business departments.
For healthcare CIOs, this deserves particular attention.
AI agents are beginning to operate across clinical applications, patient scheduling, revenue cycle, and administrative workflows. These tools need access to enterprise systems and sensitive information.
If the CAIO authorizes an AI deployment but the CIO remains accountable for security, integration, and system availability, the organization has created a serious management problem.
The executive responsible for managing the risk needs sufficient authority over the decisions that create it.
CIOs Need To Take Some Responsibility
Not every CIO can blame organizational restructuring for losing influence.
Many CIOs have successfully established themselves as business leaders. Others continue to measure their contribution primarily through system uptime, project delivery, vendor management, and IT cost reductions.
Those responsibilities are important, but CEOs increasingly want to know how technology will improve the company’s financial and operational performance.
AI makes that distinction more important.
Consider an AI application that saves employees five hours a week. That sounds like an attractive return on investment, but the savings have little financial value unless the company does something with the additional capacity.
Can the organization reduce overtime? Handle more transactions without additional hiring? Improve collections? See more patients? Reduce administrative costs?
Someone needs to make those operating decisions and establish how the results will be measured.
The CIO who understands how AI affects staffing, workflows, technology costs, and business performance has a strong argument for remaining involved in enterprise strategy.
A CIO who limits the conversation to AI platforms, technical architecture, and vendor selection may find that the CEO looks elsewhere for business leadership.
The CIO doesn’t need to manage every AI project. But the position should remain involved in decisions about how the organization uses technology to operate differently.
What CIOs Should Do Before The CAIO Arrives
The best time to address these questions is before the company hires a CAIO.
Start with the CEO. Understand why the company wants a separate AI executive and which responsibilities that person will assume.
The discussion should address specific decisions:
Who controls the enterprise AI investment portfolio?
Who approves AI agents that access company systems and data?
Who determines which business processes should be redesigned?
Who reports financial and operational results to the board?
Who is accountable when an AI initiative creates a security, compliance, or operational problem?
CIOs should also come prepared with their own assessment of where AI can improve business performance.
Identify which workflows offer measurable opportunities, where existing technology or data limitations could delay implementation, and what operational changes are needed to produce a financial return.
For healthcare organizations, that might include reducing revenue cycle expenses, improving patient access, addressing staffing shortages, or lowering administrative costs.
The discussion needs to move beyond implementing AI applications to determining what the organization expects those applications to accomplish.
I would also recommend establishing a written governance agreement among the CIO, CAIO, CFO, CISO, and relevant operating executives.
It should define investment authority, data ownership, security requirements, clinical safety oversight, approval processes for autonomous agents, and responsibility for measuring results.
This doesn’t mean the CAIO should report to
the CIO. Both positions can have distinct responsibilities while sharing accountability for enterprise outcomes.
CIOs should also participate in developing the job description and interviewing candidates. It’s much easier to establish a productive working relationship before the CAIO joins than to negotiate competing responsibilities afterward.
The Bigger Risk Is Losing Strategic Influence
Some CIOs will benefit from having a CAIO as a partner. A dedicated AI executive can help coordinate business adoption, accelerate implementation, and bring additional resources to initiatives that IT cannot manage alone.
In other organizations, the appointment may confirm that the CEO already views the CIO primarily as the person responsible for keeping technology running.
That distinction matters.
CEOs should be clear about what they expect from both executives. Boards should also question any structure that gives one leader authority over AI investments while holding another responsible for the technology and security consequences.
CIOs, meanwhile, need to demonstrate that their contribution extends beyond operating enterprise technology.
The real threat isn’t that the CAIO will replace the CIO. It’s that the CIO will keep the title, the infrastructure, and the operational accountability while someone else takes responsibility for strategy, investment, and business transformation.
By the time that becomes obvious, the company’s leadership structure may have already changed.