The CHRO's 18-Month Mandate at Northline Precision
Northline Precision, a 2,400-employee manufacturer with five plants across three states, saw operating margin fall from 11% to 6.4% over three years. The new CHRO inherited 46 HR staff organized as plant-based generalists, each plant running its own recruiting, payroll input, benefits questions, and employee relations. External benchmarking places HR at 2.1% of headcount versus 1.2% for peers. The CEO wants HR out of the paperwork business and delivering workforce analytics for an automation program that will eliminate an estimated 180 production roles while creating 60 maintenance and controls technician roles. Two plant HR managers have privately warned that their plant directors will resist anything that reduces HR presence on site. The CHRO has 18 months and a one-time budget of $900,000.
1. What should the CHRO do in the first 90 days, and what should she deliberately not do?
Read the worked answer
Build a baseline before a structure. Commission work measurement: transaction volume by activity, cost per hire, ticket volume, cycle times, and an activity-by-plant matrix showing which tasks are actually performed by HR versus payroll, IT, or finance. The 2.1% versus 1.2% benchmark is a conversation starter, not a business case, because scope definitions vary; validate it before the CEO or plant directors can attack it.
Secure the real veto holders. The CEO's mandate is necessary but not sufficient. Plant directors control adoption. Recruit two of them as design partners by tying the change to their own pain (open production roles, grievance backlog, slow onboarding), not to HR's cost ratio.
Run one visible proof case. Co-own the automation workforce analytics with operations: which roles disappear, which employees could be reskilled into the 60 technician roles, what the redeployment funnel looks like. This buys credibility for the harder structural work.
Do not do: announce a target operating model or headcount reduction in the first 90 days (it triggers defensive behavior and drives generalist attrition before shared services exists); outsource before processes are standardized (you export a broken process at a locked-in price); or cut HR headcount on benchmark alone before the service model is defined.
2. How should the CHRO manage the plant directors' resistance without slipping the 18-month timeline?
Read the worked answer
Treat the resistance as an interest problem, not an attitude problem. Plant directors are not defending headcount; they are defending response time for staffing, discipline, and grievances, which they currently get from a dedicated generalist.
- Give them a service commitment instead of a person. Convert the generalist relationship into explicit service levels (time-to-fill for production roles, response time on employee relations cases, on-site HRBP days per month) and let them hold HR accountable to those numbers.
- Let them choose within a box. If the decision is that transactional work centralizes, still let plants shape the HRBP role, the on-site schedule, and the escalation path. Participation in design reduces resistance to the parts they cannot change.
- Pilot at one plant. A willing plant with a cooperative director generates internal evidence and reframes the debate from ideology to data.
- Sequence benefits before losses. Plants should feel faster staffing and cleaner data before they feel the loss of a generalist. If the loss comes first, every subsequent problem is blamed on the reorganization.
- Escalate with data, not with authority. If a director blocks a decision inside the governance forum, bring cycle-time and cost evidence, not the CEO's mandate.
Slippage risk is highest in months 4 to 9, when the design is public but benefits are not yet visible. Milestone the plan so that at least one measurable service improvement is delivered to each plant before any role is removed there.
3. Which metrics should the CHRO present to the CEO at the 12-month mark, and what is the risk in the reporting mix she chooses?
Read the worked answer
Report in three layers, because a cost-only dashboard will cause the function to be judged before it is rebuilt.
- Efficiency: HR cost per employee, HR staff to headcount ratio, cost per hire, transaction cost per ticket. These answer the CEO's original complaint.
- Service: time-to-fill by job family, first-contact resolution, case cycle time, self-service adoption, manager satisfaction by plant. These prove the model is not just cheaper but better, which is what protects the program when a plant complains.
- Strategic workforce: redeployment rate of the 180 displaced production roles, internal fill rate for the 60 technician roles, regrettable attrition in critical skills, and cost of the redeployment versus external hiring.
The reporting risk is leading with efficiency alone. If the first three quarters show HR cost falling and headcount shrinking, the plant directors will read the deck as validation of their resistance, and the strategic analytics mandate quietly disappears. The repurposing story (180 to 60) is the one the CEO actually cares about and the one that makes HR indispensable.