People Operations Is Not a Rebrand: It's Strategic Infrastructure

[00:00:00] Have you ever started a new job? And like by day three, you are just completely tearing your hair out. Oh, absolutely. It is such a... It really is. Yeah. And our mission today is to figure out why companies can't just slap the trendy new title of people operations onto their old HR department and expect everything to, you know, magically work. Right. Because it never does. Never. We are going to look under the hood at the hidden structural gears that actually make an organization run smoothly.

[00:00:28] Or cause it to completely crash and burn. The core premise we are dealing with here requires a total paradigm shift. When you are sitting there at your desk without a laptop, navigating broken links in an onboarding portal, your natural reflex is to blame bad software. Oh, for sure. Or you just assume the IT guy is ignoring you. Exactly. Or you think the administrator you emailed is just incompetent. But what the source material reveals is that these are rarely software problems and they are rarely training problems.

[00:00:58] Really? Then what are they? They are deep structural problems rooted in organizational design. You are experiencing the friction of a poorly built company structure. Okay. So to really understand why companies fail at fixing these structural problems, we have to look at how they mistakenly try to solve them with superficial rebranding. Because the data on this is wild. It really is.

[00:01:22] According to a 2023 Talent Strategy Group survey, 47% of organizations out there claim to have a people operations function. Basically half the corporate world is walking around saying they've modernized. Right. They have the trendy title on the door. But when you look at the actual reporting structure, like who answers to whom the reality is entirely different? How so? Well, of those companies claiming to have people operations, 31% of them just subordinate it under their traditional shared services. Oh, wow.

[00:01:51] Yeah. And another 23% place it under a single vertical HR pillar like talent acquisition or total rewards. Only 28% actually position it as a true peer function to those other departments. It's a classic vertical versus horizontal problem. Think of building a house, right? Vertical integration is having the absolute best deep domain experts. You hire the best plumbers and the best electricians in the entire world. Right. They are masters of their specific craft. Exactly. They know their specific verticals perfectly.

[00:02:21] But if you don't have a horizontal general contractor making sure the plumbing pipes don't run straight through the electrical panel, the house is going to burn down no matter how brilliant the individual experts are. That is a perfect analogy. Thanks. In a company, people operations is supposed to be that general contractor. It's a horizontal integration connecting the data and the processes across all those different expert areas. What's fascinating here is that when an organization places people operations under one of those vertical pillars, say,

[00:02:50] having the general contractor report directly to the plumber, the people operations team completely loses its enterprise wide reach. Because they can't tell the other verticals what to do. Exactly. They have absolutely no authority to tell the electrician what to do. So instead of architecting a cohesive system, that horizontal team just inherits all the administrative grunt work that the deep domain experts reject. Oh, so they just become assistants basically. Pretty much.

[00:03:17] The vertical experts focus on their shiny policy designs and the people ops team just becomes a glorified help desk running around putting out fires. It completely stalls any real maturity in the system. And because so many organizations lack this general contractor, the resulting fragmentation isn't just a minor annoyance for employees. It is bleeding massive amounts of time and money, which leads us to some staggering hard data. The numbers are honestly hard to believe.

[00:03:45] Yeah. 15 to 25 percent of an HR department's capacity is lost to rework workarounds and coordination overhead like a quarter of the department. Let's visualize the scale of that for a second. If you have an HR function sporting 10,000 employees with a staff of 100 people, Well, 15 to 25 of those full time employees are doing absolutely nothing but compensating for structural fragmentation. That is insane. But they are manually reentering data from an Excel sheet into a web portal because the systems don't talk to each other.

[00:04:14] They're just chasing down errors and fixing broken handoffs all day. And without horizontal governance, organizations see data error rates of 12 to 18 percent in employee records. Which is a huge liability. Huge. Plus, there is a massive toll on the rest of the company. Line managers are wasting four to six hours every single week just navigating HR complexity. Just trying to get basic things done for their team. Right.

