I spend most of my week talking to CHROs and the CEOs who hire them, and there is a story taking hold in the market that I want to push back on. The story goes something like this: AI is fundamentally a people transformation, therefore the CHRO should personally lead it. They should redesign the jobs, reskill the workforce, evaluate the vendors, and own the roadmap. It has become the default assumption in board conversations, in executive team offsites, and in more than a few job specs I have read this year.

I understand the logic, and I even agree with part of it. AI absolutely is a people transformation, and the CHRO absolutely has to lead it. But leading something and personally carrying it are two very different things, and we are quietly conflating them in a way that is going to cost companies real time and real talent. The CHROs I see pulling ahead right now are not the ones who are working longer hours. They are the ones who insisted, early, on a different structure underneath them.

Let's start with the honest part. The CHRO day job has not gotten one ounce lighter to make room for AI. If anything, the traditional mandate has expanded. The CHROs I work with are deeper in CEO strategy conversations than ever, spending more time in the boardroom, running more sophisticated succession work, redesigning organizations mid-flight, navigating compensation cycles that keep getting more complex, and holding culture together through waves of change that would have been considered once-in-a-decade events a few years ago. None of that work shrinks. None of it delegates cleanly. And none of it is going away because a new technology arrived.

The great ones also do serious work outside the building. They sit on boards. They cultivate advisory relationships. They stay close to the CEO networks and thought leaders who keep their thinking sharp. I am a broken record on this with the CHROs I coach, because that external ecosystem is not a nice-to-have. It is what separates a competent functional leader from someone who genuinely shapes the enterprise. Every hour a CHRO spends personally scoring AI vendors is an hour they are not spending on the relationships and perspective that make them worth their seat at the table.

So when exactly is this person supposed to master every HR tech platform, evaluate the AI landscape end to end, build an implementation roadmap, and drive transformation across the function? The answer, as far as I can tell, is that they are not supposed to do it alone, and they are not likely to do it well. The companies getting this right are already building the role underneath the CHRO. Sometimes it is a Chief HR Technology Officer. Sometimes it is a Head of HR AI Transformation. Sometimes it is a COO for HR, or an expanded remit for a superstar Head of Talent who has earned it. The title is less interesting to me than the mandate. Someone owns the roadmap. Someone drives vendor decisions. Someone translates AI capability into workforce strategy and keeps the function from quietly falling eighteen months behind while the CHRO does what only the CHRO can do.

We already know how this movie ends, because we have watched it in every other function. Nobody expects a CFO to personally architect the financial systems stack. Nobody expects a CMO to run the martech environment on their own. Finance and marketing built that supporting infrastructure years ago because the complexity demanded it, and the leaders got sharper, not weaker, as a result. HR is now sitting in exactly the same moment, and the operating model has to catch up. The best CEOs I talk to already see this, and they are actively broadening the function, elevating its seat, and resourcing the structure around it. They are not doing it as a favor to their CHRO. They are doing it because they want to win.

I know the counterargument, because I hear it weekly: adding another senior HR leader creates coordination overhead. A strong CHRO with good consulting partners should be able to steward this without expanding the org chart. In some mid-sized companies, that is genuinely true for a season, and I would not tell those CHROs to over-build. But consultants do not own outcomes, and the moment AI moves from pilots to platform, the workload stops behaving like a project and starts behaving like permanent operating reality. Permanent work needs permanent ownership. Renting the capability keeps a CHRO informed. Building it puts the company ahead.

I keep coming back to this: the assumption that one leader can personally run the largest workforce transformation in a generation, while also running the most people-intensive function in the company, is not a vote of confidence in the CHRO. It is a design flaw dressed up as trust. The CHROs pulling ahead right now are not smarter or more tireless than their peers. They have a different structure behind them, and a CEO who understood the moment early enough to build it. So, if you are a CEO, the question is not whether your CHRO should lead AI transformation. The question is who you are building underneath them to make that leadership real. If you are a CHRO reading this and nodding, my honest question back is simpler: are you asking for that role yet, or are you still trying to carry it alone?

‍