Share with your CHRO
The question of whether to merge the CHRO and CTO roles gained real organizational weight when Moderna folded both functions under a single executive, and Harvard Business Review used that move as a prompt to pressure-test the idea with three practitioners. The resulting roundup is unusually candid: Keith Ferrazzi argues for cross-functional “teamship” over structural merger, Wharton’s Peter Cappelli says small paired HR-AI teams beat any org chart change, and Kalifa Oliver says the right answer depends entirely on what problem the company is actually trying to solve.
What this means for your business
Where you stand on this debate is mostly a function of how broken the HR-technology handoff already feels inside your organization. If your AI pilots keep stalling because IT deploys tools that employees won’t adopt, and HR designs change programs without understanding what the tools actually do, that gap is the real problem, and a reporting-line change is the least reliable fix for it. Companies with high org-chart complexity, strong functional identities, or unionized workforces will find the merger path particularly treacherous.
Cappelli’s point deserves more weight than it typically gets in these conversations. AI implementation fails most often not because two boxes on an org chart don’t report to the same person, but because nobody has mapped what workers actually do at the task level, the dozens of sub-tasks inside any given role, well enough to know where AI can intervene. That mapping work requires HR fluency and technical fluency simultaneously, and it almost never happens because the two functions are structured to operate on different rhythms and different definitions of success. A formal merger doesn’t create that shared fluency; it just creates one executive who is probably expert in one domain and a tourist in the other.
The Cisco “AI Control Hub” model, a cross-functional team spanning HR, IT, legal, finance, and security without changing any reporting lines, is the more replicable pattern here. It preserves functional depth while forcing shared accountability on specific deployment goals. The Gap example, where the Chief People Officer and CTO co-authored a single “North Star” metric for the technology program, shows the same logic operating at the leadership level. Neither required a structural merger. What they required was a willingness to be evaluated on the same outcome, which is a governance design question, not an org design question.
The budget implication CHROs should take seriously is this: if your company is about to greenlight another AI tooling investment without first funding the task-level workflow analysis Cappelli describes, the tool will underperform and the blame will land on HR for failed adoption. The choice to own that analytical work now, before procurement locks in a platform, is worth more than any title change. I’d revise this view if a company could demonstrate a merged CHRO-CTO role that produced measurably faster AI adoption than a well-governed cross-functional team, but no such evidence appears in this piece or anywhere else yet.
Based on reporting from AI Deep Integration in Organizations: Should CHRO and CTO Roles Merge?, originally published 2026-11-11 19:50:00.

