What is a skills taxonomy?
A skills taxonomy is an organisation’s structured vocabulary for capability: skills named and defined, grouped into families, given proficiency levels, and mapped to roles. It exists so that staffing, development and hiring conversations use the same words to mean the same things.
The structure is easy. Keeping it true is the whole job.
Building a taxonomy is a workshop exercise: name the skills, define the levels, map them to roles, publish. Organisations do this well and often. What almost nobody solves is the second problem — populating and maintaining the cells. Who has which skill, at what level, still? Launch-day answers come from self-rating and manager estimates, and they age badly: people learn, forget, move roles, leave.
A taxonomy whose levels are eighteen months stale isn’t neutral — it’s actively misleading, because decisions cite it with confidence proportional to its structure rather than its accuracy. The distinguishing question for any skills initiative isn’t how good the taxonomy is; it’s what keeps it true.
Definitions precise enough to test
The quality test for a skill definition: could you write questions that reliably distinguish level 2 from level 3? If not, the definition is vocabulary rather than measurement, and no data will fix it.
Public standards versus custom
Standard frameworks (ESCO, O*NET, sector bodies) save naming effort and aid interoperability; your differentiating capabilities usually need custom definition. Most organisations end up hybrid.
Where taxonomies pay rent
Internal mobility, workforce planning, development targeting and skills-based staffing — but only when the levels are believable enough that decisions actually cite them.
A taxonomy, doing work
The glossary defines it; this shows one in production — skills mapped to roles, each with a live verification state.
Interface shown as an illustration with representative numbers, not a screenshot — the layout is the product’s.
Test your taxonomy’s truth.
Pick one skill family and measure it — the gap between the published levels and the measured ones is the taxonomy’s real state.
The evidence this page stands on
Questions buyers ask
How many skills should a taxonomy contain?
Fewer than instinct suggests. Fifty well-defined, measured skills drive more decisions than five hundred named ones — and the maintenance burden is what kills the large ones.
Taxonomy or competency framework — which do we need?
Taxonomies organise skills; frameworks bundle them with behaviours into role expectations. Many organisations need both, and both fail identically without a truth pipeline.
Should we buy a taxonomy or build one?
Buy the common structure, build the differentiating parts. Nobody’s competitive advantage lives in how they named ‘project management’.
How do AI-generated taxonomies compare?
Useful for first drafts and gap-spotting; still needs human judgment about what matters here, and measurement about what’s true here. Drafting was never the bottleneck.
What’s the minimum viable skills initiative?
One role family, ten skills, measured properly, used in one real decision. That beats an enterprise taxonomy nobody trusts, every time.
See it on your own content.
Bring one course. We’ll show you the retention curve your current training leaves behind — and what scheduled review does to it.
- 30 minutes, on your calendar — pick a slot here
- Run on your own content wherever possible, not a canned deck
- You see the dashboards, the learner surface and the evidence exports
- No commitment — and pilot data stays yours either way