Managers who are given high autonomy and accountability naturally start treating their teams as personal territory, which quietly blocks internal movement even when everyone agrees mobility matters. This isn't malicious - it comes from a genuine drive to hit performance goals, but it hardens into silos over time.
The Hiring Excellence Podcast · Episode 234
Building Internal Mobility at Scale: Microsoft's Playbook
Microsoft's former EMEA/Asia TA leader explains how internal mobility got stuck, and what it took to fix it at scale.
Johnny CampbellHost · Co-founder & CEO, SocialTalent
What you'll learn
Reframe internal outreach language to avoid triggering manager defensiveness
Map the small number of distinct pathways mobility actually happens through
Diagnose why top performers rarely search internally for new roles
Design guardrails that let recruiters approach internal talent responsibly
00:00
--:--
Episode notes
Episode key takeaways
The real trigger for change wasn't a mobility campaign - it was financial. Microsoft kept making people redundant, then rehiring for adjacent roles months later, often ending up looking at the very people they'd just let go, which finance could tie directly to wasted cost.
A major structural enabler was building a company-wide skills taxonomy years before the mobility push existed - not designed for this purpose, but foundational to it. Without that shared skills language, employees couldn't map their own profile against open roles or see what learning closed the gap.
The team underestimated resistance from HR business partners, not frontline managers, because those HR leaders empathized so closely with the leaders they supported that they pre-emptively worried about losing talent. This forced the team to add guardrails and narrow its original ambition for TA-led outreach.
Some of the friction removed was self-inflicted rather than necessary - Thom describes building self-service pathways where a documented succession case lets someone move roles without extra sign-off once criteria are met. That level of automation only became viable after skills data and platform maturity caught up.
Good to know
Frequently asked questions
The quick answers behind this episode.
Why did Microsoft's internal mobility culture weaken over time despite low attrition? +
As Microsoft grew from around a hundred thousand to over two hundred thousand employees and roles became deeply specialized, particularly in customer-facing technical positions, moving between domains got harder because it required years of acquired expertise. Combined with managers protecting their best people, mobility slowed even though people stayed at the company a long time.
What business case justifies investing in internal mobility technology? +
The clearest justification is cost: Microsoft found it was making roles redundant, then rehiring for adjacent skill sets months later, sometimes even re-approaching people it had just let go. Tying this to finance data on the cost of redundancies, empty seats, and lost revenue built the appetite that had been missing when the idea was first raised years earlier.
Do you need a skills taxonomy before building an internal talent marketplace? +
Microsoft’s experience suggests yes, especially at large scale. They built their own company-wide skills taxonomy years before the mobility initiative and found it foundational to enabling employees to map their profile against open roles and identify learning gaps, even though some vendor platforms claim to generate this automatically.
How should TA teams handle manager resistance to internal talent outreach? +
Expect resistance not just from people managers but potentially from HR business partners who closely align with those leaders’ concerns. Building guardrails around when and how recruiters can reach out, framing it as an ask rather than aggressive sourcing, and tying every change back to a clear business imperative helps get buy-in without triggering defensiveness.