The CIO Role Has Changed But Job Descriptions Have Not

The Chief Information Officer title started appearing in organizational charts in the 1980s. The person holding it was responsible for running data centers, managing networks, keeping mainframes alive, and making sure the lights stayed on in the server room. The job was fundamentally operational: keep the systems running, keep costs down, don't let anything break during the fiscal quarter close.

That description fits about twenty percent of what CIOs are asked to do today. The other eighty percent involves digital strategy, innovation portfolios, data governance, vendor relationships with AI companies, and increasingly the question of whether the organization's technology capabilities can actually support wherever the business wants to go next. The title has not changed. The expectation has. The organizational structure around the role, in many cases, has not changed at all.

Gartner and others regularly survey CIO priorities and role perceptions, and the directional findings have been consistent for years: CIOs report feeling pressure to contribute to business strategy while simultaneously managing day-to-day operational responsibility for systems that cannot afford to fail. That dual demand is not new. What has changed is the intensity of the strategic expectation. A decade ago, "the business" might have wanted IT to support digital initiatives. Now, in most large organizations, digital capability is not a support function. It is the business. When technology fails, revenue stops. When technology succeeds, new revenue models become possible. That is a different job than keeping mainframes running.

But here is the thing that I find genuinely interesting from an organizational theory standpoint. The way organizations evaluate and position the CIO has not caught up with that shift. Many large organizations still have the CIO reporting to the CFO rather than the CEO. The reporting structure is a signal. It says, more clearly than any job description, how the board thinks about IT: as a cost to be managed rather than a capability to be invested in. When IT reports to finance, the questions that get asked are budget questions. How much are we spending? Can we reduce it? Are we getting value for money? Those are reasonable questions, but they are not the same as: how is our technology capability enabling or limiting our strategic options?

The rise of adjacent roles tells part of the story. Chief Digital Officer, Chief Data Officer, Chief AI Officer, Chief Transformation Officer. Every time one of these roles is created, there is an implicit story being told. The story is usually that the organization wants to move in a new direction, and for some reason, the CIO as currently positioned cannot carry that mandate. Sometimes this is a legitimate recognition that digital transformation requires different skills and a different organizational charter than traditional IT management. But sometimes it is a workaround for a credibility gap. The business does not trust the CIO to lead innovation, so it creates a new role to do it instead. The CIO continues running operations. The CDO chases transformation. And the two organizations, with overlapping mandates and unclear boundaries, spend a significant amount of energy managing their relationship with each other rather than building anything.

I am not claiming all CDO and CAO appointments are credibility workarounds. Some of them reflect genuinely new capability needs that deserve their own leadership attention. But I think the pattern is worth noticing. In industries where technology is taken seriously as a competitive differentiator, you tend to see CIOs with real strategic authority, reporting to the CEO, with seats at the table where business strategy is made. In industries where technology is still viewed primarily as infrastructure, you see CIOs managing compliance and operations while new digital titles chase the transformation agenda. The title proliferation is partly a symptom of that unresolved tension.

The other side of this is that the pipeline into the CIO role still tends to run through technical or operational experience. CIOs often come up through IT infrastructure, application development, or enterprise systems. That background is real and valuable. But it does not automatically produce the communication style, the political fluency, or the business development instincts that the expanded role requires. There is a gap between the skills that got someone to the CIO seat and the skills the seat now demands. Organizations that recognize this invest in developing their CIOs as business leaders. Organizations that don't recognize it wonder why their CIO is not driving more strategic value and quietly start looking for a Chief Digital Officer.

The frustrating part, from where I sit, is that this problem has been named in the IS and management literature for decades. The shift from IT as a cost center to IT as a business enabler has been discussed for at least twenty years. The argument that technology capability is increasingly central to competitive strategy is well-documented. And yet the governance structures, the reporting lines, and the organizational expectations around the CIO role still lag the theory considerably. Naming the problem has not been enough to fix it. What seems to move the needle, slowly, is watching organizations that got the CIO role right outperform the ones that didn't, until the evidence becomes too large to ignore.