Co-Owning the Future of Work: Why AI Is Pulling HR and Technology Together, and How CHROs and CIOs Can Lead Work Redesign as Partners
The HCL Review PodcastNovember 21, 202600:26:07

Co-Owning the Future of Work: Why AI Is Pulling HR and Technology Together, and How CHROs and CIOs Can Lead Work Redesign as Partners

Abstract: Generative and agentic artificial intelligence (AI) are dissolving the long-standing boundary between the people function and the technology function. Recent surveys show that the two are rarely aligned: Gartner reports that only 38% of CHROs and CIOs share an understanding of how AI will affect work, IBM finds that 46% of organizations do not involve the CHRO when AI strategy is set, and Heidrick & Struggles finds that only one in four CHROs operates as an enterprise leader. This article examines why the HR–IT divide has become a strategic liability, what it costs organizations and employees, and which responses the evidence supports. Drawing on sociotechnical systems theory, strategic alignment research, technochange management, and more than a dozen organizational examples across biotechnology, healthcare, banking, consulting, education, manufacturing, software, and government, it proposes five evidence-based responses: formal shared ownership, work redesign before tool deployment, blended teams where structure fits strategy, governance of digital labor and human decision rights, and dual fluency for leaders. It closes with three foundations for long-term capability.

Powered by the WRKdefined Podcast Network. 

[00:00:00] Imagine finding out your newest coworker, the one who just got access to your company's entire employee database, who handles all the onboarding, and maybe even evaluates your performance, doesn't actually have a heartbeat. Right, which sounds completely like sci-fi, but it is happening. It really is. I mean, in July of 2024, a major HR software company literally tried to put AI bots on their official organizational chart,

[00:00:28] like sitting right alongside actual human beings. And the backlash from the public and honestly from their own human employees was so sudden and just so intense. Yeah, they had to pull the plug in a matter of days. It was crazy. It was a massive wake-up call though. It proved that, you know, integrating AI into the workforce isn't just an IT problem anymore. It touches the very nerve of human identity at work. Which is wild because historically, those two things were handled in totally separate buildings. Oh, completely.

[00:00:57] You had information technology over here handling the servers, the security, you know, the software licenses. And then way over on the other side of campus, you had human resources handling hiring, pay, company culture. Right. They only ever talked when like the payroll software needed a patch. Exactly. But generative and agentic AI have basically just demolished that wall.

[00:01:19] So today, we are diving into a brand new, incredibly comprehensive November, 2026 article by Dr. Jonathan H. Westover from the Human Capital Leadership Review. And it is a fascinating piece of research. It really is. Our mission for this deep dive is to unpack why this old HR-IT divide is suddenly this massive strategic liability, what it's costing organizations.

[00:01:44] And most importantly, we're going to explore the evidence-based playbook for how leaders can co-own the total redesign of our jobs. Because that redesign is happening right now as we speak. And the organizations that are trying to manage it with like a 2015 mindset are already falling dangerously behind.

[00:02:01] So whether you are leading a team or you're just trying to adapt to new AI agents suddenly popping up on your desktop, or maybe you're just frustrated by why your company's latest AI rollout feels so clunky. This deep dive is going to pull back the curtain for you. We're going to get into the hidden structural battles happening in the C-suite that actually impact your daily work. Okay. Let's unpack this. So the foundation of this entire crisis really comes down to how the technology itself has mutated.

[00:02:31] Dr. Westover's source points out this fundamental shift. Like early enterprise software was rigid, right? Right. It just did what you told it to do. Exactly. It just automated simple high-volume transactions. But generative AI and specifically these new digital agents are now executing what the research calls judgment-laden tasks. Judgment-laden tasks. That's a huge distinction. It changes everything. These are nuanced decisions that have traditionally lived entirely inside human job descriptions.

[00:02:58] Right. Because an AI that screens resumes or drafts a really sensitive performance review or, you know, coaches an underperforming manager, that's not just acting as a fast calculator. No, it's exercising a form of judgment. Yeah. Treating an AI that makes HR decisions as just another IT project is like, well, it's like having the janitorial staff conduct your annual performance reviews just because they happen to own the keys to the building. That is a great way to put it.

