Two HR directors. One number. The morning that separated them.
Tuesday, 07:14
The group CFO did not sit down.
"Eighteen percent out of operating budget, by the end of Q3. Every function, no exceptions. Two weeks to tell me how."
Around the table, eleven people wrote the number down.
Marko wrote it down twice, underlined, with a question mark beside it. He ran HR for the services division: nine countries, strong engagement scores, a function that had spent three years earning its seat and was about to be asked what the seat was for.
Ana did not write it down. She ran HR for the industrial division, and she already knew what she was going to cut. She had known since January.
Marko's two weeks
Marko's strategy was thirty-one pages long and it was, by any professional standard, a good document. It mapped every group pillar to an HR domain. It set out fourteen initiatives for the year: a leadership programme, an employer branding refresh, a new LMS, a job architecture review, an engagement survey, a wellbeing framework, an HRIS module, a graduate scheme, and six more.
All fourteen had a sponsor. All fourteen had a business case. All fourteen were, in isolation, obviously worth doing.
That turned out to be the problem.
He started on Wednesday with the leadership programme, and got as far as the COO's calendar invite before he understood the shape of the next two weeks. Every cut meant walking into a specific office and telling a specific executive that their thing was the least important thing in the function. And when Marko looked for the sentence in his own document that would let him say that, it was not there. Nothing in thirty-one pages ranked anything against anything else.
By the second Monday he had stopped looking for it.
He built the alternative instead: fourteen initiatives, each surviving at eighty-two percent. The leadership programme lost its coaching component and became a two-day workshop. The engagement survey would run, but the driver analysis was dropped. The graduate scheme would take eleven people instead of twenty.
He called it a balanced reduction. It passed in nine minutes, and nobody argued.
That should have worried him more than it did.
Ana's morning
Ana's strategy was nine pages, and the first three were an argument rather than a plan.
The argument was on page two. The division had committed to a new production line that had to be running by June. The line needed forty shift supervisors with a specific technical profile. Internally, eleven people could reach that profile inside a year. Locally, the market for the rest was thin and two competitors were already in it. Every revenue number in the divisional plan sat on top of those forty people.
So page two said, in one sentence, that the supervisor pipeline was the only thing HR existed to solve that year, and that everything else was secondary until it was fixed.
Page three was the part almost nobody writes. It was headed What we will not do this year, and it listed six things.
She had written that page in January, when it cost her nothing and made her mildly unpopular for a week.
On the Tuesday of the CFO's announcement, she went back to her office, opened page three, and worked through it in a little under an hour. The employer branding campaign stopped. The job architecture review moved to next year. The wellbeing framework was cancelled outright. The annual survey became a short quarterly pulse. Two long-running projects that had survived purely on inertia were closed.
That came to twenty-two percent.
Then she took four of those points and put them back, into an accelerated technical track for the supervisor pipeline, because it was now the only thing standing between the division and its own plan.
Her submission arrived at eighteen percent net, with one line larger than it had been the year before.
Fourteen initiatives, each at eighty-two percent
Six things stopped, one thing enlarged
The question in the room
The CFO found it immediately.
"You are the only function that came back with something bigger than last year. Explain that."
Ana had been waiting for the question since January.
"If the line does not have forty supervisors in June, nothing else this division does this year matters. Everything I cut, we can do next year. This one we cannot."
There was a pause of about four seconds, which in that room counted as an endorsement.
June
The line started on schedule with thirty-eight of the forty supervisors in place, thirty-one of them promoted from inside. The two gaps were covered by contractors until September.
Nobody in the division ever mentioned the employer branding campaign that had been cancelled, because nobody had missed it.
Marko delivered all fourteen initiatives. It was real work, honestly done, and the annual review said so. The workshop produced good satisfaction scores and no change in behaviour. The survey ran, and without the analysis nobody could say what it meant. Eleven graduates joined a pipeline that needed sixty.
Every initiative existed. Not one of them crossed the line at which an initiative starts to matter.
His budget was cut again the following year, by a CFO who had seen nothing worth protecting.
Ana was asked to present at the group operations review. Not to report on HR. To explain how she had known what to protect.
The proportional cut is the tell
There is a diagnostic hiding in this story, and it is worth saying plainly.
When a function meets a constraint by reducing everything in equal measure, it is telling you that it has no basis for preferring any activity over any other. The proportional cut is not a decision. It is the absence of one, expressed in a spreadsheet.
This is why a budget cut is such an accurate test of strategy. In good years, a list of fourteen initiatives and a real strategy look identical from the outside. Both are busy, both are funded, both produce quarterly updates that read well. The difference only becomes visible the moment somebody asks what you are willing to lose, and by then it is far too late to build the answer.
A strategy you cannot cut with is not a strategy. It is a budget with adjectives.
What Ana actually had
Strip away the story and the difference comes down to three components.
A diagnosis
An honest statement of what is limiting the business, written as a constraint rather than an aspiration. Not "we will build a high-performance culture." Something a CFO could argue with.
A choice
One place where the function concentrates resources, chosen because the diagnosis makes it the binding constraint, and defended against everything else that would like to be equally important.
A stop list
The things the function will not do this year, written down in advance, while saying so is still cheap. This is the component almost every HR strategy is missing, and it is the one that makes the other two operational.
Everything else in a strategy document is context, sequencing and evidence. Useful, but not load-bearing.
Three questions, before someone else asks them
Could you name what you would stop, without opening a spreadsheet?
If the answer needs a round of consultation, the decision was never made. It was only postponed.
Does your strategy contain anything a reasonable executive could disagree with?
A document nobody could object to is a document that decided nothing.
Could a competitor's HR function adopt your strategy unchanged?
If it could, you have written a description of HR, not a strategy for yours.
Most HR functions do not fail the budget cut. They fail an earlier test, quietly, in the month the strategy was approved and nobody noticed that it never said no to anything.
The cut only reveals it.
Your HR deserves better
One call, no slides. A sharp conversation about what your HR strategy would survive — and what it would not.
Book a Call With Us