People Ops, Not Traditional HR
Why I bet on People Operations over gatekeeper HR, and why many great HR professionals are already doing People Ops without the label.
People Ops, not traditional HR
Pull up a chair. This one is personal.
I'm building Mini HostPapa as a documented hosting company, not a side project with a logo. That means org design, values, and how people are treated are not "we'll fix HR when we hire HR." They're part of the product.
I'm for People Operations. Not because I hate HR professionals. Because I've seen what happens when people work is reduced to gatekeeping, mystery rules, and policies nobody reads until something goes wrong.
This post criticizes a model, not a profession. Plenty of HR leaders already run people-first programs, document fairly, and unblock teams. Many of them are doing People Ops already. They just have "HR" on their business card.
Two names, two default questions
When I say traditional HR in this post, I mean the reflex that leads with: "Are we compliant? Did we follow procedure? Who approved this?"
When I say People Ops, I mean the reflex that leads with: "Is this fair, clear, and sustainable? Can this person do good work here? What system failed if they're struggling?"
Both care about legal risk. Only one treats that as the floor, not the whole job.
| Traditional HR bias | People Ops bias | |
|---|---|---|
| Core question | Did we follow the rule? | Does this work for humans and the business? |
| Policies | Protect the company from people | Protect people and the company with clarity |
| Culture | Compliance-first | Autonomy with documented boundaries |
| Where docs live | HR folder, separate from "real work" | Same handbook as engineering and finance |
| Success metric | Zero escalations, zero surprises | Retention, clarity, sustainable pace, honest feedback |
The People Ops label got popular in tech circles (Laszlo Bock's work at Google is often cited). You don't need to worship any single company to see the pattern: treat employment as a system, not a stack of forms.
You might already be People Ops
If you're in HR and you're reading this defensively, fair. Let me flip it.
You might already be People Ops if you:
- Publish policies where employees actually look (handbook, intranet, not a dusty share drive)
- Help managers write clear role criteria before interviews start
- Push back on "hire someone like me" with structured process
- Track retention and burnout signals, not just headcount
- Show up to understand on-call load before lecturing about attendance
- Treat compliance as necessary, not as the entire personality of the function
The gap is often naming and authority, not intent. Bad HR culture is a systems problem. Good HR people stuck inside that system deserve better design too.
Same situation, different reflex
Below are situations I've seen (or lived) in tech and ops teams. Same question. Two ways to respond.
Not caricatures. Default reflexes when the org has not decided which model it wants.
1. "Can I take Friday off? Release is next week."
| Traditional HR reflex | People Ops reflex |
|---|---|
| Check policy. Count remaining days. Quote the handbook paragraph. Approval depends on manager mood. | Confirm policy, yes. Then ask: is coverage planned? Is crunch structural or accidental? If every release is a crisis, the problem is planning, not PTO. |
2. "We need to hire someone fast. I know a guy."
| Traditional HR reflex | People Ops reflex |
|---|---|
| Post the req. Run the req. "Culture fit" meeting with no rubric. Hire the manager's friend. Hope it works. | Slow down enough to write criteria. Role description in the handbook. Interview scorecard. "Known candidate" is fine. Unknown standards are not. |
3. "Two teams claim the same ownership. Fight in Slack."
| Traditional HR reflex | People Ops reflex |
|---|---|
| Not an HR issue. Escalate to leadership. Schedule a meeting. Maybe mediation training later. | Facilitate, but insist on a written outcome: RACI, handoff table, doc update. HR/PO doesn't own the tech decision. They own fair process so the fight doesn't repeat every quarter. |
4. "On-call is destroying us. People are burning out."
| Traditional HR reflex | People Ops reflex |
|---|---|
| Suggest wellness webinar. Remind people of EAP. Log the ticket. Close the ticket. | Pull incident and paging metrics with ops leads. Ask execs: is staffing realistic? Document sustainable on-call norms. Burnout is an operating model bug, not a personal weakness. |
5. "We need a new remote-work policy. Now."
| Traditional HR reflex | People Ops reflex |
|---|---|
| Copy another company's PDF. Legal review. Announce in all-hands. Confusion for six months. | Draft with input from teams that actually work remote. Publish in the company handbook next to engineering norms. Explain the why. Iterate when reality disagrees. |
6. "Performance review season."
| Traditional HR reflex | People Ops reflex |
|---|---|
| Force rankings nostalgia. Checkbox forms. Managers rush narratives the night before. Promotions feel random. | Tie feedback to documented goals. Train managers on specific examples. Promotion criteria visible before review, not after. Surprises are a process failure. |
7. "An engineer made a production mistake."
| Traditional HR reflex | People Ops reflex |
|---|---|
| Disciplinary track. Paper trail energy. Person feels punished for being honest. | Blameless incident review first. People Ops supports accountability without humiliation. Repeat mistakes → manager conversation with clear plan. Safety to report beats performative blame. |
8. "What's my career path here?"
| Traditional HR reflex | People Ops reflex |
|---|---|
| Generic ladder slide. "Talk to your manager." Manager has no time. Person leaves in six months. | Published levels or growth frameworks where possible. Connect person to mentor, training budget, internal projects. Exit interviews treated as data, not theatre. |
Where I land
I'm not asking companies to delete HR and slap "People Ops" on the door.
I'm asking for this shift:
- Handbook-first: if it's not written, it doesn't scale and it isn't fair.
- Respect test: would a senior engineer read this policy and feel treated like an adult?
- Department leads stay accountable: People Ops facilitates. It doesn't become a shadow government.
- Metrics that matter: retention, time-to-hire, workload signals, not surveillance cosplay.
- Same table as the business: people systems next to product and finance, not a separate empire.
That's how I'm designing Mini HostPapa. Corporate runs on ERPNext. People policies live in the same knowledge base as CloudStack runbooks. Inspired in part by how GitLab publishes how they operate, adapted for a small host learning in public.
You might not need a new job title. You might need executive cover to run the model you already believe in. Name it. Document it. Measure it. That's People Ops in practice.
Further reading in this project
- Organization & departments (how People Ops fits the org map)
- Executive Overview (values and non-toxic culture standard)
If you disagree with something here, good. Write your version down. That's the whole point of handbook-first culture.