[00:03:24] I mean, they manage the infrastructure, sure, but they have absolutely no business managing the people. So, if this AI is doing the work of a person, its deployment has to be an HR issue. What's fascinating here is that this specific ambiguity, you know, who owns a piece of software when it essentially does the job of a human, is causing this quiet panic at the highest levels of leadership. I bet. The data from the article is just staggering.

[00:03:49] Gartner recently reported that only 38% of chief human resources officers and chief information officers share a common understanding of how AI is going to affect work. Wait, only 38%. Barely over a third. So, over 60% of the time, the executive running the technology and the executive running the workforce aren't even looking at the same map. How do you deploy a workforce strategy when the two main architects are speaking completely different languages?

[00:04:16] You generally don't, or you just do it very poorly. IBM ran a survey of 1,500 CHROs that really highlights how deep this divide is. They found 46% of organizations do not even involve the head of HR when setting their AI strategy. That is insane to me. Almost half of them just leave HR out of the room completely. Completely. The C-suite is still treating artificial intelligence as a software procurement issue.

[00:04:43] But when you introduce an autonomous agent into a department, you aren't just installing code. You are fundamentally redesigning the human workflows around it. I would imagine HR leaders are feeling incredibly exposed right now then. Oh, absolutely. I mean, the Heidrich and Struggles data in the source notes that only one in four CHROs actually operates as an enterprise leader. Right, meaning most of them are operating strictly inside their HR silo. Yeah, they lack the cross-functional influence to just step in and say,

[00:05:12] Hey, wait, this AI tool is changing our company culture. I need a seat at this table. And the CEOs see that gap very clearly. Another Gartner survey showed only 7% of CEOs believe their CHROs are AI savvy. 7%? Wow. Wow. Yeah. And compare that to 44% who feel confident in their CIOs. There is a massive capability gap right at the historical moment when these two domains, technology and human capital, are violently colliding.

[00:05:39] And that C-suite confusion isn't just some quirky organizational thing, though. It's actively setting fire to AI budgets. Big time. The disconnect has brutal financial consequences. Which brings us to some really painful numbers. Gartner found that 38% of companies are currently over budget on their AI initiatives. But the most alarming part isn't even the overspending. Right, it's the ROI. Only about 3% are actually exceeding their cost-saving goals.

[00:06:07] Almost every organization expects AI to save them money, but almost nobody is actually pulling it off. And the research explains the mechanism behind this failure beautifully. There's a concept introduced in 2004 by a researcher named Marcus called techno-change, which stands for IT-enabled organizational change. Okay, techno-change.

[00:06:26] The core principle of techno-change is that if you design a technical solution without deeply analyzing the social system, like how human beings will actually interact with it or fear it or manipulate it, it will fail predictably. So if you just bolt the change management on at the very end, like after the tool is already bought and configured, the people will just reject the system because their daily realities were never factored into the design in the first place.

[00:06:52] Exactly. They'll find workarounds or just ignore the tool entirely. And all those projected efficiency savings just evaporate on day one. Yep. The IBM Ask HR case study detailed in the source is the perfect cautionary tale for this. Back in 2017, IBM rolled out this internal chat bot called Ask HR. And they ran it purely as a tech project, right? Pure tech. They deployed the software and essentially told 20,000 workers to stop calling the HR help desk and start typing to this bot.

[00:07:21] Which resulted in the net promoter score for the entire HR department plummeting to minus 35. It was a disaster. The employees felt completely alienated. But I want to focus on how they fixed it because that's the real lesson here. IBM only turned it around when they stopped treating the chat bot as just a technical deployment and started treating it as a socio-technical system. Right. They took a step back and redesigned the actual workflow. They didn't just update the interface. They changed how the human HR agents interacted with the bot's handoffs.

