Owning your voice with people ops as a product work

👋 This is a free edition of the MPL Build Newsletter—resources for running your people team like a product team. Become a paid member to get access to exclusive guides, templates, and case studies.

---

There’s a particular kind of HR professional that every People leader knows, perhaps you’ve even worked with one. They’re extremely competent. They’ve read all the right books, they’ve attended the conferences, they’ve got meaningful opinions about OKRs and performance incentives. They also spend a crippling amount of their time asking for permission.

Permission to run the engagement survey. Permission to change the onboarding flow. Permission to suggest (tentatively, with seventeen caveats) that maybe the performance review process isn’t working.

This is not a dig. It’s a diagnosis. Because People Ops has spent decades earning a seat at the table by being agreeable, and it shows in how we show up as leaders when we’re building.

Something that took me far too long to learn is that agreeable doesn’t build great employee experiences. But being bold does.

Bold isn’t loud, it’s specific.

Being bold as a People leader doesn’t mean storming into the exec team meeting and announcing that HR is broken (though, points for drama). It means having a clear point of view that aligns with the company strategy and goals, backed by evidence, and being willing to defend it when someone pushes back.

Okay, let’s take onboarding as an example. Let’s say your company knows their onboarding may require some work. Exit interview data says it. New hire surveys say it. Managers say it every time they submit their fifth helpdesk ticket of the week about a confused new starter. Eeeeeveryone agrees it’s a problem.

The bold move isn’t identifying the problem, “is onboarding”…that bit is easy. It’s saying: here’s the one thing we’re fixing first, here’s what success looks like in 90 days, and no, we’re not rebuilding the whole thing. Minimum loveable, not maximum ambitious.

That’s specific. That’s defensible. That’s bold.

Stop designing for the risk. Start designing for the person.

A lot of People Ops work is built backwards, starting with the idea of a perfect world , or (worse!) with “what could go wrong?” rather than “what does a great experience look like?” The result is policies that read like legal disclaimers, processes that exist to protect the company rather than support the team’s growth and momentum, and onboarding programmes that are effectively a terms and conditions document with a welcome lunch bolted on.

Bold People leaders flip this. They ask: if an employee were a user and this policy were a product, would anyone actually want to use it? Would it solve a real problem, or does it just cover you in a tribunal?

That reframe changes what you build; because a transparent salary framework isn’t just nice in theory: it removes negotiation theatre, reduces pay inequity, and means candidates stop wasting everyone’s time in an offer process that was never going to work. That’s a product decision. It takes courage to ship it, but the logic is sound.

You don’t need permission to experiment.

I often get asked where to start with People Ops as a Product. I believe one of the best moves a People team can make is to stop treating every initiative like it needs to be perfect before it’s visible. Run a lightweight version. Test a feedback format with one team before rolling it out to 400 people. Pilot a new manager training with volunteers before mandating it company-wide.

Product teams do this as standard. They don’t wait until something is flawless, they build something good enough to learn from and iterate fast. People teams, trained to avoid mistakes in a function where mistakes feel personal, often skip this entirely and either over-engineer or stall completely.

The bold version: ship something small, measure it, tell people what you learned. Even if the first version wasn’t perfect, you’ve demonstrated that your team builds things rather than just advises on them. That reputation compounds.

The business case is your permission slip

If boldness feels risky, evidence is your armour. The People leaders who build real influence aren’t the ones who make the most noise, they’re the ones who can connect their work to what the business actually cares about, what the data supports, and where the company is going.

Attrition in engineering costing you delayed product releases and ballooning recruitment spend? That’s not an HR problem. That’s a revenue problem. Frame it that way, show your data, present your intervention and the metric you’ll track, and suddenly you’re not asking for permission: you’re proposing an empirically-backed solution.

Bold isn’t reckless. It’s informed, intentional, and unafraid to be held accountable for outcomes.

The People leaders who will build genuinely great employee experiences aren’t the ones who waited for the green light. They’re the ones who made a clear-eyed case, started small, proved the model, and scaled it.

That’s available to you right now. You don’t need a bigger team, a new AI tool, or a CEO who finally “gets it.”

You just need to decide that the work is worth doing, and then go and do it.