[00:04:40] And the HR business partners, the folks who are supposed to be doing high level strategic consultation, they are spending 35 to 50 percent of their time on administrative tasks. Instead of actually partnering with the business. But wait, I have to push back on this a little bit. Yeah. Organizations spend millions and millions of dollars on enterprise HR tech. We have these massive software platforms now that promise to integrate everything. Shouldn't the software solve this? I mean, are people just bad at using new HR platforms? It is a really common assumption.

[00:05:09] But the research directly contradicts the idea that software is a cure all. Really? Yeah. The tech only works if the structure mandates someone to connect the systems. Organizations with dedicated integration functions see 73 percent faster time to value on their tech investments and 42 percent higher system utilization. Software isn't magic. But how do you mandate that without just becoming like a dictator that the other departments resent?

[00:05:39] If I run the talent acquisition vertical and I want a specific recruiting software, I don't want the people ops team telling me no. And that's exactly why you get platform proliferation. If you leave it to distributed responsibility, every vertical team buys a tool that optimizes their own specific workflow without considering the system level impacts. Ah, I see. The recruiter buys a tool they love, but it doesn't integrate with the compensation team's payroll system. Suddenly data has to be moved manually.

[00:06:05] The software fails because the organization didn't mandate anyone to integrate it. So everyone is just optimizing for their own little silo. Exactly. And the consequence, when HR delivery is fragmented like that, it leads to 22 percent lower employee satisfaction and an 18 percent higher perceived administrative burden from employees.

[00:06:24] OK, let's unpack this because if software isn't the magic bullet and structural authority is the real answer, we need to look at how a company actually reorganizes that power dynamic in the real world. Yes, we need a practical example. The source material provides a brilliant case study on Tesco. They are dealing with multiple brands, massive geographies and incredible complexity. So what did they actually do? They completely reorganized their power structure by moving to a four pillar model.

[00:06:54] They had their centers of excellence, their business partners, their shared services, and then they created this fourth pillar called people platforms. OK. And the critical move was making people platforms a true peer to the other three. This is about being invited to the executive table versus just taking notes from the hallway. You can't fix a broken system if you report to the people who are breaking it. You have to have the same amount of leverage. Precisely. They established what the research calls boundary spanning authority. Boundary spanning authority. I like that.

[00:07:22] Tesco succeeded because they gave their people platforms team the explicit mandate to prioritize the needs of the entire enterprise over the preferences of any individual pillar. And they reinforced this with a governance mechanism called big room planning. Wait. What does big room planning actually look like in practice? How does that resolve a conflict? Imagine the talent acquisition pillar wants to buy that shiny new recruiting software we talked about earlier. Right.

[00:07:51] But the compensation pillar realizes it's going to corrupt their payroll data. In a traditional structure, they just fight about it or the louder executive wins. Or whoever has the bigger budget. Exactly. Yeah. In big room planning, they bring all the pillar leaders together quarterly. The people platforms team acts as the tiebreaker holding the ultimate authority on system architecture. Oh, so they actually have the power to say no. Yes. They align priorities and explicitly resolve conflicts about who owns what work and what tools are allowed in the ecosystem.

[00:08:19] And the results of giving someone that authority speak for themselves. Tesco saw a 30% reduction in process cycle times and a 40% decrease in HR service desk volume. It's incredible. Because the general contractor finally had the authority to tell the electrician and the plumber how to route their wires and pipes, the system started working for the people instead of the people working around the systems.

[00:08:43] And for the employee listening, that 30% reduction in cycle time is the difference between waiting a month for your benefits to kick in versus having them active by the end of your first week. That is huge. Yeah. So once the general contractor actually has the authority to dictate the blueprint, the very first thing they have to fix are the tools the workers are using. This leads us to NatWest Group. Right. Another great case study.