[00:07:50] That's a huge difference. Yeah. They trained the bot to recognize when an employee was getting frustrated and then seamlessly transfer them to a human without making the employee repeat their whole problem. Which is the worst part of dealing with bots, honestly. It really is. By treating it as a shared human experience rather than an IT mandate, they completely flipped the script. By 2025, that same system handled 16 million messages with a plus 74 customer satisfaction score. That's an incredible turnaround. Now, here's where it gets really interesting.

[00:08:19] Because when organizations finally realize they need to treat AI like a workforce issue, sometimes the pendulum swings way too far in the other direction. Oh, definitely. Let's go back to that Lattice example from July 2024. They're an HR software company. And they announced with immense pride that they were giving AI digital workers actual employee records. They were putting software bots on the official organizational chart. Right.

[00:08:47] The assumption being, hey, if the bot is doing the work of an employee, let's treat it exactly like one. But the human backlash was so severe that Lattice's CEO had to issue a public statement reversing the decision just days later, confirming they would not pursue digital workers in their product. Yeah, the internet was not having it. But I have to push back on this a little. We just established that AI is doing judgment-laden tasks. It's not just a printer or office furniture.

[00:09:13] If it's essentially doing the work of a human, why shouldn't it be on the org chart? Why did actual human employees hate that idea so viscerally? This raises an important question about a psychological mechanism called algorithmic control. And it touches the very core of human dignity. Human dignity. Okay. Say more about that. Well, research by Kellogg and colleagues demonstrates that when algorithmic systems begin to recommend or restrict or evaluate human workers,

[00:09:42] people instinctively resist it if they feel the system lacks legitimacy. Because it feels like you're being managed by a black box. You can't reason with it. Exactly that. Imagine a human manager gives you a poor performance review. You can argue with them. You can appeal to their empathy. You can explain the contextual nuances of why a specific project failed. You retain your human agency. Right. There's a conversation. But when an algorithm gives you a bad rating, you are being judged by math.

[00:10:10] It strips away your ability to appeal. When Lattice tried to put software on the org chart as a coworker, it blurred a line that makes humans deeply uncomfortable. It signaled that human identity and software utility were essentially interchangeable. I see. So you can govern a piece of software using HR principles without pretending it's a person. You don't need to give a bot a birthday cake or an employee ID badge to hold it accountable for its output. That distinction is paramount.

[00:10:38] You must govern the digital labor. But if you anthropomorphize it to the point where it threatens the identity of your human workforce, you will absolutely face a revolt. So because tech first approaches fail and treating AI like a human sparks a revolt, organizations are scrambling to find this structural middle ground. They know the old divide between HR and IT is broken. But the ways they are attempting to fix it are incredibly polarizing. Very much so.

[00:11:05] We're seeing some massive reorganizations on opposite ends of the spectrum. The source outlines some highly radical approaches. Moderna, the biotech company, they decided to completely obliterate the wall. They merged their human resources and digital technology functions under a single executive. Wow. A single executive for both? Yeah. Her mandate isn't just to manage people or manage servers. It's to, quote, architect the flow of work. And under that merged structure, they've deployed over 3,000 custom GPTs.

[00:11:34] 3,000? 3,000. That is wild. And smaller firms like WorkLeap and Cavizian have simply folded their IT departments entirely underneath their HR leadership. Which makes a lot of sense if you view technology purely as a tool to serve the human workforce. But then you have this inverse risk. Fortune reported that some AI native companies are going the exact opposite direction. They are putting technologists and product operations leaders in charge of HR. Right.

[00:12:02] And this brings up a massive red flag from Wharton's Peter Capelli in the source material. If we put optimization-obsessed engineers in charge of human beings, aren't we just going to see massive head count cuts instead of employee development? I mean, the core function of an engineer is to eliminate friction and redundancy. Right. They want to streamline everything. Exactly. But human beings are, by definition, full of friction and redundancy. It is a profound danger. Yeah.

