A skills taxonomy is a framework that defines the skills within an organization, how they are grouped, and the proficiency levels for each, enabling the association of skills with roles, individuals, and decisions. It serves as the common foundation for building skills inventories, competency matrices, and talent maps. Its development involves six steps: purpose, information gathering, categories and levels, baseline measurement, validation, and maintenance.
People management has been shifting from position to skills for some time now, and the pace is not slowing down: according to the Future of Jobs Report 2025 by the World Economic Forum, Employers surveyed expect 39% of workers' core skills to change by 2030. Without a common language to name them, each department describes them in its own way, and there is no way to compare them.
Table of Contents
What is a skills taxonomy?
It is a standardized, hierarchical system that classifies people's skills and relates them to the skills the organization needs. It answers three questions:
- What skills exist? The skills and knowledge required to perform the tasks and roles of the company.
- How do they relate to each other? They are grouped by affinity: digital, interpersonal, leadership, technical.
- How is the mastery of each one measured? It establishes levels of competence that allow for objective comparison.
It's not just a simple list of labels. When done well, it allows you to link a skill to different roles, projects, or sectors, identify transferable skills across areas, design learning and career paths, and connect talent with business strategy.
To fulfill that function, a good taxonomy must be:
- Exhaustive, but manageable: It gathers the relevant skills without becoming unmanageable.
- Updated: adjusted to today's needs and those that are foreseeable.
- Modular: Skills can be grouped, combined, or adapted to different roles.
- Measurable: Each skill can be linked to a way of assessing its level.
- Actionable: It guides specific processes such as selection, training, succession, or internal mobility.
Is it the same as Bloom's taxonomy?
No. If you search for the term on Google, most of the results talk about Bloom's Taxonomy, which is an educational tool: it classifies learning objectives by levels of complexity of thinking (in its revised version, from remembering to creating) and is used to write objectives and design tests.
The HR skills taxonomy classifies job capabilities to describe positions and people. Both share a useful idea, progression by levels, and for this reason some teams draw inspiration from Bloom's Taxonomy to define proficiency levels. But their purpose is different: Bloom's Taxonomy organizes what is learned; a skills taxonomy organizes what is needed and possessed to do the job.
Taxonomy, inventory, matrix and competency map: how do they differ?
They are all parts of the same system and are often confused. Taxonomy is the dictionary; the other tools use it.
| Tool | What does it answer? | What it contains | What is it used for? |
|---|---|---|---|
| Taxonomy of skills | What skills exist and how are they ordered? | Definitions, categories, and mastery levels | To provide a common language for the entire organization |
| Skills inventory | What skills does each person have today? | Registration per person and current level | Knowing the starting point |
| Competency matrix | What level of qualifications does each position require, and what level does each person possess? | Cross-training or people with skills | Identify individual and team gaps |
| Skills or talent map | Where is the talent and what is missing in the organization? | Aggregate view by areas, potential and gaps | Plan selection, training, succession and mobility |
If you're going to start by registering what's there, the guide to doing a skills inventory in your company explains the process; to cross positions and levels, the one of how to build a competency matrix.
What types of skill taxonomies exist?
There is no single way to classify skills. These are the most common approaches, and many companies combine several:
| Guy | How to group | Advantage | Limit |
|---|---|---|---|
| Functional or organizational | By departments, roles, and hierarchical levels | Very much in line with the operation of the business | Not very flexible in the face of technological or strategic changes |
| By skill type | Hard, soft, cognitive, digital, leadership | Versatile and transferable across roles and sectors | Adapting it to the company's structure takes time |
| By levels of mastery | From basic knowledge to the ability to teach others | Useful for learning paths and progression | It requires properly measuring each person's level beforehand. |
| By tasks or results | Because of the tasks it allows you to do or the result it achieves | Useful in selection for positions based on objectives | It falls short if the catalog isn't updated |
| External or standardized | Frameworks of international organizations | Extensive coverage and external validation | It needs to be adapted to the reality of the company |
A functional example: a technology company detailing the technical engineering skills, sales skills, and competencies of those who lead teams. A task-based example: in customer service, active listening is linked to customer satisfaction, conflict management to incident resolution, and data analysis to identifying retention opportunities.
In a tiered model, a four-point scale works well: 1, basic or theoretical knowledge; 2, application in simple tasks; 3, application in complex or changing situations; 4, ability to teach or improve that skill in others.
What reference frameworks can you use as a basis?
There's no need to start from scratch. These public frameworks serve as a starting point for naming and defining skills:
- ESCO, The European classification of skills, competences, qualifications and occupations of the European Commission. According to the Commission, It describes 2,942 occupations and 13,485 skills linked to them. capabilities pillar It is organized into four subcategories (knowledge; skills; linguistic skills and knowledge; attitudes and values) and indicates for each concept its level of reuse: cross-cutting, intersectoral, sectoral, or occupation-specific. It is available in Spanish, making it practical for companies in Spain.
- O*NET, from the U.S. Department of Labor. content model It organizes information for each occupation into six major areas, including the characteristics of the worker, their requirements (skills, knowledge, training) and the activities of the position.
- SFIA, The skills framework for the digital world, widely used in technology, defines professional skills and seven levels of responsibility that serve as a model for the domain levels.
The drawback of any external framework is the same: it describes generic occupations, not your specific roles. Use it for vocabulary and structure, and adapt the definitions and levels to what actually happens in your company.
How to build a skills taxonomy step by step?
The steps change depending on the size of the company and the objective, but these six are essential:
- Define the purpose and scope. Decide what you want it for (career plans, selection, restructuring) and whether it will cover the entire company or only key functions.
- Collect and analyze existing information. Descriptions and job profiles, Performance evaluations, current development plans, key business competencies, and external frameworks are all considered. This involves area managers, HR, and employee representatives to gain a comprehensive understanding.
- Categorize and rank. It groups skills into logical categories (technical, transversal, leadership, digital) and sets the mastery levels for each one, with an observable definition per level.
- Measure the current level in the organization. A useful taxonomy needs to know the starting point, and self-assessment alone is not enough. Standardized tests allow us to measure each skill, identify individual and collective gaps, and personalize development. For example, if the taxonomy includes problem-solving as a critical skill, the Hirint test library It includes a Problem-Solving test (10 minutes) to see how developed the template is. For technical skills, the assessment of hard skills of the candidates It follows the same logic.
- Validate and adjust with those involved. Review the proposal with management, team leaders, and employee representatives to ensure it is relevant and fits with the organization's culture.
- Implement and keep the taxonomy alive. Integrate it into role design, selection, training, performance, succession, and internal mobility, and review it on a fixed schedule as business and technology change.
How do you move from taxonomy to skills intelligence?
Taxonomy provides the language; skills intelligence is using measured skills data to make decisions. With taxonomy as a foundation, HR can:
- Select by skills (skills-based hiring): define the position by what you need to know how to do and choose the psychometric tests that measure it, not just filter by degrees or years of experience.
- Detecting gaps between the level required by each role and the level of each person, and deciding between training, moving, or hiring.
- Planning for succession and internal mobility with comparable criteria across areas.
- Add the data on a talent map that shows where the organization's strengths lie and what is missing.
The condition is the same in all cases: the results of a test complement the CV, the interview and the judgment of the person in charge, and the final decision is human.
What mistakes should be avoided when applying a skills taxonomy?
- Treat it like a list of tags. Every skill needs definition, levels, and a method to evaluate it; otherwise, it does not allow for comparison.
- Make it too big. Hundreds of skills without prioritization paralyze their use. Start by reviewing the critiques of each job family.
- Copy an external frame without adapting it. ESCO or O*NET provide vocabulary, but they don't know your positions.
- Relying solely on self-assessment. People tend to overestimate or underestimate their skill level; social desirability plays a significant role, especially in soft skills. This contrasts with tests and with the supervisor's observations.
- Decide with just one piece of information. No single skill, personality, or cultural fit should be the sole criterion.
- Forget the regulations. Evaluating candidates and employees involves processing personal data: people must be informed and the GDPR and applicable labor regulations must be respected.
- Do not keep it. A taxonomy that is not reviewed becomes outdated in a short time.
If you want to move from taxonomy to real data about your workforce's skills, Hirint can help with this through its service. Talent Mapping: predictive profiles, skills gap and high potential based on standardized assessments.
Frequently Asked Questions
What is a human resources skills taxonomy?
It's a framework that defines the skills within the organization, how they are grouped, and the proficiency levels for each. It serves as a common language for describing positions, evaluating individuals, identifying skills gaps, and planning training, succession planning, and internal mobility. It differs from a list in that each skill has a definition, levels, and a method for measuring it.
What is the difference between taxonomy and a competency matrix?
The taxonomy defines and organizes skills: it's the dictionary. The competency matrix uses this dictionary to cross-reference positions or individuals with skills and levels, thus identifying gaps. Without a taxonomy, each matrix names skills in its own way, making it impossible to compare teams or departments. The taxonomy is agreed upon first, and then the matrices are built.
Does ESCO serve as a skills taxonomy for a company?
It serves as a starting point. ESCO, the European Commission's European classification, describes some 13,485 skills linked to 2,942 occupations and is available in Spanish. It provides vocabulary and structure, but describes generic occupations: it's advisable to adapt the definitions and levels to the actual positions within the company and focus on the critical skills for each one.
How many domain levels should a taxonomy have?
It depends on the use, but four or five levels are usually sufficient to distinguish between them without complicating the assessment. A common scheme progresses from basic knowledge to application in simple tasks, application in complex situations, and the ability to teach others. The important thing is that each level has an observable description that two evaluators would interpret in the same way.
How often should a skills taxonomy be updated?
It's advisable to review it regularly, for example, once a year, and also whenever the strategy changes, a relevant technology is incorporated, or new positions emerge. Employers surveyed by the World Economic Forum expect 39% of workers' core skills to change by 2030: an unmaintained taxonomy quickly becomes obsolete.