A Conversation about People Operations: Strategic Infrastructure for the Integrated HR System

[00:00:00] So I want you to imagine walking into a luxury hotel. Like you've booked this place months in advance. Right, you're expecting a great experience. Exactly. You check in at the front desk, but instead of handing you a room key, the concierge slides over a hammer. A hammer. Yeah, a hammer, a box of loose wires, and like a map of the plumbing system. Oh wow. And then they just smile and tell you to go up to the fourth floor and finish building your own bed before you can go to sleep.

[00:00:28] And you know, if you actually complain about it, they probably just give you an email address for a support portal. Right. One that auto replies in like three to five business days. Yeah, exactly. I mean, it sounds completely insane when we talk about a hotel, right? We would never ever tolerate that as a consumer. No, of course not. You'd ask for a refund immediately. But according to this massive body of structural research we are unpacking in today's Deep Dive,

[00:00:56] that is exactly what your company is probably doing to you on your first day of work. It really is. You show up, you know, eager to start your new job and suddenly you realize the building is actively under construction while you're trying to live in it? Yeah, it's um, it's not a great feeling. Right. IT doesn't have your laptop ready. Human resources is sending you like conflicting emails with broken links to benefits portals. Oh, the broken links are the worst.

[00:01:23] And your new manager is just completely buried in administrative paperwork, just trying to get you a physical security badge so you can actually use the elevator. Which is just the absolute definition of organizational fragmentation. I mean, it's chaos. It really is. And the irony, of course, is that the company just spent, you know, tens of thousands of dollars and sometimes months of aggressive recruiting just to convince you to join them. Oh, for sure. They sold you on their amazing culture.

[00:01:47] Right. Their culture, their seamless operation. And then on day one, they just instantly break that trust. We tend to look at those moments, you know, and think, well, wow, somebody really dropped the ball. Or, um, this company just has a terribly incompetent HR department. That's the default assumption. Yeah. But our mission today is to dive into some core structural design research. Specifically, we're looking at a pretty comprehensive analysis by Dr. Jonathan Westover.

[00:02:16] Which is a fantastic piece of research, by the way. It is. And this analysis completely flips the script on how we view this. Those terrible onboarding experiences, the clunky processes, you know, the disconnected systems where you have to enter your home address into like five different databases. Oh, yeah. The endless form filling. Right. Well, those aren't just isolated screw ups. No, they really aren't. And they aren't training gaps either. Yeah. We always want to blame the individual who forgot to click the right button, you know.

[00:02:44] Obviously, yeah. It's easy to blame the person. But this research argues that these failures are actually symptoms of a profound structural breakdown. It's about how modern organizations are fundamentally architected. So it's baked in. Exactly. The system is actually doing exactly what it was built to do, which is, um, operate in completely disconnected silos. Which brings us to the big question we're going to explore today.

[00:03:08] Yeah. Because over the last few years, there has been this like massive industry-wide trend of companies renaming their human resources departments. Right. The big rebrand to people operations. Yeah. People operations. You see it on every single corporate career page now. It sounds modern, right? Very tech forward. Yeah. Tech forward friendly.

[00:03:28] But we really want to know, is this trendy corporate title actually fixing this structural failure? Or is it just a fresh coat of paint on the exact same broken machinery? And that distinction is critical. Because as the research points out, structural change cannot be faked. You can't just slap a label on it. Right. If you just change the name on the door from HR to people operations, but you keep the underlying plumbing exactly the same, you're not going to get different results.

[00:03:56] You're just going to get the same chaotic onboarding experience. Exactly. Except now the confusing email comes from a, you know, a people experience specialist instead of an HR coordinator. That is so true. So let's start by figuring out why these universal pain points exist in the first place. We have to look at the foundations. Right. The research draws a really sharp contrast between vertical silos and horizontal integration.

[00:04:20] To understand the chaos you experience on your first day, we have to look at how traditional HR has been built for decades. Which is mostly built on something called the three pillar model. The three pillar model. So let's break that down for everyone listening. Yeah. It's practically industry standard. I mean, if you work in a company with more than, say, a few hundred employees, you are almost certainly living inside this structure right now.

[00:04:44] Whether you realize it or not. Exactly. And understanding what those three pillars are is really the key to understanding why everything in your work day feels so incredibly full of friction. OK, so let's walk through them. The first pillar is the centers of excellence or COEs. Right. If you hear that term, you know, think of the deep domain experts. These are your compensation analysts who spend their entire days building really complex salary bands. Or your learning and development specialists.

[00:05:11] Yeah. The ones who design corporate training programs. They are basically the architects of policy. But importantly, and this is key, they are completely insulated from the daily execution of those policies. So they're kind of in an ivory tower? Pretty much. They design the blueprint in a vacuum, optimizing for their specific narrow domain. Right. OK. Then you have the second pillar, which is the business partners. These are the folks who sit embedded with the actual business leaders.