[00:12:29] And to truly understand why that tech-led approach to HR often fails, we actually need to look backwards to a foundational study from 1951 by researchers Tristan Bamforth. They were studying the transition to mechanized coal mining. Wait, hold on. We're talking about generative AI and you're bringing up 1950s coal mining. I'm struggling to see how digging coal relates to deploying a large language model.

[00:12:55] I know it sounds crazy, but the mechanism of human reaction to technology hasn't changed. In the mines, a highly efficient technical system, this mechanized conveyor method for extracting coal, was introduced to replace the old manual methods. Okay. It was designed entirely by engineers for maximum mechanical optimization. It looked perfect on a blueprint. But it completely broke apart the tight-knit, self-regulating social groups of the miners.

[00:13:20] They went from working in small, communicative teams to being totally isolated along a massive conveyor belt. Ah. So the technical system just completely ignored the social fabric of how the work actually got done. Yes. And the result. Absenteeism spiked, psychological stress skyrocketed, and productivity actually plummeted below the old manual methods. Wow. This became the founding evidence for socio-technical systems theory. You cannot design the technical system without simultaneously designing the social system.

[00:13:50] So when we look at Moderna merging departments or tech companies putting engineers in charge of HR, the actual structure, like whose name sits at the top of the org chart, is secondary. So it doesn't really matter if IT reports to HR or HR reports to IT as long as the design process is shared. Exactly. What matters is co-ownership. The CHRO and the CIO must be jointly accountable for how the technology and the humans interact.

[00:14:18] But if simply smashing the departments together isn't a guaranteed silver bullet, what does that co-ownership actually look like in practice? Because fortunately, the research lays out a highly specific five-step playbook for how organizations can successfully govern digital labor without tearing apart their human culture. Yeah. And step one requires formal, codified governance. You cannot rely on the HR leader and the IT leader just having a good relationship and occasionally chatting over coffee. Right.

[00:14:47] The source points to Advocate Health as the gold standard here. They are a massive organization with hundreds of thousands of employees. They didn't just hope for collaboration. They created a written charter called Work Forward Plus. It's brilliant. They literally paired their chief people officer and their chief AI officer to jointly lead the redesign of work. They share metrics and govern through joint councils. It is hardwired right into the operating system of the business.

[00:15:14] And that formal structure is what enables step two, which is that work redesign must precede technology deployment. You have to map the human workflow first, identify the friction points, and then figure out how AI can augment the human rather than just buying an AI tool and telling the humans to figure it out. The West Monroe consulting firm example illustrates this perfectly. They looked at their agonizing process of staffing project teams. It used to require like a week of back and forth emails between managers and consultants. It sounds painful.

[00:15:44] Totally. HR and IT mapped that specific pain point together, and they custom built a chat bot to automate the scheduling. It now does the work of three full-time employees, saving them a million and a half dollars a year. But this is the crucial nuance here. They didn't fire anyone. Instead, they deliberately slowed down future hiring to absorb that new efficiency. And that decision, the deliberate reinvestment of freed capacity, is what separates a sustainable AI deployment from a toxic one.

[00:16:13] If an AI saves a million dollars in time and the immediate reaction of leadership is just to fire three people, the remaining employees will aggressively resist the next AI tool. Of course they would. They'd see it as a direct threat to their livelihood. Exactly. By slowing hiring instead, West Monroe preserved the psychological safety of their current staff. But mapping the workflow and preserving jobs is only half the battle. Once that chat bot is actually running the schedule, who is in charge of it?

[00:16:40] If it makes a mistake, who gets reprimanded? Right. That brings us to steps three and four of the playbook. Creating blended teams and establishing digital governance. And we are getting into some really wild territory here. The financial services company BNY is cited as having nearly 140 digital employees. Digital employees. Yeah. They have login credentials. They operate within the systems. But crucially, every single one has a named human supervisor.

[00:17:08] And that human supervisor is not just a bureaucratic rubber stamp. It is a vital defense against something researchers call the jagged technological frontier. The jagged frontier. Mm-hmm. How does that actually play out in a daily workflow? So, AI capability does not scale linearly. An AI might be able to instantly synthesize a hundred page financial report with perfect accuracy, which is highly complex. Right.

