Taxonomy Governance

A taxonomy without governance is a taxonomy with a slow decay timer. The decay is not dramatic — it is incremental. One contributor creates a near-duplicate category. Another uses "Client" where the standard is "Customer." A third adds a new tag without checking whether an equivalent already exists. After 18 months, the taxonomy has drifted far enough from its design that users distrust it. Governance is the system that prevents this drift — not by bureaucratizing every edit, but by providing clear ownership, clear change processes, and regular drift detection.

1. Assign a Taxonomy Owner One person is accountable for the taxonomy's integrity. Not a committee — a person. Committees approve changes; one person owns the day-to-day. The taxonomy owner maintains the controlled vocabulary, reviews flagged inconsistencies, approves new category or facet value requests, and runs the quarterly drift audit. Without a named owner, accountability diffuses and nothing gets enforced.
2. Define the Change Process Document the path for requesting a new category, renaming an existing one, or deprecating an old one. The process should have three tiers: minor changes (alias additions, documentation updates) approved by the taxonomy owner alone; moderate changes (new facet values, category renames) requiring owner review and a 5-business-day comment period; structural changes (new top-level categories, facet dimension additions) requiring a formal review with domain leads. The process does not need to be heavy — it needs to exist.
3. Implement Drift Detection A quarterly drift audit covers: categories with no items added in 90 days (potential dead categories), items classified in catch-all or "General" categories (orphan content), near-duplicate category names identified by string similarity, and facet values with fewer than 3 items assigned (potential over-classification). The audit is a report, not a judgment — it surfaces what needs attention and routes it to the taxonomy owner.
4. Communicate Changes Proactively When a category is renamed or deprecated, notify contributors who have content in that category before the change takes effect. Silent renames break muscle memory and create distrust. A one-line email — "The 'Customer Onboarding' category is being renamed to 'Client Onboarding' on [date]. Your content is automatically reclassified." — is the difference between a smooth change and a support ticket three weeks later.