[00:05:41] They're supposed to be advising on high level strategy, coaching executives, that sort of thing. Yeah. Like helping a specific department figure out its future organizational design. Exactly. And then finally, you have the third pillar, which is shared services. Ah, shared services. Yeah. This is the engine room of the organization. They're the ones who actually execute the transactions. So if you've ever, like, submitted an IT ticket into a black hole and waited three weeks for a password reset, you are stuck in the shared services pillar.

[00:06:09] Unfortunately, yes. They process the payroll. They handle benefits enrollment. They answer routine employee tickets. OK. So you have policy design in pillar one, strategic advising in pillar two, and transaction execution in pillar three. Right. And on paper, you know, in a business textbook, that sounds incredibly logical. Everyone has a very clear, highly specialized role. That sounds neat and tidy. But structurally, this creates a phenomenon called vertical specialization.

[00:06:39] Everyone becomes a world class expert in their specific vertical silo. But no one is talking to each other. Exactly. Absolutely no one is responsible for the connective tissue between them. You build massive, deep capability in a specific discipline, but you completely lack any horizontal integration. And horizontal integration is what actually connects them, right? Yeah. It has the invisible mechanism that connects across those domains. It is what ensures that when a candidate clicks accept on an offer letter in the applicant tracking system,

[00:07:08] that data flows perfectly into the onboarding system. Without someone having to retype it. Right. Which then automatically triggers IT to provision a laptop, alerts payroll to set up direct deposit, and, you know, notifies the manager with a simple checklist of what to do on Monday. I have to go back to an analogy here because it sounds like building a house where you have hired the absolute world's best plumbers and the world's best electricians. OK. Yeah. But you decided to save money by not hiring a general contractor.

[00:07:37] So the plumber puts a massive water pipe right through the wall where the electrician desperately needs to run the main power wire. Because they aren't talking to each other. Right. They are just optimizing their own vertical job. And suddenly you, the employee, are stuck living in a house where the lights flicker every single time you flush the toilet. That is a perfect analogy. Yeah. And the danger of that setup is what happens when something actually breaks. When the lights flicker, you know, who do you call? The plumber insists it's an electrical issue and tells you to submit a ticket.

[00:08:07] And the electrician says the pipe is blocking their conduit and it's a plumbing policy issue. That is exactly what happens in a fragmented corporate system. The employee is just left holding the bag, bouncing between departments. Constantly. Which, ironically, is supposed to be the entire point of genuine people operations. Genuine people operations is meant to be that general contractor. Where's the theory?

[00:08:30] It is supposed to be the horizontal integration that orchestrates all the processes, the technology, and the data across those rigid vertical boundaries. Right. But, and here's what I don't get. If this is the magic bullet, everyone must be doing it right. Because, like I said, that title is everywhere now. Well, they certainly use the title. But when you look at the 2023 survey data on organizational structure from the research, the reality is actually pretty bleak. Oh, really? What does the data say?

[00:09:01] Almost half of the organizations surveyed about 47% claim to have a dedicated people operations function. Okay. Almost half. That sounds pretty good. It does. Until you realize that the vast majority of them are totally faking it. The data shows that 31% of these companies take this new people operations team and just subordinate it under the shared services pillar. Oh, so it's just the old engine room with a new name. Exactly.

[00:09:24] And another 23% hide it deep inside a different vertical pillar, like putting it entirely under talent acquisition. Wait, wait. Let me do the math. So that means only 28% actually position it correctly as a peer to the other pillars. Yeah. Roughly three quarters of the companies claiming to do people operations are literally just slapping a new label on their existing silos. And the structural placement is everything.

[00:09:48] When you subordinate people operations under shared services or tuck it away inside a vertical pillar, it completely lacks what the research calls enterprise reach. Enterprise reach, meaning what? They can't force other departments to change. Exactly. It simply does not have the organizational authority to challenge how work flows across the whole company. Because they are too low on the org chart to push back. Like, they can't go to the ultra-powerful head of compensation and say,

[00:10:15] Hey, your new bonus approval process requires a manual spreadsheet upload and it's actively breaking our automated payroll system. Right. We need you to redesign it. They can't say that. They have zero leverage. Zero. So instead of acting as the general contractor who can force the plumber to move the pipe, they just inherit the messy, disconnected work that the other teams reject. They become the complaint department. Exactly.

[00:10:39] They become the complaint department for the flickering lights, forced to manually fix errors caused by bad upstream design. So they're just doing transactional excellence, which is what shared services focuses on anyway. Right. Which is fundamentally different from system integration, which is what people operations should do. So when you deny them peer level authority, the function artist scope just compresses back into basic administrative support. Okay. Let's ground this in the real world for a second.

