HR Business Partner

I don't see the two as opposing forces most of the time, though I won't pretend there's never tension. My approach starts with understanding what the business is actually trying to achieve, not just the immediate request, so I can find solutions that serve both sides rather than picking a winner. When a manager wanted to performance-manage an employee out within two weeks because a project deadline was slipping, I pushed back on the timeline but not the underlying concern: I proposed a structured 30-day improvement plan with clear, written expectations, which protected the employee's right to a fair process while still giving the manager a defined point to make a final decision. The employee ended up meeting the bar and stayed. When advocacy and business needs genuinely conflict and there's no middle path, I'll say so plainly rather than dressing up a compromise as a win for everyone, because leaders trust HR more when we're honest about trade-offs instead of always finding a tidy answer.

I start by listening more than I advise in the first few weeks, sitting in on team meetings, reviewing recent turnover and engagement data, and asking the leader directly what has and hasn't worked with HR support in the past. Trust in this role is built through follow-through more than charisma: if I say I'll come back with an answer by Thursday, I do, even if the answer is that I need more time. Early on with a new sales leader, I noticed his team had unusually high first-year attrition, and rather than opening with that as a criticism, I asked what he thought was driving it. He said onboarding felt rushed. I pulled the data, confirmed his instinct with numbers, and brought him a proposal rather than a lecture. That combination, listening first and then backing up his own read with evidence, got me taken seriously much faster than arriving with a ready-made plan would have.

I treat this as an ongoing discipline rather than something to catch up on when a problem appears. I subscribe to updates from our employment law firm and a couple of specialist HR publications, and I block time roughly once a month to actually read them rather than letting them pile up. For anything that could carry real risk, like a termination in a protected category or a restructuring that affects a works council, I loop in employment counsel early rather than after I've already committed to an approach with the business, because it's far easier to adjust a plan before it's been communicated than after. I also keep a simple internal reference document for common scenarios, probationary periods, notice requirements, right to be accompanied at disciplinary meetings, so managers get consistent guidance regardless of who on the HR team they ask. I'm confident handling routine matters independently, but I'm equally clear with myself about where the line is and when a lawyer needs to be involved.

I start by getting specific about what struggling actually looks like, because vague concern from above them is rarely useful feedback for the manager themselves. I usually gather a few concrete examples, from skip-level conversations, engagement survey comments, or attrition patterns, before I sit down with the manager, so the conversation is grounded rather than accusatory. With one manager whose team had unusually low engagement scores, I found the underlying issue was that he rarely gave feedback outside of the annual review, so people felt invisible day to day. Rather than telling him to 'communicate more', which is advice nobody can act on, we agreed on one specific change: a fifteen-minute weekly one-to-one with each direct report, and I gave him a simple structure to follow for the first few sessions. I checked in with him monthly and the team's engagement score moved meaningfully within two quarters. Coaching works better as a small, specific commitment than a general instruction to improve.

I managed the termination of an employee who had been with the company for six years but whose role had become redundant after a restructuring. He was well liked and the news was going to be hard regardless of how it was delivered, so I focused on making the process as fair and dignified as I could rather than trying to soften something that was inherently difficult. I made sure the severance package was finalised and clear before the conversation happened, so I could answer his questions on the spot rather than leaving him waiting for follow-up. I kept the meeting itself short and direct, avoided vague corporate language, and made space for him to react without rushing him out of the room. I also arranged outplacement support and offered to be a reference, which he later told me mattered to him more than anything else said that day. The team was watching how this was handled too, and several people told me afterwards that the way it was done gave them more confidence in the company, not less.

A department head wanted to promote someone into a people-manager role primarily because they were the strongest individual contributor on the team. I disagreed, based on 360 feedback that consistently flagged the person as difficult to work alongside, and I felt promoting them into management without addressing that first was likely to cause turnover on the team. Rather than simply saying no, I brought the actual feedback data to the conversation and asked the leader what he thought would happen to team retention if the interpersonal pattern continued at a higher level of influence. I proposed an alternative: a six-month stretch project with some team leadership responsibility, paired with coaching, before making the promotion decision. The leader was initially frustrated, but agreed to the delay. The stretch project surfaced exactly the pattern I'd flagged, the individual worked on it seriously with a coach, and the promotion went ahead successfully five months later than originally planned, but with a much better outcome for the team.

I had to tell a team of eight that their department's budget for the next year had been cut by 30%, which meant two roles would not be backfilled after planned departures and the remaining workload would need to be redistributed. I didn't try to spin it as good news or bury it under corporate framing. I explained the business context honestly, what drove the decision and what had already been considered and ruled out, then walked through exactly what it meant for the team's day-to-day work over the coming months. I left real space for questions, including ones I didn't have a full answer to yet, and I committed to specific follow-up dates rather than vague reassurances. Afterwards I met with each team member individually over the following week to check in, because a group meeting is rarely enough on its own for something like this. Several people told me later that hearing it clearly and early, even though it was bad news, was better than the vague hints they'd been picking up beforehand.

I treat HR data the way a good product team treats user data: useful for spotting patterns, but always paired with qualitative context before I act on it. My regular toolkit includes our HRIS reporting, exit interview themes coded into categories rather than read as isolated anecdotes, and eNPS or engagement survey results segmented by team and manager rather than looked at only at the company level. When one business unit's voluntary attrition climbed to 18% against a company average of 9%, I didn't jump straight to an intervention. I pulled tenure data, exit interview themes, and manager one-to-one completion rates for that unit specifically, and found a pattern: most departures happened within the first year and cited unclear expectations. That pointed to an onboarding and early management gap rather than a compensation problem, which is what leadership initially assumed. We fixed the actual cause instead of the assumed one, and attrition in that unit dropped to 11% within two quarters.

I start well before the announcement, working with the business leader to get absolute clarity on the business rationale, because employees can tell the difference between a genuine business need and a decision that's been reverse-engineered to justify headcount cuts. I map the people impact in detail: who is affected, whether any roles trigger collective consultation obligations, and what the timeline realistically needs to be to stay compliant and fair. I prepare manager briefings and scripts so that whoever delivers difficult news to their team is consistent and confident, not improvising on the spot, and I build in one-to-one support sessions for anyone directly affected rather than relying on a single group announcement. Throughout the process I keep a close eye on how the change is landing with the wider team who isn't directly affected but is watching closely, because a poorly handled reorg damages trust well beyond the people who lost their roles. After the dust settles I always run a short retrospective with the business leader on what we'd do differently next time.

I start by talking to each party separately before bringing anyone together, because people are usually more honest one on one than in front of the person they're in conflict with, and I need to understand whether this is a genuine values or working-style clash versus a specific incident that can be resolved directly. I listen for facts I can verify rather than accepting either side's framing entirely, and I'm careful not to signal which side I'm on before I've actually gathered both perspectives. Where the conflict is workable, I'll bring both people together with a clear structure, each stating their view without interruption, followed by a joint conversation about what needs to change going forward, and I document the agreed actions so it doesn't quietly resurface in three months. When the conflict is between two teams rather than two individuals, I usually involve both managers directly rather than trying to mediate the whole thing myself, because a resolution that doesn't include the managers rarely holds. I always follow up a few weeks later rather than assuming the first conversation fixed it.