Skills Mapping for HR: How to Know What Your Team Can Actually Do

The VP of Engineering needs someone who understands machine learning pipelines. She doesn’t need a full-time ML engineer, just someone with enough background to ask the right questions in a two-hour vendor evaluation.

Nobody in People Ops knows if anyone in the 200-person company has that skill. Slack messages go out. Engineering managers get pinged. LinkedIn profiles of current employees get searched. Four hours later, it turns out someone on the Data Analytics team spent three years building ML systems at her previous company. She never mentioned it because her current role didn’t require it, and nobody had ever asked.

This is the skills gap that matters most: the gap between what your people can do and what you know they can do.

Skills Nobody Knows You Have

Companies simply don’t know what skills they have in-house. Ask any VP of People whether they have a complete picture of their workforce’s capabilities and the answer is almost always no. Skills data is scattered across resumes that were reviewed once during hiring, LinkedIn profiles that may or may not be current, and the memories of managers who’ve worked with people long enough to know what they can do.

Nearly every company, then, is making workforce decisions (hiring, project staffing, promotions, training investments) based on job titles and assumptions rather than actual capabilities.

You see it play out in three places:

External hiring for internal skills. Companies spend months and thousands of dollars recruiting for capabilities that already exist in-house. SHRM’s 2024 Talent Trends report put the average cost per hire at $4,700 for professional-level roles, and for specialized technical positions, that number can triple. Every unnecessary external hire when an internal candidate existed is money and time wasted, plus a missed development opportunity.

Adjacent skills, the things people learned in previous roles, side projects, or self-study, are the ones most likely to go unnoticed. Nobody puts “I can do Python data analysis” on their profile if their current role is product management, even though that skill could save a colleague two weeks of vendor evaluation.

Without knowing what skills people already have, training budgets get misallocated. Generic programs replace targeted interventions. You end up sending people to courses on things they already know while missing the skills they need.

Why Most Companies Never Start

Skills mapping doesn’t fail. It never gets attempted.

The reasons are predictable: it feels like an HR project with no clear payoff. Nobody knows where to start. The HRIS doesn’t have a skills field. And the one time someone proposed it, the response was “we’ll get to that next quarter,” which means never.

Companies that do start often over-engineer it. They build elaborate competency frameworks with 200 predefined skills, then ask employees to rate themselves 1-5 on each one. The result: checkbox fatigue, generic self-assessments, and a spreadsheet nobody trusts. Is “Python” one skill or twenty? Does “project management” mean the same thing to an engineer and a marketer? Rigid taxonomies force people into boxes that don’t match reality.

A third failure mode: collecting good data and then burying it. Skills data that lives in an HR spreadsheet nobody else can access answers questions for HR but doesn’t help the VP of Engineering find someone who knows ML pipelines. If only HR can search it, most of the value is lost.

A Better Approach: The Living Skills Inventory

Three principles that work in practice.

Let People Describe Their Own Skills

Instead of a predefined taxonomy, give people a freeform field. “List the skills you’d be comfortable helping a colleague with.” This simple prompt produces more specific and useful data than any competency framework.

People know what they’re good at; they just need a place and a reason to say it. When you ask “rate yourself 1-5 on the following 80 competencies,” you get checkbox fatigue. When you ask “what do you know that others might not?”, you get real answers.

We have seen this work at companies between 80 and 300 people: adding a “Skills & Expertise” section to every employee profile and asking people to list three to five things they would be happy to be consulted on. The fill rate consistently beats traditional skills surveys because the prompt is lightweight, the result is immediately visible to colleagues, and people can see what others wrote before filling in their own.

Make Skills Searchable, Not Just Stored

Collected skills data is only useful if it’s discoverable. When the VP of Engineering needs an ML expert, she shouldn’t have to ask Tom to search a spreadsheet. She should be able to type “machine learning” into a search bar and see who comes up.

This is the difference between a skills database and a skills directory. A database stores information. A directory makes it findable by anyone who needs it. When skills data is buried in HR systems, employees can’t find each other and expertise stays invisible.

Skills data should live where employees already look for people: in the org chart or employee directory, not a separate HR system. When someone searches for a colleague, they should see name, role, team, and skills in one place.

Keep It Alive Without Forcing Updates

Treating a skills inventory as a one-time project is the fastest way to kill it. The best thing you can do is make updating it effortless and part of existing routines.

After project completion: “You just wrapped up the payments migration. Want to add any new skills to your profile?”

During one-on-ones, managers can ask “Have you learned anything new this quarter that we should capture?”

New hires fill in their skills as part of onboarding profile setup, when they’re most motivated to show what they bring.

This turns the skills inventory from a snapshot into a living document that gets richer over time, without anyone being assigned to “maintain” it.

Certificates vs. What People Actually Know

Formal certifications and real expertise are not the same thing. This disconnect shows up everywhere: someone has a project management certification they haven’t used in years, while the person everyone actually goes to for project advice has zero formal credentials but twelve shipped launches under their belt.

A good skills inventory captures both but weighs self-declared expertise and peer recognition more heavily than credentials. Instead of asking “what certificates do you have?”, ask “what would your colleagues come to you for?”

Where to Start (It’s Smaller Than You Think)

Open your HRIS or employee spreadsheet. Add one column: “Would consult on.” Send it to five managers and ask them to fill it in for their direct reports. You’ll have a working skills inventory by Friday. It won’t be perfect. It doesn’t need to be. A rough inventory that people can search beats a pristine competency framework locked in an HR drive.

That company from the opening never did a formal skills mapping initiative. They just made skills visible. Within three months, they’d staffed two internal projects with people whose expertise had been invisible, avoided one external hire, and cut the average time to find an internal expert from “days of Slack messages” to “one search.” Start with visibility, and the rest follows.