[00:11:07] Because if I'm an executive listening to this, I might be thinking, okay, sure, our HR structure is a little clunky. Maybe it takes a few extra days to get a laptop. It's just administrative friction. You know, it's a minor cost of doing business. Right. They write it off as an annoyance. But this research actually quantifies this chaos. And the hidden costs of this fragmentation are staggering. Let's talk about the capacity drain first because this totally blew my mind. Yeah. The numbers here should honestly keep any chief financial officer awake at night.

[00:11:34] The research indicates that integration gaps, and by that we mean, you know, handoff failures, manual workarounds, pure coordination overhead, eat up 15% to 25% of an HR function's total capacity. Up to 25%. Let's do the math on that for you listening right now. If you are at a moderately sized company with, say, 10,000 employees, you might have roughly 100 people working in HR and administration. That's a fair estimate.

[00:12:00] That means you have up to 25 full-time employees earning full salaries and full benefits whose entire 40-hour workweek consists of absolutely nothing but compensating for broken structures. Yep. They aren't adding value. They're just human duct tape. Human duct tape. I love that term, but it's so depressing. It is. And the tragic part of being human duct tape is the sheer misery of the daily work.

[00:12:22] Imagine your entire job is downloading a CSV file from the recruiting software, manually formatting the date columns at Excel so they don't break, and then uploading that exact same file into the payroll software. Just because the company refused to buy systems that talk to each other. Exactly. All day, every day. And when one of those 25 people inevitably burns out because the work is so soul-crushing and quits, the institutional knowledge of how to format that one specific Excel column leaves with them. Right.

[00:12:52] And suddenly payroll breaks for 300 new hires. Which creates a massive ripple effect, right? And that brings us to how this destroys the second pillar we talked about, the business partners. The research calls this the business partner trap. Yes. Because the business partners are supposed to be out there designing the future. They are highly paid strategic advisors looking at workforce planning or figuring out how to transition the sales team into a new market. That's the theory. But what does the data show they're actually doing?

[00:13:21] The research tracking their time allocation shows they waste 35% to 50% of their time on administrative coordination and case escalation. Almost half their time just putting out administrative fires. Because when the underlying system breaks down, when the onboarding fails, or a manager realizes the compensation data for their whole team is suddenly wrong, the manager doesn't know who to call in the labyrinth of shared services. Right. They don't know the difference between a tier one support ticket and a tier two escalation.

[00:13:50] So they just call their dedicated business partner and say, I don't care how you do it, just fix this. The business partner inherits responsibility for problems the structure itself cannot solve. So you have your most highly skilled, highly paid strategic thinkers doing basic administrative triage. Yep. It's like paying a top-tier corporate lawyer $800 an hour to unclog your office toilet just because you couldn't be bothered to hire a maintenance team. That is a spectacular waste of resources.

[00:14:18] And, you know, it gets even more dangerous when we look at the data disaster this causes. We always hear these buzzwords about big data and people analytics. Oh, constantly. Every HR tech vendor pitches it. Right. But without horizontal governance, without that general contractor ensuring the data flows cleanly from pipe to wire, the employee record error rates sit between 12% and 18%. Which is terrifying. An 18% error rate is a terrifying number for any large organization.

[00:14:46] It means nearly one in five employee records is fundamentally flawed. And we aren't just talking about a misspelled middle name, are we? No, not at all. We were talking about incorrect hire dates, wrong task designations, or completely outdated salary bans. This creates immediate, massive compliance and legal risks. And it just completely ruins any attempt at strategic analytics.

[00:15:09] If your foundational data is wrong, every single dashboard, every fancy predictive report, every strategic presentation given to the board of directors based on that data. It's basically a hallucination. Yeah. The errors compound. Incorrect data in the applicant system propagates to payroll, which then propagates to the benefits provider, which eventually leads to an employee finding out their health insurance was quietly canceled because of a system glitch. And that brings us to the human cost of this, specifically for the managers.

[00:15:37] The research connects this directly to your daily life if you lead a team. Yeah, let's talk about the managers. Line managers in these fragmented, vertically siloed organizations are wasting between four and six hours a week just navigating HR complexity. That is more than half a workday every single week stolen from your actual job. Stolen. They are reconciling inconsistent information. They're fighting with portals and escalating exceptions. It's exhausting.

[00:16:05] And the psychological impact of that administrative burden has to be profound. It is. Manager frustration often manifests as sheer avoidance. The research points out that managers will literally avoid having necessary performance conversations, or they will fail to document serious behavioral issues on their team simply because they do not want to deal with the HR labyrinth required to process the paperwork. Oh, wow. So they just let bad behavior slide because the forms are too hard to fill out. Exactly. Or they will work around the formal processes entirely.

