The HRBP Job Description Nobody's Rewritten Yet

The HRBP model most companies still run on was introduced in 1997. It assumed employment was a lifelong contract, capital meant humans and money, and HR knowledge was genuinely scarce. None of those conditions hold anymore, and the data on the model's performance says as much: HRBPs spend roughly 30% of their time on strategic work, and only 24% are viewed as strategic contributors by the business leaders they support.

That gap isn't a training problem. It's a structural one.

This builds on an idea my CPO, Steven Bianchi, put into words first: read his original piece here.

The Knowledge Advantage Is Gone

For decades, an HRBP's value rested on knowing things other people didn't: employment law, compensation benchmarking, policy detail. That knowledge is now fully commoditized. Every major language model contains more accessible HR knowledge than any one professional could accumulate across a career. An HRBP whose value proposition is "I know HR" is already redundant, not because AI replaced them, but because the thing they were valued for stopped being scarce.

What hasn't been commoditized is judgment: reading a room, sensing what a policy will actually do to morale, knowing which battle-tested exception applies here and why. That's the part worth building a role around.

The Role Fractures Into Three

Rather than one generalist stretched thin across everything, the job splits into three distinct capabilities.

The Capability Architect. Views the organisation as a system and takes real accountability for whether it has what it needs to deliver, regardless of whether that capability is a person, a process, or an AI agent. Thinks in terms of how the pieces connect, not just what each piece does on its own.

The Human Sensor. Operates where machines can't: reading motivation, morale, and the unspoken parts of the employment relationship. Understands that people choose to stay somewhere based on whether it's a place worth choosing today, not based on an engagement survey score.

The Wisdom Keeper. Guards the organisation's actual way of doing things, the institutional judgment and context that new hires and new systems don't inherit automatically. Makes sure the company doesn't lose its identity in the rush to move fast.

These aren't three job titles to hire for separately. They're three directions an HR professional can specialise toward, and most functions will need all three represented somewhere in the team.

Why Governance Comes Before Automation

There's a genuine accountability risk hiding in this shift. If an AI tool makes an error on something as simple as approving time off, it's often genuinely unclear who's accountable: the person who built the tool, the person who wrote the policy it's enforcing, or the manager who deployed it. In most organisations today, the honest answer is nobody.

The fix isn't to automate faster. It's to decide, before automating anything, which decisions still need a specific human in the loop, and to name that person before the system goes live, not after something goes wrong.

What Good Looks Like

An HR function organised around these three capabilities instead of a flat roster of generalist HRBPs, where each person has a real answer to "what am I accountable for that a system can't be," and where automation gets built on top of a governance decision, not instead of one.