A skills taxonomy is a promise. Measurement keeps it.
Every skills strategy starts with a taxonomy — the structured naming of what the organisation needs to be good at. Most taxonomies then die as spreadsheets, because naming skills was never the hard part. The hard part is attaching truth: who actually has what, at what level, still.
Why taxonomies die, and what keeps them alive
The taxonomy project produces a beautiful artefact: skill families, proficiency scales, role mappings — endorsed, published, and stale within a year. It dies because nothing feeds it: levels were populated by self-rating at launch and never again; the org changed; the spreadsheet didn’t. A taxonomy without a truth pipeline is org-chart poetry.
The living version inverts the effort: modest structure, serious measurement. Skills get definitions precise enough to test; diagnostics and practice data populate levels continuously; decay shows as decay. And because the levels are believable, decisions start citing them — staffing queries, development plans, hiring specs — which is the only survival mechanism a taxonomy has ever had.
Structure sized to reality
Fifty well-measured skills beat five hundred named ones — we help scope taxonomies to what the organisation will actually maintain and decide on.
Import what exists, measure what matters
Existing frameworks — internal, vendor or public standards — import as structure; measurement attaches where decisions need truth first.
The taxonomy as query surface
Who can cover X at level 3? Which team is thinnest on Y? Where did Z decay since the reorg? — questions the living taxonomy answers in seconds.
The taxonomy, kept alive
Skills, levels and role mappings that update as measurements arrive — a taxonomy that describes people, not a PDF.
Interface shown as an illustration with representative numbers, not a screenshot — the layout is the product’s.
Bring your taxonomy, dead or alive.
We’ll attach measurement to one skill family and show the spreadsheet becoming a query surface.
The evidence this page stands on
Questions buyers ask
Taxonomy versus competency framework — the difference?
Taxonomies organise skills; competency frameworks bundle skills with behaviours into role expectations. In practice they converge, and both die the same death without measurement — the sibling page covers frameworks.
Should we adopt a public standard taxonomy?
Standards help interoperability and save naming effort; your differentiated skills still need custom definition. Import the standard, extend where you’re distinctive, measure everywhere.
How granular should skills be?
Testable granularity: if you can’t write questions that distinguish level 2 from level 3, the definition is decoration. Granularity follows measurability.
What does maintenance cost once it’s live?
Near zero for levels (practice data maintains them) and periodic review for structure — a quarterly hour against the annual re-launch the dead version needs.
Can AI generate our taxonomy?
AI drafts structure and definitions usefully; your leaders’ judgment on what matters is irreplaceable. Same pattern as everything here: machine drafts, human decides, measurement keeps everyone honest.
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