HR Is Not People Operations

Most companies treat HR and People Operations as interchangeable labels for the same department, but they are not. The confusion is understandable because both functions deal with people, both sit within the same organizational chart, and in most startups, both are handled by the same person. Conflating the two is not a structural convenience, it is a structural problem, and the evidence increasingly supports that distinction.

The question is not whether HR matters, because it does. Compliance, labor law, payroll accuracy, and risk management are all critical. The question is whether the same department that enforces policies and manages legal exposure can also credibly own the employee experience, drive culture, and act as a genuine advocate for the people inside the organization. That is a dual mandate with a built-in tension, and it rarely resolves in the employee's favor.

What Each Function Does

HR, in its original and still most essential form, is a compliance and administrative function. It manages the legal relationship between employer and employee, including contracts, benefits, disciplinary processes, termination procedures, compliance with labor laws, and regulatory filings. These activities are not optional, they are the operational baseline that keeps an organization legally sound and financially stable. HR builds the framework within which work happens.

People Operations is a different discipline. The term itself was popularized by Laszlo Bock at Google, who renamed the company’s HR department in 2006 after recognizing that a strictly administrative function lacked the mandate to solve people problems at their root. In his book Work Rules!, Bock described the shift as moving from a department that was “administrative and bureaucratic” to one with the genuine ability to influence organizational outcomes. People Operations focuses on the employee experience, engagement, development, and retention, approaching the workforce the way product teams approach users: iteratively, data-driven, and with a bias toward improvement.

The distinction is not merely semantic. A compliance function asks: “Are we protected?” A People Operations function asks: “Are our people thriving, and does that connect to how the business performs?” These are different questions, and they require different capabilities, metrics, and organizational loyalties to be answered well.

The Structural Conflict

The problem with housing both functions under one department is not a matter of workload, it is a matter of allegiance. When the same team that disciplines employees also claims to advocate for them, trust erodes. When the function responsible for compliance-driven terminations also runs engagement surveys and culture initiatives, credibility is compromised. Employees know the difference between a department that serves the organization and one that serves them, and they adjust their behavior accordingly.

Ram Charan made this argument explicitly in a 2014 Harvard Business Review article, proposing that HR be split into two separate functions: one focused on administration and compliance, the other on leadership and organizational development. Charan’s core observation was that CEOs wanted strategic partners in their people leaders but were consistently getting administrators, because the administrative mandate crowded out everything else. The article acknowledged that HR’s compliance duties were not going away, but argued that they were structurally incompatible with the strategic and human-centric role organizations increasingly needed.

This is not a fringe position, and it reflects a real and observable tension in how HR departments operate. When compliance and culture share the same org chart node, compliance wins by default. The risk calculus is asymmetrical: a compliance failure has immediate legal and financial consequences; a culture failure is slower, harder to quantify, and rarely traced back to the function responsible.

The Cost of Getting It Wrong

Research shows:

Gallup's large-scale meta-analysis, covering 230 organizations and 82,248 business units across 49 industries, found that employee engagement correlates strongly with nine distinct performance outcomes. Organizations in the top quartile of engagement outperform bottom-quartile peers by 21% in profitability, 20% in sales production, 10% in customer ratings, and show 59% lower turnover in stable-workforce organizations.

These are not marginal differences, but the gap between organizations where the people function is genuinely strategic and those where it remains primarily administrative. If the people function is structurally constrained to compliance and risk management, those outcomes are not accessible, regardless of how talented the HR team is.

A separate line of research found that companies doubling their employee engagement efforts experience a 22% decrease in absenteeism and a 9% increase in productivity. That is a significant return on a deliberate structural investment in the people experience, not simply a byproduct of better HR administration.

Google's own transformation under Bock’s People Operations model offers a real-world proof point. By applying data-driven methods and moving away from pure process compliance, Google’s people operations group achieved 6% annual productivity gains for five consecutive years, while reducing HR cost per employee to 73% of the 2011 baseline, without outsourcing or increasing vendor reliance. The company was also named the top employer in the United States seven times during that same period.

The Antrops Triple Aim

At Antrops, the framework for any people function is built around three simultaneous aims: people thrive, business performs, and the organization grows. These are not sequential priorities; they are concurrent ones, and they require different capabilities to deliver.

