Global Talent Mobility Strategy
A global talent mobility strategy moves the right people to the right locations on purpose, so skills and knowledge travel across the business instead of staying stuck in whichever office they started in.
A five-step sequence covers one move end to end: spotting the skills gap, choosing the right person, planning the move properly, supporting the transition, then tracking that the knowledge actually transferred.
Reach for this when…
- A new regional office has no one who's actually run this kind of team before.
- Your best people feel stuck because the only path up is in a country they can't relocate to.
- Knowledge that exists in one office isn't reaching the others that need it.
How to run it
- Identify the skills and knowledge gaps by location, not just headcount gaps.
- Identify people ready for a stretch move, by potential as well as current role.
- Plan the move: visa, family, cost, and a defined length and purpose, not an open-ended posting.
- Support the transition with training, a local sponsor, and a return or next-step plan.
- Track what moved with the person: the knowledge transferred, not just the relocation completed.
A worked example
Situation. Anna Frei led people strategy at Frei Engineering, a consultancy based in Basel, Switzerland, opening a new project office in Nairobi with nobody senior enough on the ground to run it.
Applied. Rather than hiring cold, she moved a project lead from the Basel office to Nairobi for an eighteen-month posting with a named local deputy shadowing every decision, and a clear return path back into a leadership role at home afterwards.
Result. The Nairobi office was running independently within a year, and the deputy who'd shadowed the posting stepped into the lead role when the original project lead returned home as planned.
The catch
Mobility programmes fail quietly when the moved person's knowledge never gets structured for handover, so it leaves again when they do. They're also expensive and slow if you run them without a clear purpose and end date attached to every move.
If a move doesn't have a named local successor being built up alongside it, you've relocated a person, not transferred a capability.