[00:16:35] They start keeping shadow spreadsheets on their own computers, which, by the way, exposes the company to massive legal liability. Okay, wait, hold on. I'm listening to this, and I'm thinking about the millions of dollars companies spend on tech. We live in a golden age of workplace technology. We have AI. We have massive cloud-based HR systems that cost absolute fortunes to implement. We do. If the tech is so powerful these days, shouldn't the software just fix the data errors?

[00:17:03] Shouldn't a really good software platform automatically connect those clumsy handoffs and solve the structural problem for us? That is the exact trap almost every executive team falls into. They think software is a silver bullet. And the research addresses this head on. Technology amplifies structural problems. It does not solve them. Oh, it amplifies them. Yes. If you take a terrible, fragmented, disconnected process, and you put it into a shiny new, multi-million dollar cloud software, you don't get a fixed process.

[00:17:31] You just get a terrible, fragmented process happening at the speed of light. Ah, because the software is just a mirror of the organization. If the underlying structure is built in vertical silos, the technology will be implemented in vertical silos. Precisely. The learning team will buy the software they like, the recruiting team will buy the software they like, and they still won't talk to each other. And the consequence of that tech fragmentation is just a complete erosion of employee trust. It is.

[00:17:57] There is a quote referenced in the research from a 2013 Sullivan study regarding knowledge workers that perfectly captures this dynamic. What's the quote? A highly skilled technology professional was interviewed about their workplace experience, and 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? Oof. That hits incredibly hard. Because it's so true.

[00:18:23] It's devastating because it highlights that operational failures are not just administrative annoyances. They aren't just paper cuts. They deeply damage the psychological contract between the employee and the organization. Right. If a company looks administratively incompetent on day one, if they can't figure out how to give you a laptop, highly mobile, talented knowledge workers will instantly start updating their resumes.

[00:18:47] They will assume that if the simple things are broken, the complex things like fair pay and career advancement are completely rigged. Operational failure directly triggers turnover. Okay. So we've established that these vertical silos are bleeding capacity. They're ruining data and driving away top talent. The obvious question is, why don't companies just force these departments to talk to each other? Right. What's physically stopping them? Exactly.

[00:19:13] Let's pivot to the solution because the research gives us a blueprint for how to structurally mandate this horizontal integration. And it starts by looking at a major retail case study. Yes. To do this right, organizational design theory dictates that an effective horizontal function needs three very specific elements. You can't just mandate teamwork. You have to build structural authority. So what's the first element? First, the new people operations function needs boundary spanning authority.

[00:19:41] This means they have the explicit power to convene stakeholders from completely different departments and forcefully challenge their existing workflows. They can bring them into a room and say, we are fixing this. Exactly. Second is architectural ownership. They have to own the connective infrastructure. Meaning the technology systems and the data architecture. Right. The tech that enables work to flow across those teams. The vertical teams don't get to buy their own tech anymore. Oh, that's huge. Okay. And the third. The third element is governance mechanisms.

[00:20:11] This basically means having a formalized institutional way to resolve conflicts. Because there will be conflicts. Oh, there will absolutely be conflicts. Yeah. When the horizontal need for integration inevitably clashes with a vertical team's desire to just do things their own way because it's easier for them, you need a mechanism to break the tie in favor of the enterprise. And the case study of Tesco illustrates this brilliantly. Tesco is a massive, highly complex retail operation in the UK, right? Yeah.

[00:20:41] They deal with hundreds of thousands of employees across multiple brands in geographic markets. They realized the traditional three-pillar model was collapsing under its own weight. So they shifted to a four-pillar model. They kept the centers of excellence. They kept the business partners. And they kept shared services. But they introduced a brand new fourth pillar they called people platforms. People platforms, which was their version of true, structurally sound people operations.

[00:21:10] And the crucial detail that made it work is that people platforms was designed from day one as a true, undisputed peer to the other pillars. It wasn't tucked underneath shared services. So the head of people platforms sat at the same exact executive table as the head of compensation. Yes. They had explicit accountability for system integration and the real authority to redesign end-to-end processes across the entire employee lifecycle. And they backed this up with real teeth-bearing governance. They did.

[00:21:38] They created a people leadership team where the head of people platforms had an equal voice. But more importantly, they instituted quarterly big room planning sessions. Big room planning. I love that. Imagine forcing the heads of every single HR silo into a room for two days. They couldn't just operate in a vacuum anymore. Exactly. The structure forced them to align their priorities, identify dependencies, and publicly figure out how their systems connected before they were allowed to launch a new initiative.

