At Thales, sourcing data exposed a hidden business risk: a manufacturing facility that had become geographically isolated as the surrounding industrial estate emptied out. Recognizing this let the team build a business case to relocate the entire site rather than keep fighting to fill roles nobody wanted to take there.
The Hiring Excellence Podcast · Episode 237
Why Talent Intelligence Is Outgrowing Traditional TA Teams
Toby Culshaw explains how talent intelligence grew from a sourcing hack into a boardroom function, and why AI and headless data mean TA can't own it alone.
Johnny CampbellHost · Co-founder & CEO, SocialTalent
What you'll learn
Spot job requisitions that are misaligned with real market salary and skills
Evaluate centralized versus headless models for delivering talent market data
Frame requests to data teams as problems needing expert guidance
Find peer networking communities for benchmarking talent intelligence practice
00:00
--:--
Episode notes
Episode key takeaways
Talent intelligence teams scaled aggressively during the post-pandemic hiring boom, then were among the first functions cut when budgets tightened. Leaders often viewed TI's value as future-facing rather than urgent, making it an easy target once companies shifted into survival mode.
Data quality for talent intelligence varies enormously by geography - the US benefits from strong public labor statistics, while many governments across Africa, LatAm and APAC lack basic visibility into their own workforce. That gap makes benchmarking unpredictable and stretches project timelines unevenly across regions.
Large language models are described as predictive text on steroids, meaning they excel at generic, average answers but struggle to deliver the specificity that real strategic decisions require. Toby warns that teams leaning on AI without recognizing this trade-off risk losing the nuanced expertise that made talent intelligence valuable in the first place.
Benchmarking surveys run through the Talent Intelligence Collective reveal a structural shift: talent intelligence functions used to sit mostly inside TA, but more of them now sit outside it, often folded into people analytics or run directly by the business.
Good to know
Frequently asked questions
The quick answers behind this episode.
How did talent intelligence originate within talent acquisition teams? +
Talent intelligence grew out of sourcing work, where recruiters used market data to explain why roles weren’t filling. At Thales, sourcing intel revealed a manufacturing site had become isolated from its labor market, prompting a relocation business case instead of endless requisition attempts – a shift toward using data to influence business decisions upstream rather than firefighting downstream.
Why do companies cut talent intelligence teams during downturns? +
When hiring slows and budgets tighten, TA leaders often protect only what feels essential to filling today’s roles. Talent intelligence’s impact is usually longer-term, so it gets deprioritized first even when leaders acknowledge the work is valuable, because teams end up operating in what the guest calls survival mode.
How is AI changing talent intelligence and TA work? +
AI tools can produce directionally useful outputs fast, but they generate predictable, average answers unless prompted with real specificity. The risk is teams substituting AI for expert judgment on complex questions like location strategy, losing the nuanced thinking that separates a strong recommendation from a merely adequate one.
What is a headless system in HR technology? +
A headless system separates underlying data from any single interface, letting people pull answers through tools they already use – Slack, Teams, or a chatbot – instead of logging into a dedicated platform or dashboard. It reflects a broader shift toward wanting direct answers rather than reports or graphs.
Should talent intelligence report into TA or sit elsewhere in the business? +
There’s no single right answer. Benchmarking data shows more talent intelligence teams now sit outside TA than inside it, often within people analytics, but moving out can disconnect TA from insights it needs day to day. Some organizations end up rebuilding smaller TI capability inside TA after centralizing it elsewhere.