HR Business Partner

While HR is a single team, it sees the company as one thing. One policy gets written and applied to every department, and requests get handled in the order they arrive. With three or four departments that works fine.

It stops working once departments start having different problems. Engineering cannot find people to hire; sales hires them and loses them within six months. The same remedy aimed at both misses both. And central HR does not sit in department meetings, so it learns about either situation late.

At Pagedeck the gap showed up during mid-year reviews. Three engineers said they were leaving within a month of each other, and HR found out during the first one's exit interview. The engineering lead had been carrying the same worry alone for four months. Nothing was missing from the policies; what was missing was any channel through which HR could see what was happening inside the organization.

The HRBP role is that channel, built out of a person. One HR person is attached to one organization, sits in its meetings, and carries the problems the leader had been holding alone. Rather than writing company-wide policy, this seat applies that policy to the situation in front of it.

It starts by being in the organization's meetings. Sitting inside the group rather than waiting for requests to arrive is the basic posture of the role. The work splits into four blocks.

1. Reading the state of the organization. Regular one-on-ones with the leader to hear what is currently stuck, plus separate conversations with a handful of team members. Also numbers: attrition, the rate at which people leave voluntarily, and the results of the engagement survey, both sliced down to this organization alone. A company-wide turnover rate of 12 percent means little when the assigned division is running at 28.
2. Setting hiring and staffing. Working out headcount — how many people the organization is allowed to have — with the leader, and deciding which seats get filled first. Posting roles and running interview logistics stay with central HR; the HRBP owns the earlier question of which seats the organization actually needs.
3. Running the review and pay cycles inside the group. Helping the leader write evaluations on the performance management schedule, and preparing the calibration meeting that aligns standards across different reviewers. When someone comes up for promotion, checking the case against the career framework that defines each level.
4. Going into problems once they break. How to handle someone falling short of expectations, how to resolve a conflict on a team, whether to try to keep someone who has resigned or let them go — decided together with the leader. Anything that touches employment law or formal policy goes to central HR and outside counsel. The HRBP's contribution here is usually the part nobody else has: knowing both the company standard and the specific history of the team involved.

Block 1 takes the most time, because staying current on what is happening inside the organization is the precondition for the other three.

Three directions, each with a different shape.

• The leader of the assigned organization — the person the HRBP spends the most time with. Not a seat that makes the leader's decisions, but one that supplies the information and the options a decision needs. An HRBP covering engineering at Pagedeck meets Theo's manager every other week.
• People in the assigned organization — a front door for HR questions, though not a counselor. What someone says does not get relayed to the leader verbatim; if it looks like an organizational problem, it goes up in a form that does not identify the person. Where that line gets drawn determines whether anyone trusts the role.
• Central HR — the relationship between the people who write policy and the person who uses it. Payroll, contracts, and process sit with the HR manager, policy design sits with people operations, and the HRBP reports back on how that policy behaves inside the assigned organization. The reporting line usually runs to the CHRO.

That reporting line matters. An HRBP who reports into the organization's leader ends up representing only that organization's interests and has no standing to block a decision that conflicts with the company-wide standard.

"Let's loop in the engineering HRBP on that one."

Bring in someone who knows the organization's situation rather than central HR.

"I talked it over with our HRBP — the promotion case isn't strong enough against the level criteria."

Relaying a leader's judgment after it was checked against the company-wide standard.

"We don't have an HRBP yet, so we have to go straight to the HR team."

Meaning there is no dedicated partner, and requests get handled in the order they arrive.

Pagedeck added its first HRBP after passing sixty people and splitting into three divisions. What the person covering engineering did for the first quarter was sit in the weekly meeting. Around two months in, the leader started raising half-formed concerns while they were in the room.

The third month produced something concrete. The engagement survey pointed to unusually high turnover on one particular team, and the cause turned out to be not pay but the fact that this team alone had no documented promotion criteria. What reached Grace was not "people are leaving" but that one sentence, which is why the next step could be decided on the spot.

The most common misreading is that the HRBP is on the leader's side. They meet the leader most often and carry the organization's goals with them, so it looks that way. In practice the role exists to apply the company-wide standard inside one organization, and blocking a leader's request is a regular part of it. With nobody inside the organization to refuse a salary above the band or a promotion without a case, the HRBP becomes the organization's advocate rather than its HR partner.

The other misreading is that this is the seat that writes policy. It sits in the HR function and deals with reviews and pay, so the assumption is natural. Company-wide policy — review mechanics, salary structure — is set by people operations or the CHRO, and the HRBP runs it inside one organization and reports back on where it does not fit. Blur that distinction and each division develops its own standards, and the differences all surface at once on the day a reorganization merges two of them.