Tag dictionaries that partners actually open
Shared vocabulary between ITAM and cloud cost ops without turning the doc into a novel.
Tag dictionaries fail when they try to be encyclopedic on day one. Ship a single page with eight terms that are actively disputed in your organization. For each term, include a plain definition, a negative example, and the field name where it should appear.
Host a twenty-minute review with one representative from engineering operations, one from procurement, and one from ITAM. Capture decisions as dated addenda rather than silent edits. The date stamp matters when someone asks why a label changed.
Revisit monthly until disputes taper. Expand the dictionary only when new services introduce genuinely new ownership questions. Brevity keeps the document open in browser tabs instead of buried in shared drives.