[00:09:07] They make digital technology a foundational piece of their people operations rather than just outsourcing it to corporate IT. That is a crucial distinction. In most companies, HR goes to the IT department, begs for resources and waits in line behind 50 other corporate projects. Yeah. You're just a ticket in the queue. Exactly. But NatWest brought that architectural capability in-house to people operations. They didn't just ask IT for a tool.

[00:09:34] They led the enterprise platform selection to ensure vendors met strict integration requirements rather than just optimizing for individual siloed use cases. And doing that led to a 60% reduction in platform implementation timelines and a 45% improvement in data accuracy. Which is just massive. It is wild what happens when you actually own the tools you use. Then there's Peabody, a UK housing association, who took this a step further. They gave people operations end-to-end accountability for processes.

[00:10:03] Not just the tools, but the actual workflows. Exactly. They meticulously mapped out major HR processes and used cross-functional improvement teams. And they saw a 35% reduction in time to hire and a 40% decrease in leave-related queries. Their methodology is what really stands out to me though. Peabody used a pilot iterate scale approach. I want to dig into that because I've seen companies try to just overhaul everything at once.

[00:10:27] Is it better to fix an entire broken system piece by piece in specific regions rather than just ripping the band-aid off enterprise wide? If we connect this to the bigger picture, trying to digitize a broken enterprise system all at once isn't ripping off a band-aid. It's like trying to update the operating system of an airplane while it's in mid-flight. That sounds terrifying. It is incredibly risky. This is a trap so many companies fall into.

[00:10:54] They take an incredibly complex, inefficient manual process and they just digitize it. So they just make the bad process digital. Right. All that does is make a bad process fail faster. Peabody's iterative scaling prevents this. You have to simplify a process before you write a single line of code. So how does the pilot work? You pilot the redesign in one geography, you collect feedback, you refine the workflow and then you scale. It forces you to fix the underlying mechanics before locking them in. That makes total sense.

[00:11:23] And optimizing that software and those processes is ultimately about serving the human on the other end. But doing that requires a completely different breed of talent to orchestrate. It really does. Adobe is a prime example here. They built a function called employee experience and operations. They mapped out the entire employee journey, specifically focusing on onboarding. And they intentionally shifted all the heavy paperwork to the pre-hire phase.

[00:11:49] Which is brilliant because day one should be about connection, culture and meeting your team. It shouldn't be about sitting in a windowless room filling out tax forms for six hours. Yes. I remember my last onboarding just drowning in PDFs. But by making that structural change, Adobe reduced manager admin time by 50 percent, raised new hire confidence by 35 percent and accelerated the time to productivity by three entire weeks. Three weeks.

[00:12:17] That is three extra weeks of a new employee actually doing the job they are hired for instead of fighting with the system. And that touches on a really profound concept in the research, the psychological contract between the employer and the employee. Here's where it gets really interesting, especially for anyone listening who has ever felt totally disconnected at work. There's a quote in the source material from a tech professional that really stuck with me. Oh, I know the one you mean.

[00:12:42] They said, if they can't get onboarding right after doing it thousands of times, why would I trust them to get promotion decisions or compensation equity right? It hits hard. Think about that. This explains why top performers quit when basic administrative things are chaotic. It entirely shatters the psychological trust between employee and employer. It absolutely does. Employees expect consumer grade experiences now. When you order something online, you track it to your doorstep in real time.

[00:13:12] Exactly. On your phone. Right. If your internal company systems feel like they were from 1995, employees immediately perceive the entire organization as administratively incompetent, regardless of how strategic your business goals are. That makes perfect sense. And fixing this requires a very specific kind of talent. Transaction excellence, which is what traditional shared services does, like processing a payroll check perfectly and system integration are entirely different capabilities.

[00:13:39] So you're saying you can't just take your absolute best payroll processor, promote them and expect them to suddenly architect a seamless digital employee journey. Exactly. Look at Microsoft's people analytics function. When they built their horizontal infrastructure, they didn't just hire traditional HR folks. They went out and hired data scientists, research methodologists and organizational psychologists. Wait, what is a data scientist doing in HR that a traditional HR rep isn't?

