Your HRBPs don't have a performance problem. Your operating model does.

A business leader once described his HR business partner to me as "brilliant at getting things done." In the same conversation, he mentioned that he wouldn't think of taking a workforce planning question to her.

He meant both as compliments. Together, they described a failure.

She was the person you called when an offer was stuck in approvals or a policy exception needed sorting. She was fast, reliable and well-liked. She was also never in the room when decisions about the shape of his organisation were being made — and nobody, including her, found that strange.

I've seen some version of this in nearly every organisation I've worked with. The HRBP role is defined on paper as strategic partnership. In practice, it becomes the place where unassigned work goes to live.

---

Start with the calendar, not the capability assessment

Before diagnosing anything, I'd suggest a simple exercise. Ask your HRBPs to log two weeks of their time against four categories:

• Transactional — approvals, documentation, letters, system corrections, chasing
• Advisory-reactive — answering questions a manager or employee could have resolved elsewhere
• Programme delivery — running cyclical processes such as appraisals, engagement surveys, salary review
• Strategic partnership — workforce planning, organisation design, talent and succession, leadership advisory, change

Then compare the result with what the role description promises.

In most organisations I've worked in, the fourth category is the smallest by a considerable margin, and the business leaders are more surprised by that than HR is. The conversation that follows tends to be far more useful than any competency framework, because it reframes the issue from "are our HRBPs strategic enough?" to "have we built a system that permits them to be?"

How the work ends up there

Nobody designs this. It accumulates, usually through three mechanisms.

The escalation ratchet. An HRBP solves something outside their remit once, because a leader needed it and it was faster than routing it correctly. That solution becomes a precedent. The precedent becomes an expectation. Within a year, it's simply part of the job — and it never gets removed, because removing it would feel like a reduction in service.

Manager avoidance. A significant share of what reaches HRBPs isn't administrative at all. It's a manager who is uncomfortable having a difficult conversation and would prefer HR to hold it for them. That work looks strategic when it lands in the inbox. It rarely is.

The ownership gap. Where there's no clearly accountable owner for a category of demand, it lands with whoever responds. HRBPs are, by disposition and design, the people who respond.

Why adding headcount doesn't resolve it

This is the point where most organisations reach for a business case. If HRBPs are overloaded, add HRBPs.

It buys relief for perhaps two quarters. The routing hasn't changed, so the new capacity fills with the same category of work. You've now made the operating problem more expensive without making it more visible.

What a redesign actually requires

Redesign is not an org chart exercise, and it isn't a technology purchase. It comes down to three decisions.

One: who owns each category of demand — and who enforces that routing. Publishing a service model changes nothing. If a leader can still get a faster answer by messaging their HRBP directly, they will, and the model exists only on the intranet.

Two: what managers are expected to handle themselves — with the investment to make that realistic. Shifting work to managers without building their capability doesn't redistribute the load. It delays it, and it returns as escalation.

Three: what HRBPs are accountable for that isn't responsiveness. This is the one most transformations skip, and it's the reason so many of them revert. If speed of response remains the primary measure of a good HRBP, the role will drift back to transactional work within a year, whatever the model says. Accountability has to move to things like quality of workforce plans, bench strength in critical roles, and the organisation design decisions they've influenced.

The part that doesn't make it into the case study

There's a dip.

For a quarter or two, service genuinely feels worse to the business. Requests that used to be answered in an hour now take a day and go through a channel people find unfamiliar. The leaders who most valued their responsive HRBP will be the loudest about it, and they're not wrong — from where they sit, something they liked has been taken away.

If you don't have executive sponsorship that holds through that period, the model reverts. Not through a formal decision, but quietly, one exception at a time.

I've had the opportunity to work through this at scale, including redesigning the HRBP operating model as part of a global HR transformation supporting 300,000+ employees, alongside a broader transformation programme that delivered $2.5 million in savings through process redesign, automation and operational improvements. The structural work was the straightforward part. Holding the line during the dip was not.

---

The aim of any of this is not to make HR leaner, and it certainly isn't to reduce the standing of the HRBP role. It's the opposite. It's to give the people in that role the capacity to do the work the business actually needs from them — and then to hold them to it.