HR business partner interview questions: the seat at the table, earned

Our managing director wanted to announce a machine-shop restructure — 60-odd affected roles — in the same week as the annual pay award, to 'get all the bad news out at once'. Commercially I understood the instinct: one storm instead of two. Operationally it was a mistake, and my job was to say so before it happened rather than manage the wreckage after.

What I brought to the conversation — and I asked for it privately first, MD and me, because challenge lands differently with an audience: three pieces of evidence, not a feeling. First, our own history: the previous restructure's engagement scores, where the site that heard about changes alongside unrelated announcements showed trust scores that took two years to recover, against 10 months for the site that got clean communication. Second, the legal mechanics: bundling the announcements risked contaminating the consultation — employees reasonably hearing the pay award as connected to selection, which our employment counsel confirmed in one phone call would sit badly if we ever faced a tribunal on process. Third, the operational number he cared about most: the machine shop was mid-delivery on our two biggest contracts, and the fitters' overtime goodwill — which those deliveries quietly ran on — was exactly what a botched announcement would burn first.

What I actually said, close to verbatim: 'You can have one storm, but it'll flood the consultation. Give me three weeks between them and I'll give you a cleaner process, a defensible file, and fitters who still pick up the phone on Saturdays.'

He pushed back — the board wanted momentum — and we landed on twelve days rather than my three weeks, with the pay award second, not first. His call, and workable; I said so and meant it.

The restructure ran without a single process challenge, overtime cover held through both deliveries, and — the part I actually value — the MD started routing announcements past me BEFORE deciding, which is the real prize: the challenge bought the seat, not just the decision. What I'd generalise: senior challenge works when it's private first, evidenced in their currency, and ends with you visibly committed to whatever gets decided.

The hardest version I've run: closing a cushion and curtain factory of 85 people — a genuine closure, not a squeeze, with production consolidating to our other site 40 miles away. Collective consultation territory, and the difference between proper and performative was decided in the design, before anyone heard a word.

What proper actually involved, in the order it mattered. Before announcement: a communication plan built around one principle — every affected person hears it in person, same day, before the customers and the local press do; we briefed the works council reps under embargo the evening prior, which is trust spent carefully, and it held. The announcement itself: the MD delivered it, not HR — my drafting, his voice, because people deserve to hear a closure from the person who decided it, and HR announcing closures teaches everyone what HR is for.

The consultation was where 'meaningful' had to mean something: 30 days minimum by law at that scale — we ran 45, and not decoratively. The reps' counter-proposals got costed properly by finance and answered in writing: two were adopted — phased closure over four months instead of nine weeks, which protected customer deliveries AND gave people a real runway, and a transfer scheme with a trial period plus travel support for anyone willing to work at the other site. Nineteen people transferred under it; the original plan had assumed six would.

The individual mechanics: every one of the 85 got a one-to-one within the first fortnight — me and two colleagues, diaries cleared — covering their numbers, their options, and their questions with an actual answer or a dated promise of one. Plus the parts no statute requires: a jobs fair we organised with eleven local employers, CV and interview sessions run on site in work time, and the pension people brought in twice because the over-55s' questions deserved specialists.

The business half held too: not one late customer order through the wind-down, which given 85 people working out a closure tells you how it was handled — people finish properly when the process treats them properly.

What I'd take into this role: consultation is 'proper' when the counter-proposals genuinely could change the plan — and everyone can tell whether that's true within a week. Ours did change it, twice, and that's why the rest of it held.

Our operations board was convinced the branch network had 'a pay problem': driver and rental-agent turnover was running high against our region, the exit interviews said 'better money elsewhere', and the proposed fix was an across-the-board uplift costed at £600,000 a year. The view was set — the budget line was already pencilled.

I asked for three weeks before it went to group, because something in the shape bothered me: our pay benchmarking showed us mid-market, not trailing, and 'money' is what people say in exit interviews when the true answer needs more courage.

The analysis that unpicked it, all from data we already owned: I cut two years of leavers by branch, tenure and shift pattern rather than by role. The 'pay problem' collapsed on contact. Turnover wasn't evenly high — it was catastrophic at eleven of our 60 branches and normal everywhere else, and those eleven shared two features: single-agent weekend shifts (lone working, no cover, every difficult customer yours alone) and — the finding that changed the room — branch managers who'd themselves been in post under a year. New manager plus lone weekends predicted leaving better than any pay band did. And the exit interviews? At those eleven branches, read closely, 'better money' was almost always the second sentence; the first was a shift story or a manager story.

What changed: the across-the-board uplift died — £600,000 unspent — replaced by a targeted package at roughly £180,000: paired weekend cover at the eleven branches, a manager-stability plan (we'd been using those branches as a first-posting proving ground, which the data showed was expensive folly), and a genuinely modest pay adjustment for weekend premiums only, where the benchmarking DID show a gap.

Twelve months on: turnover at the eleven branches within three points of network average, network-wide regretted losses down by roughly a third, and the ops director now asks 'what does the cut say?' before proposing people spend — which is the credibility the question is really about. The method I'd bring here: leadership rarely has wrong data; it has un-cut data. The HRBP's edge is asking it a more suspicious question.

The change as I'd draw it: an advisor's week is shaped by what arrives — the grievance, the absence case, the manager on the phone. A partner's week is shaped by what the business is trying to do that quarter — and the casework still exists, but it's evidence for the agenda rather than the whole job. The advisor answers questions; the partner decides which questions the region should be asking.

The evidence I'd offer that I've been operating across that line for a year, with three exhibits. First: pattern-to-agenda. Handling disciplinary casework across our 70-odd stores, I noticed my caseload clustering — four investigations in six months from stores that had recently lost their dispensing optician to a competitor. Advisors close cases; I took the cluster to the regional director as a retention-and-cover problem wearing disciplinary clothes: stretched teams cutting corners, then being investigated for the corners. That reframe became a locum-cover review I co-ran — and my casework from those stores halved the following year, which is the only KPI for whether the reframe was real.

Second: the manager-capability move. Half my calls were the same six questions from new store managers, so I built and delivered a half-day 'first 90 days as a manager' session with the L&D lead — attendance now standard for new store managers. My call volume from that cohort dropped by roughly a third, which I'd frame the partner way: I automated the advisor part of my own job to buy partner hours.

Third — the one I'd weight most: I've started being IN the room before decisions. When my region planned Sunday-trading pilots, the retail director invited me to the design meetings — not to check the contracts after, but because the previous pilot's rota grievances had cost more than its revenue, and I'd been the one to show him that arithmetic. Advisors get consulted on documents; partners get invited to design meetings. The invitation is the evidence.

What I still need — honestly: exposure to organisational design at scale and to consultation above 20 heads, which is exactly what this role's restructure calendar offers. I'm not claiming the finished article; I'm claiming the trajectory, with receipts.