[00:17:32] But then it might completely hallucinate a basic compliance check that a first week intern would catch in five seconds. The boundary of what AI can and cannot do isn't a smooth, predictable line. It is jagged. It fails unpredictably on tasks that fall just outside its training. Think about the software you use right now. If it flags something incorrectly, do you feel empowered to tell your boss the machine is wrong? Or do you just quietly fix it so you don't look like a bottleneck? It happens all the time. Right.

[00:18:01] And because of that jagged frontier, organizations must grant their human employees protected override rights. If an AI agent recommends declining a customer's loan or rejecting an expense report, the human supervisor must have the explicit protected authority to say, no, the algorithm is hallucinating here, without fear of being penalized for bucking the system. To do that effectively, though, the human needs to understand how the AI thinks.

[00:18:28] And the IT team designing the AI needs to understand how the human works. That is step five, dual fluency. I think of it like needing to speak both the language of the motherboard and the language of the break room. That's a perfect analogy. HR leaders have to learn about data architecture, large language models, and latency. IT leaders have to learn about employment law, change management, and human motivation. It goes both ways. Intuit is actually modeling this dual fluency brilliantly.

[00:18:57] Their chief technology officer reportedly spends a full third of his time directly with the HR team. He is actively working on skills roadmaps and external hiring decisions. You can't just hire a consultant who knows both fields. You have to cross-pollinate your existing leadership. But none of this playbook works without three long-term foundational pillars that Dr. Westover outlines in the research. First, you must have a shared workforce data architecture.

[00:19:25] HR systems and IT systems just have to communicate flawlessly. Which is easier said than done. Oh, it's incredibly hard. The U.S. federal government is attempting this right now, trying to merge over a hundred disparate HR systems into a single commercial platform. It is an absolute logistical nightmare. But it's the only way to get a unified view of the workforce and the technology infrastructure. The second pillar is a single scorecard.

[00:19:50] Historically, IT is evaluated on server uptime, compute costs, and adoption rates. HR is evaluated on turnover, employee engagement, training times. Totally different metrics. Right. And if you keep those separate, they will always be at war. IT wants to deploy fast and cheap. HR wants to deploy slowly with extensive training. You need a unified scorecard.

[00:20:12] The CHRO and the CIO have to succeed or fail on the exact same metrics, measuring system uptime right alongside employee skill growth. And the third foundation is psychological safety. We mentioned override rights earlier, but it goes deeper than that. The technology is moving so fast that work will need to be redesigned repeatedly. Like constantly. Exactly. If your culture penalizes an employee for pointing out that a new AI tool is actually making their job harder, you lose the safety net.

[00:20:41] You lose the human judgment you are paying those people for and the organization will just calcify. So what does this all mean? The core takeaway from all this research is that the next decade of business is not going to be won by the companies that simply throw the largest budgets at the most advanced AI tools. Not at all.

[00:20:58] It will be won by the organizations where the chief information officer and the chief human resources officer sit at the exact same table, sharing the exact same metrics to deliberately design how human beings and digital agents work together. If we connect this to the bigger picture, achieving that true co-ownership requires leaders to completely drop their territorial egos. The old boundaries between the systems department and the people department are gone.

[00:21:27] Today, every single technology decision you make is fundamentally a people decision. Yes. And every workforce strategy you design is fundamentally a technology decision. It's a completely new reality. We spent this entire deep dive analyzing how companies need to restructure and manage this shift from the top down. But I want to leave you with something to think about regarding your own day to day life. It's a big question.

[00:21:49] As digital labor continues to take over more of the routine tasks on your plate and your most reliable, responsive and productive colleague suddenly becomes an autonomous AI agent, what happens to the human culture of your team? Does the very definition of what it means to be a co-worker fundamentally change when half your team doesn't have a heartbeat? It really makes you wonder. Are we still operating in two separate buildings? Or are we constructing something entirely new?

[00:22:18] Thanks for joining us on this deep dive. Keep questioning the systems around you. Thank you.