[00:22:07] By forcing that cross-pillar alignment, the results they achieved were just staggering. The research notes Tesco saw a 30% reduction in process cycle times for complex, multi-step employee journeys. A 30% reduction is massive at that scale. And they saw a 40% decrease in HR service desk volume. Wait, a 40% drop in people calling the help desk? Yes.

[00:22:30] Because when the underlying processes are actually connected and logical, employees don't need to call a human being to ask how to submit a medical leave form. It just works. It just works. Yeah. Self-service capabilities actually started functioning as intended. But here is where we usually hear some pushback from leadership. Yeah. I know exactly what you're going to say. I mean, I'm thinking the same thing. If we elevate this people platforms team to the C-suite, aren't we just adding another boss?

[00:22:54] It sounds like we're trying to cure bureaucracy by adding a fourth pillar of management, which is literally just more bureaucracy. It's a completely fair initial reaction. But it fundamentally misunderstands where bureaucracy actually comes from. Okay. Unpack that for me. What the Tesco example proves is that horizontal integration actively removes bureaucracy for the end user. The end user being the employee and the manager. Right.

[00:23:21] When you don't have a peer function like people platforms, each vertical center of excellence builds its own bureaucratic labyrinth. To protect themselves. Exactly. The compensation team builds a bonus approval process that optimizes perfectly for their own data entry needs, completely ignoring the fact that it requires a manager to fill out a 12-page form. So the silos create red tape because they don't care about the user experience. Precisely. When you introduce a horizontal peer with the explicit authority to redesign workflows, they act as an advocate for the end user.

[00:23:50] Ah. So they force those deep domain experts to compromise on enterprise needs. Yes. They step in and say, no, you cannot require 12-page form. We are capping it at three fields, and it will be automated. They act as an editor, cutting out the red tape that the vertical silos try to create. That makes perfect sense. They are the defender of the end-to-end user experience.

[00:24:14] And since Tesco proved that this horizontal mandate actually works, we need to explore how that mandate is executed on the ground. Which brings us back to the tech. Right. According to the research, the absolute foundation of horizontal integration is owning the technology. Because you can't fix the process if you don't own the pipes. Technology and data are the ultimate connective tissue of any modern organization. The research is very clear on this point. People operations must own the technology architecture and data governance.

[00:24:43] You can't just leave it to corporate IT. You cannot leave this to corporate IT, because corporate IT generally doesn't understand the complex human nuance of HR processes. That's true. They just see servers and licenses. Right. And you certainly can't leave it to individual HR silos, because that just creates that fragmented mess of disconnected apps we talked about earlier. The text highlights a really fascinating case study from NatWest Group, a major banking organization. Oh, the NatWest example is brilliant. Yeah.

[00:25:12] They realized this, and they made the bold decision to embed digital technology capability directly inside their people operations function. Which is such a smart move. They didn't just submit a request to the corporate IT department and hope for the best. No. They literally hired enterprise tech architects and software engineers into the HR organization. And that structural positioning changes everything.

[00:25:35] By having deep technical capability living inside people operations, that team led the enterprise platform selection. They had the expertise in-house. Right. They ensured that any vendor solution chosen by a silo had to meet incredibly strict integration requirements. They didn't just buy a tool because the recruiting team thought the user interface was pretty. They bought a tool because its data architecture allowed it to flow perfectly into the existing payroll and performance systems. Exactly.

[00:26:03] They enforced strict data governance protocols, defining exactly what a piece of data meant, how it was validated, and who legally owned the master record. And again, when you look at the results, they are undeniable. NatWest saw 60% faster tech implementation timelines. Getting a new enterprise system live 60% faster is massive. And they saw a 45% improvement in data accuracy.

[00:26:29] Plus, they gained the ability to systematically kill off legacy systems, which, if you've ever worked in a big corporation, you know is almost impossible. Retiring legacy systems is a nightmare when technology ownership is scattered. Every vertical team wants to hold on to the old, clunky tool they're used to simply because they don't want to learn a new one. Right. Change is hard. But when People Operations owns the architecture horizontally, they have the authority to pull the plug. They can enforce sunsetting old platforms for the good of the whole system. It makes me think of an analogy.

[00:26:59] If you let every vertical team buy their own software, it's like a family going on a long road trip where every single person brings a completely different, incompatible phone charger. Oh, I've been on that road trip. Right. The teenager in the back has a lightning cable. The dad driving has some weird proprietary watch charger. Someone else has a micro USB. It's chaos in the car. Everyone is fighting over the cigarette lighter. And nobody's phone is actually charged. That is the perfect way to describe shadow IT.

