Taxonomy governance is the set of decisions and roles that keep a controlled vocabulary true. Who may add a term. Who approves a change in meaning. What happens to a term when it is retired, and how often anyone checks.
It is the part of the work that has no deliverable. A taxonomy is a visible artifact somebody can point at. Governance is the reason it still says something accurate a year later. Its absence shows up as drift, and never as a missing document.
Four causes, and none of them involve anybody behaving badly.
| Cause | What it looks like | What it produces |
|---|---|---|
| Slow approval | Adding a term takes a fortnight | People use free text, and the vocabulary stops describing reality |
| Unassigned branches | The owning team reorganised and nobody reassigned | A branch nobody maintains, visibly current and quietly wrong |
| No duplicate check | Two near-identical terms added months apart | Queries split across both and return partial sets |
| Retirement without a pointer | A term is deleted and nothing replaces it | Everything tagged with it is stranded |
Slow approval is the root of most of the others. When the official route is expensive, people route around it, and every workaround adds a term the vocabulary does not know about. A governance model that optimises for correctness and ignores latency produces a vocabulary that is correct and ignored.
Three roles, and conflating any two of them is the common failure.
The failure mode when steward and approver collapse into one is a central team authoring meaning it does not have. The failure mode when they separate too far is a federated model with no structural consistency, which produces several taxonomies wearing one name.
A workable split gives the steward authority over structure and process, and the domain approver authority over meaning. When those two disagree, the steward escalates instead of overruling.
Four fields per change, and anything less is not a review trail.
The last one is the one that gets skipped and the one auditors ask for. A definition that changed with no record of what it changed from leaves every historical report unexplainable, because nobody can reconstruct which version produced which number.
Expressing this in an open standard helps, because the record then travels with the vocabulary. SKOS carries notes, editorial history and replacement pointers, and SHACL can require that a concept has a definition and an owner before it is valid.
Quarterly for a review pass, and immediately when a consuming system reports a problem.
The quarterly pass asks three questions per branch. Is the owner still here and still in that role. Has anything been added without going through approval. Is anything in here now wrong because the business changed. Twenty minutes per branch, and it catches the slow failures before they compound.
The incident path matters more. When a system or a person reports that a term is wrong or missing, that has to reach the approver within days. A vocabulary where reporting a problem leads nowhere teaches people to stop reporting, and after that the only signal you get is the drift itself.
Coverage is the usual metric and it measures the wrong thing. A vocabulary can be exhaustive and still be routed around by everyone who has to use it.
The first and the last are objective and automatable. The middle two need somebody to look, which is itself the point: a governance model nobody checks is a governance model nobody has.
Watch time to decide most closely. It is the earliest signal and the one that moves before anything visible breaks, because people stop proposing long before the vocabulary looks wrong.
How does this sit inside data governance?A taxonomy is one of the things a data governance programme governs, and the review trail it produces is the same evidence an audit asks for. The overlap is real and the scope is different.
Data governance covers access, quality, lineage and policy across the estate. Taxonomy governance covers one narrow question inside it: what the terms mean and who said so. Folding the second entirely into the first tends to lose it, because meaning is slower and less measurable than the other concerns and gets deprioritised against them.
The practical arrangement is that taxonomy governance reports into the wider programme and keeps its own cadence and its own approvers. Data governance for AI covers the wider frame, and taxonomy and ontology management covers running a vocabulary and a model together.
Split structure from meaning, record four fields on every change, and make the approval loop fast enough that nobody routes around it. Latency is a governance property, and a slow process produces an inaccurate vocabulary just as reliably as no process at all.
TopQuadrant's position is that governance is what separates a vocabulary from a list, and that it has to be in the data instead of in a side document. When the approver, the date and the replaced version travel with the concept, the question of what a term meant in March is answerable from the vocabulary itself. When they live in a spreadsheet beside it, they survive exactly as long as the person who maintained it. Taxonomy management covers the surrounding discipline.