HR, properly structured, enables the third aim through the scaffolding it provides: legal protection, operational consistency, and institutional stability. The first two aims, people thriving and business performing through people, require a function that is freed from the compliance mandate and able to operate with full accountability to the employee experience. When both aims report to the same function, the compliance mandate will always pull resources and attention away from the strategic one, because its costs are more visible and its consequences more immediate.

The separation is not about adding headcount or creating unnecessary bureaucracy. The problem is not having two people; it is having one function with two incompatible accountability structures.

How the Separation Works

The structural separation of HR and People Operations is already underway in organizations that have carefully considered the employee experience as a strategic asset. The pattern is consistent: HR owns compliance, labor relations, payroll, and legal risk. People Operations owns engagement, culture, development, retention strategy, and the employee lifecycle from an experience perspective. Both report to leadership, but on different lines and with different success metrics.

Christopher Koeneman, writing on LinkedIn, described this distinction as the difference between a function that polices and a function that develops, arguing that combining them produces a department that does neither well. The structural logic behind that observation is reinforced by the research: when the mandate is split, but the department is not, the administrative function will dominate by default, and the strategic function will be underfunded, under-resourced, and perpetually reactive.

The practical implication for startups and scale-ups is straightforward. If you are serious about the employee experience as a driver of retention and performance, the first step is not hiring a better HR person; it is clarifying which function you need and building the accountability structure to match. A People Operations mandate crammed inside an HR reporting line will eventually become an HR function, because that is where the organizational gravity sits.

The Argument Against Separation

The most common counterargument is resource efficiency: smaller organizations cannot afford two separate departments, and the functions overlap enough to justify combining them. This is a legitimate constraint, not a compelling structural argument. Overlap in execution does not mean overlap in purpose. Finance and accounting share significant tooling and data, but organizations do not typically argue that they should be the same department because they both work with numbers.

Three structural paths make the separation viable regardless of headcount. For organizations with the budget, the answer is two distinct functions: separate hires, separate reporting lines, separate success metrics. For startups and scale-ups navigating tighter resources, the compliance function can be outsourced or automated through PEOs, HRIS platforms, or fractional HR administration, leaving the internal function free to operate with a clean People Ops mandate from the start. A third path is to bring in a fractional People Operations partner who works directly with leadership, with an explicit scope that excludes compliance, giving founders the structural separation and expertise without the cost of a full-time hire.

A second counterargument is that good HR professionals can do both. Some can, and do with difficulty, but designing a structural solution around the best-case individual is not sound organizational design. The question is what the function produces by default, not what an exceptional practitioner can produce under ideal conditions. By default, when compliance and culture share a mandate, compliance wins.

The case for separating HR and People Operations is not ideological; it is structural. Two functions with different accountability structures, different success metrics, and different organizational allegiances cannot be optimized by sharing a department name. The research on engagement and business performance is clear about the stakes, and the practical evidence from organizations that have made the split is clear about the upside.

The question is not whether HR matters, because it does, and it should. The question is whether HR's compliance mandate should constrain the people function's capacity to drive organizational performance through the employee experience. The answer, both structurally and empirically, is no.

Key Sources & Further Reading

Charan, R. (2014, July–August). It’s time to split HR. Harvard Business Review. https://hbr.org/2014/07/its-time-to-split-hr

Gallup, Inc. (2016). Q12 meta-analysis: The relationship between engagement at work and organizational outcomes. Gallup. https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx

Koeneman, C. (2026). It may not be popular, but human resources should be split in two. LinkedIn Pulse. https://www.linkedin.com/pulse/may-popular-human-resources-should-split-two-christopher-koeneman-vzstc/

Sullivan, J. (2020, July 7). Revealing the ‘HR professional of the decade’: Laszlo Bock of Google. Dr. John Sullivan. https://drjohnsullivan.com/articles/revealing-hr-professional-of-the-decade-laszlo-bock-google/

Taggd. (2025, October 16). People operations vs HR: The essential guide for modern leaders. Taggd HR Glossary. https://taggd.in/hr-glossary/people-operations/

TriNet. (2023, December 4). People operations: A guide to the new HR term you should know. TriNet Insights. https://www.trinet.com/insights/people-operations