Step-by-Step Guide: How to Map a Skills Inventory Without Job Titles

Eighty-five percent of progressive employers say they've moved to skills-based hiring. Ask the middle managers responsible for the actual hiring, and they'll tell you the same thing: nobody has shown them how to actually build the skills inventory the strategy assumes exists.

This is the practical version. No big consulting deck. Just the steps that produce a working skills map you can use for hiring, mobility, and L&D inside a quarter.

The 7-step skills inventory build

Step 1 — Pick a taxonomy, don't build one

Do not invent your own skills language. Adopt an existing taxonomy (Lightcast, ESCO, or a vendor's) as a base. You can add 10–15% custom skills. Building from zero is where this project usually dies.

Step 2 — Extract skills from what you already have

Use an AI mapping tool to pull skills from existing job descriptions, performance reviews, project documentation, and Slack channels. This gives you a first-pass current-state map without surveying anyone.

Step 3 — Validate with a self-assessment, kept short

Ask employees to confirm or correct ~15 skills the system inferred about them. Not 80. People won't do 80. Fifteen, twice a year, is sustainable.

Step 4 — Add proficiency, not just presence

A skill on a profile means nothing without a level. Use a simple 4-level rubric (aware → practicing → proficient → expert) with one-line behavioral anchors per level. Don't over-engineer.

Step 5 — Map adjacency, the unlock for mobility

Skill X is adjacent to skill Y if 60%+ of the underlying tasks overlap. AI mapping tools do this well. This is what powers "you're 70% there for this role" — the killer feature for internal mobility.

Step 6 — Tag every open role with required vs. nice-to-have skills

If a role has more than 8 required skills, you don't have a role — you have a wishlist. Force the prioritization conversation.

Step 7 — Open the internal marketplace

Once you have profiles, role tags, and adjacency, you can stand up an internal mobility marketplace. Start with stretch projects, not full job moves. It's lower risk and builds the data you need.