When I started in technology, the job was legible. You were measured on whether the systems stayed up, the projects landed roughly on time, and the budget held. Do those well and you were a good IT leader. It was a demanding job, but it was a knowable one, and it lived comfortably in the back office where it was largely left alone.
That job description quietly expired, and nobody handed us the new one. The role I hold today has almost nothing in common with the one I trained for. I sit at the pulsing heart of the enterprise, accountable for things that were never on any IT job spec, expected to think like a strategist, operate like a general manager, and lead people through change across borders and cultures. The title stayed the same. The job underneath it was rewritten. This is my attempt to describe the new one, because I think a lot of us are living it without ever having named it.
The oldest version of the role was about doing. Build the thing, run the thing, fix the thing. Then it became about managing the people who do those things. The shift now underway is larger than either. Deloitte’s 2026 study of technology leaders found that 79 percent now name driving business outcomes as their top priority, a decisive move away from running systems toward creating enterprise value, and it argues that technical expertise alone is no longer enough for the job. McKinsey, surveying more than 600 technology and business leaders, goes further and describes the top CIOs as strategy architects who are weaving AI and data into the operating model itself, no longer just managing technology but shaping the company’s future. The industry press puts it more bluntly, as a move from back-office order taker to full business partner.
The pattern holds on my side of the language divide too. A recent French barometer found that 78 percent of information-system directors now see themselves as key partners to general management rather than a support function. The word support has quietly disappeared from how the best of us describe what we do.
What all of this really says is that the center of gravity of the job moved from doing to deciding. Not what can we build, but what should we build, why, in what order, and to what end. That is a different discipline entirely, and it is not one that technical mastery prepares you for on its own.
The four muscles the old job never trained
If I try to be concrete about what the modern role demands beyond technical judgment, it comes down to four capabilities that the classic IT career simply did not develop.
Business acumen at board level. I am expected to speak in revenue, margin, working capital and risk, not in systems and roadmaps, and to make the case for technology in the only language a board actually funds. This is a real skill, learned mostly by getting it wrong in front of senior people a few times, and it is now table stakes rather than a nice-to-have. The technology leader who can only talk technology has already lost the room.
Strategic thinking under genuine uncertainty. The job used to be executing a plan handed down from the business. Now technology often is the strategy, or at least reshapes what strategy is possible, and I am expected to help set direction rather than just deliver against it. AI has sharpened this to a point. The board conversation has shifted from how do we use AI for growth to how do we govern the intelligence already defining our future, and that governance question lands squarely on my desk.
Leadership across borders and cultures. My teams span several countries, and coordinating technology across them is the smaller part of that challenge. The larger part is leading people who work differently, decide differently, and define good differently, without flattening what makes each of them effective. No systems-design course teaches this. You learn it by doing it, usually after a few costly misunderstandings.
The soft skills, which turn out to be the hard ones. Persuasion, listening, building trust, reading a room, managing the politics of change. For years these were treated as secondary to technical brilliance, the things you tolerated in an expert if the expertise was strong enough. In the modern role they are primary. Most of what I do now is move ideas and people, and almost none of that is technical. The label soft skills has always undersold how difficult and decisive they are.
Why the heart of the enterprise sits here now
There is a reason this role expanded rather than some other one. Technology stopped being one function among many and became the substance almost every other function now runs on. When the way you sell, deliver, decide and protect the company is all mediated by systems and data, the person accountable for those systems and that data is no longer adjacent to the business. They are inside its bloodstream.
That is why I think of the modern information system as the pulsing heart of the enterprise rather than its plumbing. Plumbing you notice only when it fails. The heart sets the pace of everything else. Deloitte found that only 1 percent of technology leaders report no major operating-model change underway, which is a polite way of saying the transformation is universal and there is no version of this job that gets to sit it out. The role grew because the thing it is responsible for moved to the center.
What I would tell someone stepping into it
If you are a strong technologist moving into this seat, the hard news is that the skills that got you here are now the entry ticket, not the job. They matter, and I would not trust a technology leader who lost their feel for the technology entirely. But they are the floor. The job is built on top of them out of judgment, persuasion, business fluency and the ability to lead people through change they did not ask for. The good news is that this is the most consequential the role has ever been, and the most interesting. We are no longer the department that gets told what to build. We are increasingly in the room where it is decided what the company should become, and asked to help decide it. That is a genuine privilege and a genuine weight, and it deserves to be met with more than technical excellence.
Nobody wrote down the new job description. We are drafting it in real time, in the choices we make and the way we show up at the top table. I would rather have a hand in writing it than wait for someone to hand me a version that no longer fits the work. The role earned its place at the heart of the enterprise. The task now is to be worthy of the seat, which asks a broader kind of leader than the one the old job ever required.