[00:27:28] People Operations is the parent who turns around and says, Look at me. We are all using USB-C. End of discussion. I'm throwing all these other cables out the window. And that parent is performing a vital service for the family's sanity. That is exactly what architectural authority over tool selection looks like in practice. It prevents what the industry calls shadow IT proliferation. Where departments just quietly buy their own software subscriptions on a corporate credit card. Yes. And create massive hidden data silos.

[00:27:58] We talked earlier about that terrifying 12% to 18% error rate in employee data. The research points out that when horizontal data stewardship is firmly established. When you have that parent enforcing the USB-C rule for data. Right. Those error rates plummet down to just 3% to 5%. That is the crucial difference between data you can barely trust to run basic payroll and data you can actually use to predict workforce trends and make multi-million dollar strategic business decisions.

[00:28:26] But owning the technology is only half the battle. Technology is just the tool. The next critical piece of the puzzle is how you use that tool to fundamentally engineer processes. Right. Which brings us to the necessary evolution from processing transactions to engineering processes. There is a massive psychological mindset shift required here. There really is. The old shared services mindset was exclusively about transaction efficiency. They would ask, how fast can we process this form?

[00:28:52] Or how do we reduce the unit cost of handling a password reset ticket by 14 cents? Right. Bean counting. But the mature people operations mindset is entirely different. It's about process innovation. It's about eliminating the waste entirely. It is the difference between asking, how can we efficiently process these 100 onboarding forms in an hour? And asking, why do we require 100 onboarding forms in the first place? Can we structurally eliminate 80 of them?

[00:29:19] To really illustrate this, the research dives into a case study of Peabody, a large UK housing association. Peabody is a great example of this mindset shift. During their operating model transformation, they gave their people operations team explicit accountability for end-to-end performance across the whole employee lifecycle. They weren't just executing steps blindly designed by the centers of excellence anymore. They actually owned the final outcome. And their methodology is a master class in how to engineer a process.

[00:29:48] They didn't just sit in a boardroom and guess at solutions. They utilized systematic process mapping. Which is essential. Let's explain what that actually looks like because it sounds like corporate jargon. Systematic process mapping means they literally put a giant piece of butcher paper on the wall, brought in the payroll person, the IT guy, the hiring manager, and mapped out the 42 distinct clicks and emails it took to approve a basic leave of absence.

[00:30:15] They identified every single handoff, every delay, where an email sat in an inbox for three days, and every point of failure. Exactly. They formed cross-functional improvement teams. They brought together the people who actually did the work across the different silos. And redesigned the workflows collaboratively, forcing them to look at the whole picture. And then they used a pilot-iterate-scale approach. You don't just roll out a massive global change on a Monday morning and hope it works. Right. That never works.

[00:30:43] They piloted the redesigned workflow in a specific unit, say. Just the marketing department gathered immediate feedback, fixed the bugs that popped up, and only then did they scale it across the company. And the outcomes from Peabody's methodology are fantastic. By eliminating the structural waste, they achieved a massive 35% reduction in time to hire. In a highly competitive labor market, getting talent in the door 35% faster is a huge operational advantage. Massive.

[00:31:11] They also saw a 40% drop in employee queries related to leave administration. That means the process became so clear and the self-service tools became so intuitive that employees simply didn't need to ask for help nearly as often. But I want to go back to the tech trap we discussed earlier. Because companies love to just buy fancy new software and digitize their garbage process. Oh yeah. They think, oh, our leave administration is a mess on paper. Let's buy a cloud app. But all they do is make their bad processes happen faster. They just digitize the chaos.

[00:31:39] That is a central theme and a major warning in the research. You cannot automate a broken process and expect a good outcome. Automating a broken process just generates errors at scale. Peabody succeeded specifically because they explicitly simplified the workflows before they wrote a single line of code or bought any software. They cut out the unnecessary approvals and the redundant data entry first. And crucially, they fundamentally changed how they measured success. Explain that. How did the metrics change?

[00:32:09] They started measuring outcomes rather than outputs. Traditional HR measures outputs. How fast did the HR rep process a specific form? Let's say they processed it in five minutes. Great. Okay, but... But an HR rep processing a form in five minutes is completely irrelevant if the employee still doesn't have a functional laptop for two weeks. Right. The output was fast, but the outcome was terrible. Exactly. People... Operations measures the outcome for two weeks to full productivity.

[00:32:37] They measure the reality of the employee's situation, not the speed of the HR administrative task. This shift toward measuring the actual lived outcome for the employee brings us to the next massive conceptual leap in the research, orchestrating the consumer-grade employee experience. Yes. We are shifting from the mechanics of the process, the wires and the pipes, to the psychology of the experience. Employee experience is broadly defined as the accumulated perceptions, emotions, and feelings from all organizational touchpoints over time.

