HR teams manage employees and skills, finance manages headcount targets and costs, while procurement manages contractors and spending on services. Separate systems, planning calendars, and assumptions make it difficult for managers to see how workforce decisions translate into outcomes. According to SAP research, 62% of senior executives are dissatisfied with the integration between people and business performance data. While 50% of organizations are planning AI’s impact on productivity and capacity, only 21% are assessing its impact on job design and organizational structure.
The workforce now includes not only employees but also contractors, specialist partners, and AI systems that run actual business processes. As a result, automation affects headcount, skills, spending on services, and productivity assumptions at the same time. Reskilling can reduce dependence on contractors, while increasing contractor capacity can close a short-term gap but widen the long-term skills problem. Assessing decisions by different teams using separate data prevents sound planning.
The real issue is not simply choosing between hiring, automation, or reskilling; it is how work will be distributed between people and intelligent systems, and what that will cost. CFOs have to connect financial data to operational choices, while CHROs have to connect it to job design. Working together can shift planning from periodic budgeting to continuous strategic assessment.
Why it matters
This framework shows that workforce decisions cannot be treated solely as the responsibility of HR or finance; choices regarding staffing, outsourcing, skills development, and automation converge in the same cost and capacity calculation. In particular, the failure to adequately reflect the impact of artificial intelligence on organizational structure and job design in planning leaves a gap between productivity calculations and how employees and processes will be reorganized. This requires short-term capacity solutions to be evaluated alongside long-term skills challenges. However, the text does not provide a concrete corporate practice or case; because the methodology and date of the SAP study are not disclosed, it offers limited context regarding the scope and timeliness of the findings.