[00:14:06] Well, a traditional HR rep looks at a spreadsheet of exit interviews to see why people left last month. Right. Looking backward. A data scientist builds predictive models using complex data architecture to forecast which high performing teams are at risk of burnout six months from now based on their collaboration metrics and system usage. It is a completely different mindset. You need systems thinkers, process designers and change managers.

[00:14:31] If you hire for operational execution and expect architectural design, you will fail every time. Okay. So let's say a company does all of this right. They get the enterprise mandate. They establish the general contractor. They hire the data scientists and they beautifully map the employee journey. Dream scenario. Right. But even after all of that heavy lifting, the article warns about a hidden lingering danger regression.

[00:14:57] The natural organizational gravity that constantly pulls teams back into their comfortable siloed habits. Right. Because vertical teams naturally want to optimize for themselves. It is human nature to want direct control over your own tools and your own budget. Of course it is. Over time, those centers of excellence will try to reclaim control over technology decisions. The talent acquisition team will sneak out and buy a rogue piece of software again. To fight that gravity, you need serious governance mechanisms.

[00:15:24] The research outlines a few non-negotiables. You have to establish formal work placement criteria so when a new task pops up, it isn't just dumped on people ops by default. Yes. Very important. You need those cross-pillar planning forums we talked about. Yeah. Like the big room planning. And you need explicit escalation paths for when departments inevitably disagree. Because they will disagree. Oh, constantly.

[00:15:48] It's also about treating HR data as a strategic asset moving from just descriptive analytics, which is tell you what happened, to prescriptive analytics, which tell you what we should do next. This raises an important question about accountability within an organization. Think about a process like hiring and onboarding that spans across multiple different departments. Oh, yeah. It's never just one team. You have recruiting, background checks, IT for the laptop, facilities for the desk, and the actual hiring manager.

[00:16:17] If nobody is explicitly placed in charge of the handoffs between those departments, shared accountability usually just means no accountability. Everyone assumes someone else is doing it. Exactly. When everybody owns a piece of the puzzle, nobody owns the picture. Governance is what ensures the horizontal function maintains its authority over those handoffs so the ball doesn't get dropped. So it's basically the glue holding everything together.

[00:16:41] Without governance, the people operations mandate just erodes over time until you are right back where you started. So what does this all mean for you listening right now? Whether you are leading a massive team, prepping for a strategy meeting, or just trying to navigate your own frustrating workplace, understanding how power and accountability are distributed explains why things either flow beautifully or constantly get stuck. It is so crucial to understand. It is never just a glitch in the software.

[00:17:09] It is always about the structural design of authority. To wrap this all up, people operations is only real if it has three essential things. First, it needs structural authority as a peer at the executive table. Second, it needs the right multidisciplinary talent architects, not just administrators. And third, it needs the enterprise mandate and governance to act as the horizontal connective tissue of an organization.

[00:17:37] Otherwise, it is quite literally just a shiny new nameplate on a broken system. It is a powerful framework. And I want to leave you with one final thought to mull over that takes this beyond just the workplace. Oh, I like where this is going. We've just spent all this time seeing how magical horizontal integration is for an HR department. But what if we applied this exact same framework to our own lives? Okay. Think about the vertical pillars of your daily routine. You have your finances, your physical health, your career, your relationships.

[00:18:07] Do you have a horizontal infrastructure connecting them? Or are they operating in completely isolated silos? Wow, that is deep. Is your intense career optimization breaking down your physical health because the two don't talk? Are your financial goals disconnected from your relationship goals? Are you waiting for a system failure in your own life because nobody is actively managing the handoffs? Wow. Be the general contractor of your own life. Thank you so much for joining us on this deep dive. Keep questioning how the systems around you are built. And we will catch you next time.