Business Glossary

A glossary is only worth building if it is linked and owned. An unlinked glossary is a document of definitions nobody reads; a linked one lets someone looking at a column called cust_st_cd see what it means, who defines it, and which other assets implement the same concept.

The ownership requirement is the harder one. Definitions must be owned by a named business steward with the authority to settle disputes, because the value comes from resolving disagreement, not from recording it. A glossary that contains three definitions of "active customer" because three departments each submitted one has documented the problem rather than solved it.

The maintenance trap is scale. Glossaries that attempt to define every term in the enterprise stall under their own weight, and stale definitions are worse than absent ones because they are trusted. The pragmatic approach is to define the terms that appear in regulatory reporting, executive metrics and cross-domain integration — the ones where disagreement is expensive — and leave the long tail undefined.

Where it connects to architecture: the glossary is the human-readable half of the semantic layer, and the two should reference the same definitions rather than drifting apart. A metric defined in the semantic layer should carry its glossary term, and a glossary term should name its authoritative implementation.