ISSUE 4

Recent labour market signals suggest organisations are entering what some policymakers have described as a transition phase in hiring. Employers are showing increased restraint, particularly in execution-heavy and entry-level roles, while evaluating how AI will reshape workflows.

Industry surveys report that a significant proportion of companies have reduced hiring due to AI adoption plans. In financial markets, productivity narratives linked to AI are increasingly referenced in earnings commentary and macro analysis. [source]

At the same time, senior leadership at major technology providers like Microsoft AI has started to publicly attach near-term timelines to white-collar task automation. [source]

Job losses are visible events. Conversely, hiring restraint is less visible, but often more consequential. When organisations expect productivity gains from AI, they will begin adjusting workforce assumptions before full deployment of automation systems. The mechanism is straightforward:

So the labour impact emerges through non-expansion rather than direct elimination, changing how exposure should be assessed.

The relevant shift as it relates to job security is in how labour is treated within planning models. As AI becomes embedded in strategic discussion, roles become evaluated against future productivity assumptions. Planning incorporates the possibility that fewer people may be required to produce similar output, which introduces conditionality into hiring. Those conditional roles tend to share characteristics:

Roles tied to decision rights, risk ownership, and outcome justification are likely to remain less conditional because they anchor accountability. It comes down to how easily a role can be absorbed under an improved productivity baseline.

Technology-driven productivity transitions have often followed similar sequences. During early ERP system rollouts, firms adjusted staffing models before full efficiency gains were realised. Hiring slowed in operational functions while systems were being implemented. Headcount decisions reflected expected future integration, not current capability.

The same pattern emerged during early cloud migration cycles. IT and operational roles were reclassified as infrastructure matured, and hiring discipline tightened in anticipation of consolidation.

In both cases, workforce impact followed planning assumptions rather than immediate technological perfection. AI appears to be entering a comparable phase.

The relevant question is whether your role sits inside the zone of conditional expansion. Consider the following questions:

Hiring slows initially where future productivity assumptions can absorb incremental work. This does not require technical substitution to be complete. It requires leadership to believe substitution will improve capacity, and right now that’s becoming an ever more widely-held belief.

This week, we examine:

Workforce compression rarely begins with redundancy notices. It begins with changes in expansion assumptions. So understanding where your role sits within those assumptions is increasingly important.