[00:33:07] Right. It's not just one interaction with a recruiter. It's the sum total of everything, from the interview to the onboarding to how easy it is to book a sick day. And the research finding here is fascinating and, honestly, a bit of a reality check for a lot of HR professionals. It really is. The data notes that employees actually care far more about process, consistency, and ease of interaction than they do about heavy personalization or super generous, flashy programs.

[00:33:32] It's a vital insight for leadership. Employees are consumers in their personal lives. We all walk around with supercomputers in our pocket. Sure. We use apps like Amazon, Uber, or Netflix, where everything is seamless, highly intuitive, and almost entirely frictionless. You can order a meal to be delivered to a moving car with two taps of your thumb. And modern workers expect those exact same consumer-grade experiences from their internal workplace services.

[00:33:56] Exactly. When they have to navigate five different clunky, password-protected portals just to request time off, it creates intense psychological frustration. Regardless of how generous the actual time off policy is. Right. You could offer unlimited PTO, but if it takes an hour to figure out how to log it, the employee still hates the experience. The research highlights Adobe as an absolute pioneer in treating employees like consumers. Adobe did incredible work here.

[00:34:26] Adobe literally created a function called Employee Experience and Operations, which is essentially people operations with absolute, crystal clear mandate clarity. They systematically mapped critical employee journeys, like new hire onboarding, internal mobility when you change departments, and manager transitions. And they established metrics that you usually only see in consumer product design, like net promoter scores and customer effort readings.

[00:34:52] By treating the internal employee journey like a consumer product, Adobe's cross-functional teams were able to radically redesign how work happened. Take onboarding, for example. What did they do there? They shifted a massive amount of the heavy administrative paperwork to the pre-hire phase, before day one. Getting it out of the way. Right. They coordinated tightly with IT and facilities to ensure absolute day one readiness. The laptop was there. The badge worked. The software was loaded.

[00:35:19] And they built proactive communication sequences, so the new hire never had to sit there wondering what was happening next. The return on investment Adobe got from this is just incredible. Let's hear the numbers. By redesigning onboarding, they saved managers 50% of their administrative time. Wow. 50%. They boosted new higher confidence scores by 35%. And the most important metric, they accelerated timed productivity by three whole weeks.

[00:35:46] Three weeks. Getting a highly paid knowledge worker fully productive three weeks faster pays for the entire people operations team by itself. It does. And it proves beyond a shadow of a doubt that experience improvements require intense, militant, cross-functional coordination. You cannot accelerate productivity without IT, facilities, and HR all moving together in lockstep.

[00:36:07] And as we've established today, the coordination is structurally impossible without the horizontal authority that a true people operations function provides. So what does this all mean for you listening right now? If you are a manager or just an employee at a large company and your organization is actually doing this right, what does your Monday morning actually feel like compared to the bad old days? If your company has built genuine people operations, your Monday morning feels invisible.

[00:36:37] And I mean that in the best possible way. Invisible because the friction is gone. The friction is completely gone. If you have a new person starting on your team, you don't spend Sunday night dreading the administrative mess you're going to walk into. You know the systems have already talked to each other. Right. The laptop is sitting on the desk. The security badge is printed and waiting at reception. The necessary software licenses are automatically provisioned based on the role. IT, facilities, and HR all moved in concert behind the scenes without you having to send a single pleading email.

[00:37:06] You, as the manager, just get to focus on welcoming a human being to the team and talking about the actual meaningful work. That is the feeling of an orchestrated experience. It sounds like an absolute dream. It is. But the final hurdle the research addresses is how you actually build the team capable of running this dream state, and critically, how you stop the organization from sliding backward into its old siloed habits. Which is the hardest part.

[00:37:34] Let's talk about capability building, and then we have to talk about defending the castle. This is where a lot of well-intentioned transformations fail. Because the capabilities required for true people, operations are fundamentally different from traditional HR skills. Right. Traditional shared services requires operational discipline, quality control, managing service level agreements. It's very focused on transactional speed. But people operations requires deep systems thinking.

[00:38:01] It requires advanced skills in change management, complex process mapping, and enterprise technology architecture. The research points to Microsoft as a prime example of getting this talent mix right. Microsoft's approach was brilliant. When Microsoft was building their people analytics function, which is a heavily data-driven, horizontal wing of people operations, they didn't just promote traditional HR folks into those roles. They didn't just take a great payroll clerk and ask them to be an analyst.

[00:38:29] Right. They went out and hired actual data scientists, research methodologists, organizational psychologists, and tech architects. They built a multidisciplinary team specifically designed to tackle complex integration challenges. You cannot just take someone who has spent 10 years efficiently processing health insurance forms and expect them to suddenly know how to architect an enterprise-wide, API-driven data integration strategy. It is a completely different professional skill set.

