A Taxonomy Is Not an Architecture

A taxonomy is a vocabulary. It tells you what a skill is called and how it relates to other skills. It is necessary, it is increasingly commoditised, and on its own it changes nothing about how an organisation operates.

An architecture is the taxonomy plus the connective tissue: the mapping of that vocabulary onto real roles and real people, the inference logic that keeps profiles current without asking everyone to self-assess quarterly, and the decision surfaces where the data actually gets used.

The distinction matters commercially. Organisations that license a taxonomy and expect behaviour change are effectively buying a dictionary and expecting a translation service. The subsequent build — usually underestimated by a factor of three — is where timelines slip from months into years.

The useful question when evaluating any skills investment is therefore not 'how good is the taxonomy' but 'what is running, on our data, at the end of this'.