People Operations

Where the term came from

The label spread through US technology companies in the late 2000s and 2010s, which wanted an HR function that behaved more like an operations or product team: measuring outcomes, testing changes and designing processes around the employee's point of view. Since then it has been adopted well beyond tech, sometimes as a real change in approach and sometimes as a new sign on the same office door.

It is worth separating the term from HR operations, which in most companies means the transactional and systems layer of HR. People operations usually means the whole function.

What a people ops team does

Scope is largely the same as traditional human resource management:

• Talent acquisition and onboarding.
• Compensation, benefits and payroll coordination.
• Performance management and development.
• Employee relations and policy.
• HR systems, data and analytics.
• Compliance with employment law.
• Culture, engagement and internal communication.

What tends to differ is how the work is run. People ops teams usually map the employee experience as a journey, measure it with surveys and data, and change processes based on what the data shows. They also tend to own more of the tooling decisions themselves rather than waiting for IT.

People operations vs HR

In practice the differences show up in four places:

• Orientation. Traditional HR is often organized around risk and policy. People ops starts from the employee and manager experience, with compliance built into the design.
• Data. People ops teams lean heavily on people analytics: attrition by manager, time to productivity, engagement scores by team.
• Process design. Changes are piloted with one group, measured and then rolled out, much like a product release.
• Self-service. Routine requests go through portals and automation so the team spends time on advice and programs.

None of this is unique to companies that use the title. Plenty of HR departments work this way under the old name, and some "people teams" run on spreadsheets and email. Judge the function by how it works, not by its name.

Typical structure by company size

At a 60-person startup, people ops is often one person covering recruiting coordination, onboarding, benefits enrollment, payroll inputs and policy. Between roughly 200 and 1,000 employees, the team splits into recruiting, people partners (similar to HRBPs), people operations or HRIS, and total rewards. Above that, large organizations add centers of excellence, shared services for transactions and dedicated people analytics.

High-volume employers face a particular test. A people ops model built for 300 salaried employees at one office often struggles with 3,000 hourly workers across 40 sites who do not have company laptops. Self-service has to work on a phone, policies have to make sense to frontline supervisors and data has to come from scheduling and time systems as well as the HRIS.

Common mistakes

• Renaming without redesigning. Changing "HR" to "People" with no change in process tends to make employees more cynical, not less.
• Underweighting compliance. An experience-first mindset still has to get I-9s done on time, pay overtime correctly under the FLSA and handle leave under FMLA and state laws. These rules vary by state, and they do not care what the team is called.
• Measuring everything, acting on little. Quarterly engagement data without owners and follow-up actions wastes employees' time.
• Designing for office workers only. Frontline and shift employees need different channels and timing.

Hiring for people ops roles

People ops job titles vary widely: people partner, people operations specialist, people programs manager, head of people. When hiring, test for the combination the title implies: comfort with data and systems, process design, and the judgment to handle sensitive employee issues. Our people operations interview questions cover those areas with scenarios and scoring guidance. For roles that are mostly employee relations and site support, a classic HR generalist profile is often a better fit than a data-heavy people ops background.