People Operations

Human resources (HR) work was long divided up by the paperwork it produced: contracts, payroll, attendance, insurance filings, all owned by one person. That tells you whether each item cleared its deadline, never what the experience was like for the person filling in the form.

Once a company passes thirty people, the gap shows up as scenes. A new engineer arrives on day one without a laptop, gets server access three days later, and learns over lunch on day four where the team's documents live. Nobody was late with their own piece. What was missing was anyone seeing those three days as one stretch that a single person walked through.

Review season has the same shape: a template file and a deadline arrive by email, while why the questions are worded that way and where the answers go is written nowhere.

People operations exists to own that gap. It treats employment policy not as a queue of transactions but as journeys an employee moves through. For each one, the job is to find where people got stuck and fix it before the next group walks the same path. The word operations is literal: these systems are run and revised, not built once and filed away.

A day splits into running the systems that already exist and designing the one being reworked — roughly six tenths, three tenths, and the rest to questions people bring over. The running half is four recurring jobs.

1. Joiners and leavers. At forty-five people a typical week brings one or two hires and one departure. Joining means hardware, accounts, a first-week schedule and a buddy lined up before arrival; leaving means a handover list and a full sweep of access revocation.
2. Running the review cycle. The day self-assessments open, the manager deadline, the meeting where reviewers align standards, the day results land — laid out as dates and announced four weeks ahead.
3. Answering policy questions. Can vacation be split into half days? Does a remote day allow an external meeting? When the same question arrives three times, the answer becomes an edit to the written policy.
4. Watching the numbers. Headcount in and out, people per department, trailing twelve-month turnover, compiled the same way every month. Eleven departures from a forty-five-person company is 25 percent turnover, but if five came from one team, that team is what to look at.

The design half takes one system at a time. If this quarter's target is employee onboarding, ask the six people who joined in the last three months what blocked them in their first two weeks, pick the three answers that repeat, rewrite the checklist, and ask again a month later to see whether time to first contribution shortened. An engineer who ships their first change on day three and one who takes three weeks usually differ in preparation, not skill.

One at a time is deliberate. Change compensation, work arrangements and performance management in the same quarter and there is no telling later which change produced which effect.

The people seen most often are the managers who run teams. They execute the review cycle, and they are where the first news arrives about how a policy behaves in practice. A common rhythm is fifteen minutes with each team lead every other week, covering open roles and early signs that someone is drifting.

Recruiting is next. Where there is a dedicated recruiter, sourcing and interviews sit with them, while people operations sets the reference points hiring works against: job levels, which grade roles by scope and responsibility, and the salary range fixed for each level. Without those ranges, two people at the same level end up $9,000 apart within six months.

With the executive team the subject is numbers attached to people — how many roles to fund next year, what total payroll looks like, how the org should be split. The chief executive decides and people operations builds the case underneath. Finance gets pulled in on salary and bonus totals, legal on contract language.

Past roughly 150 people, one seat stops being enough. An HR business partner (HRBP) splits off to sit with a single division, and a chief human resources officer (CHRO) appears above the function. People operations then narrows toward what applies company-wide. Employees come by directly too, though this is not a counseling desk: handling one situation as a private exception is how a policy quietly stops existing.

"Let's not handle this as a one-off exception — I'd rather change the policy."

Read as a signal the same request is coming again, so the rule itself gets rewritten.

"I moved account provisioning to three days before the start date. That's where day one was breaking."

The order of steps changed based on what people who went through it said.

"That level is already at the top of its range, so raising it means revisiting the level."

Pay is settled inside an agreed structure rather than by individual judgment.

Pagedeck created its first people operations seat at forty-five employees, and the first quarter went to the first week on the job. Six recent joiners were asked what had blocked them, Theo among them, and five gave the same answer: for two days they had no accounts, so they couldn't open the documents they were told to read. Provisioning moved to three days before the start date, the all-hands introduction came off the day-one schedule, and reading time for team documents went in. The next quarter's four arrivals picked up their first task on the afternoon of day one.

The second quarter went to a problem Grace brought over: two people at the same level were far apart on pay. A range was drawn for each level, the seven people outside their range were listed, and an order for correcting them was agreed. Grace asked what it would cost; the answer was three options rather than one number.

The most common reading is that this is the perks job. The visible output is snacks, offsites and vacation announcements, so that is what the role looks like from outside. Most of the hours actually go into review cycles, salary ranges and hiring bars, none of which anyone sees. Left uncorrected, this reading makes the seat the first thing cut when budgets tighten, and a year later nobody is left to draw a range or hold a rating standard.

The second reading is that the role takes the employee's side. The listening happens here, so it feels that way. What it does is apply one standard to both sides: turning down a remote-work exception and reversing a rating a manager couldn't justify are the same person's job. Left uncorrected, the employee reads a refusal as betrayal and the manager reads a reversal as bias, and neither brings anything to this desk again.