[00:38:56] Organizations have to define these capability requirements explicitly and either invest heavily in upskilling their current staff or acquire external talent from completely different disciplines. But even if you hire the perfect team of data scientists and systems thinkers, the research warns about a very real threat called regression. Regression is always lurking. The research notes that horizontal power naturally erodes over time.

[00:39:21] The vertical teams, the powerful centers of excellence will always try to claw back control over their budgets, their pet software projects, and their own rigid processes. It is human nature and it is organizational gravity. Vertical silos want to be independent. They don't like being told what to do by a horizontal peer. Preventing this regression requires ironclad governance mechanisms that survive changes in leadership. It makes me think of an invasive plant species. Oh, like bamboo or something?

[00:39:51] Yeah, exactly. Getting your garden in shape and pulling the weeds is one thing. But if you don't uproot the legacy governance structures entirely, if you leave even a little bit of vertical purchasing power in the soil, those silos will vine back over the entire system, the second executive leadership stops paying attention. That's so true. If you let the vertical teams start quietly buying their own software again, the chaos instantly returns. And that is why the research lays out specific governance mechanisms needed to survive.

[00:40:20] First, you need explicit work placement criteria. What does that look like? When a new project pops up, there must be a defined, unbending rulebook for who owns it. Does this project require deep domain expertise, like designing a new executive equity plan? Then it goes to the center of excellence. And if it's horizontal. Does it require horizontal integration across multiple systems, like rolling out a new performance management software?

[00:40:47] Then people operations owns it, no exceptions. This prevents the vertical teams from just grabbing the fun strategic work and dumping the operational mess back onto people operations. Exactly. Second, you need defined escalation paths. Right. When a conflict arises, say, the learning and development team wants to buy a flashy new training platform that people operations says violates the company's data architecture standards, who breaks the tie? You have to have a clear, fast path to senior leadership to resolve that quickly,

[00:41:16] rather than letting it turn into a territorial cold war that lasts for six months. And third, you have to systematically measure integration performance. You have to constantly show the data proving that this horizontal model is working. You have to continually present dashboards showing the faster cycle times, the lower error rates, the massive time savings for managers. You have to continuously prove the financial and operational value of the integration to justify keeping the authority.

[00:41:43] And the research also gives a really practical piece of advice for building the right culture to support this, rotating high potential talent through people operations. Putting rising stars from other HR functions, say, a brilliant young compensation analyst into people operations for a 12 to 18 month assignment is brilliant. It builds what the research calls bridge builders. They learn systems thinking. They personally experience the pain of broken processes and manual workarounds.

[00:42:11] And when the rotation is over and they go back to their vertical roles, they are much more likely to partner effectively rather than fight for turf. They realize that positional authority isn't enough. You need genuine partnership across the organization to make anything work. This has been an incredible journey into the hidden mechanics of how our workplaces actually function. We started by looking at the universal pain of clunky, chaotic workplace processes, the hammer and the loose wires at the hotel. Right.

[00:42:39] And we discovered that people operations isn't just a trendy new name for the HR help desk or the same old shared services department. When it is done right, it is a massive, fundamental structural revolution. It is the necessary shift from vertical silos to horizontal orchestration. It's a horizontal powerhouse that acts as the general contractor. It owns the technology architecture. It ruthlessly smooths out and simplifies the processes before digitizing them.

[00:43:08] And it orchestrates a seamless consumer grade experience for every single employee. And by doing that, it ultimately saves the company massive amounts of time, money and highly valuable talent. And importantly, it prevents the massive capacity drain and data disasters that completely plague traditional corporate models. So as we wrap up this deep dive, we always like to leave you with a final thought to mull over. Something that builds on the source material, but pushes it a bit further into your own daily life.

[00:43:36] The research highlights a very profound principle. Structural change cannot be faked because a system will always deliver exactly what it is designed to deliver. Right. If it's designed to be fragmented, you will get chaos. So I encourage you to look at the biggest recurring frustration in your own work right now. Think about that one process that always breaks, that one handoff that always fails, the thing that makes you dread Monday mornings. Are you blaming the people involved?

[00:44:04] Are you assuming they are just incompetent or lazy? When perhaps you should actually be looking at the horizontal architecture of the system they are trapped in. They might just be doing exactly what their vertical silo demands of them. The real question is, how could you step in, span those boundaries and become the integrator that your team desperately needs to fix the underlying structure? That is a powerful lens to view your workplace through. Stop blaming the plumber and the electrician and realize you just need a general contractor.

[00:44:32] Thank you for joining us on this deep dive. Our goal is always to extract the ultimate nuggets of insight from complex material. And exploring the mechanics of organizational design certainly delivered that today. We'll see you next time. I'll see you next time. Bye.