Skills have been on my mind a lot lately, from our 2027 Skills Intelligence Report to rolling out skills across our own team at Docebo. So I went digging to find more examples of how other leaders are building skills strategies in their organizations.
Meet Enrique Ortega, Head of HR Business Partner and Talent at Provident Mexico, a lender whose purpose is a better world through financial inclusion. His skills playbook drew 70%+ adoption within weeks, uncovered hidden talent, and gave the C-suite data on who’s ready and willing to move.
Before we dig into the how, let’s start at the root cause. Why skills, why now?
Provident Mexico makes small loans to people and small businesses, and it has about 2,500 employees split between head office and the field. When the team began opening new branches across Mexico, they went looking for talent internally.
“We thought that we had the pool of talent. But when we need it, it doesn’t exist,” Enrique says. And the people they could find didn’t want to relocate.
Enrique’s diagnosis: the available talent was there, but nobody could see it.
The invisible talent problem
Where did the talent data live? In managers’ heads and in outdated titles, he says.
When Enrique asked managers about skills, they named a person and a job title. There was no data behind it, just what the manager could recall. And skills that live in one manager’s head leave when that manager does.
A title shows where someone is today. Capabilities show where they could go. And that view of the workforce was missing.
The field made it even harder. Field employees, the company’s biggest population, aren’t always connected at a desk, so the company wasn’t (quite literally) seeing their talent.
Building an internal talent marketplace
Enrique’s team changed that in 12 weeks.
Enter: Talent Connect, Provident Mexico’s talent marketplace. Its goal was connecting people’s skills to real opportunities.
Enrique and the Provident team launched Talent Connect in four waves, with field employees first. They had the least visibility and the most to gain: a massive population with few chances to grow. Enrique’s rule was that the skills platform and strategy had to work for anyone, regardless of title or level.
HR uploaded every job description with the capabilities each role needs. Employees added their information, or imported it from another professional network, and saw the company’s roles laid out in a “universe” view. Then they compared their skills against what the next role asks for, and Enrique says that could put them a year, or two, or three from ready.
It also solved a job findability problem. HR used to post vacancies, and employees said they couldn’t always find them. Now openings sit in the same universe view, next to the skills each role requires.
70%+ adoption in the first few weeks
When asked for an early win, the number Enrique reached for was adoption. More than 70% of employees adopted the platform within weeks of launch.
There was no big campaign. His pitch to employees was simple: the whole company can see you, beyond your own manager.
After employees filled out their profiles, they came back asking what else they could do.
This time when the Provident Mexico team went looking for talent internally, they found it.
Here’s one of Enrique’s most telling examples. An outside consultancy was working on a project using a very particular methodology. Partway through, HR learned that someone on its own L&D team already knew it.
That’s what a talent visibility problem looks like. The skill was down the hall, and nobody knew to ask.
Across a company of ~2,500 employees, moments and opportunities like this really add up.
The C-suite now sees who’s ready
Leaders used to wait for HR to hand them information about their people. Now they can see their teams’ skills and gaps themselves, and what they ask HR for has shifted from training requests to questions about what the next step requires. Enrique calls it a cultural evolution.
"Being a skills-based organization gave us an edge on our competitors. Now we think about where people can be, instead of where they are right now."
It also changed how the C-level talent ID review runs. His team downloads the data and shows how many people are ready to move, how many are willing, and how many have the skills identified as critical.
Three things worth stealing
Run the title test this week. Ask managers what skills their team has. Write down whether each answer is an actual skill or a static job title.
You don’t have to build everything at once. Provident focused on field first when rolling out skills intelligence: lowest visibility, most to gain.
Launch before the descriptions are perfect. “Don’t wait to have the perfect architecture,” Enrique says. “Just start.” Launch with what you have and evolve it along the way.
What is most interesting to me is how ordinary the starting point was. Provident wanted a clearer view of the people already inside the company. That view surfaced skills nobody knew to ask about, showed field employees where they could go, and gave the C-suite data on who’s ready and willing to move.
So here’s my question for you: if someone on your team already had a skill you were about to go outsource, how would you find out?

