The HR Function That Reacts vs the HR Function That Leads
Two organizations. Same industry. Same size. Same growth ambitions.
Organization A's HR team finds out about the plan to expand into two new markets three weeks before the announcement. They scramble to estimate headcount needs. They post jobs reactively. Six months later, half the new roles are still unfilled. The expansion is delayed. Leadership blames talent supply.
Organization B's HR Director was in the room when the expansion was first discussed, twelve months earlier. She had already modelled three scenarios. She had identified the 42 net new roles needed, the 14 roles that could be filled through internal mobility, and the 28 that would require external hiring. She had calculated the recruitment timeline, the total cost,
and the skills gap risk. She had a Build/Buy/Borrow/Bot recommendation for every role category.
When Organization B announced its expansion, the people plan was ready.
The difference between these two organizations is not talent supply. It is whether HR was operating predictively or reactively. And the difference between predictive and reactive HR is whether you have a workforce planning model, or just a headcount budget spreadsheet.