I turned content governance into rules a system could enforce rather than conventions people were expected to follow.
Eli Lilly · CYRAMZA Knowledge Base
Challenge
Medical and promotional content lived across separate assets with no common record behind them. Teams could not reliably tell which version was current, who owned it, or what reuse had been approved. In a regulated setting that uncertainty is expensive: a claim can be reused in a context it was never cleared for, and there is no way to demonstrate otherwise afterwards.
Action
The work was to make governance testable rather than described. I specified permissions, ownership fields, version states, source requirements, and retrieval rules for a controlled repository, each written so it could be checked rather than interpreted. The Requirements Traceability Matrix tied every rule to the owner who would enforce it and the approved source it depended on, which is what made the requirements reviewable by the people accountable for them rather than only by the team writing them. Requirements had to be testable, owners named, and approved sources linked before definition closed.
Result
The specification established how claims entered the repository, who could change them, and which approved materials could consume them. Ownership, version state, role-based permission, and approved-source policy stopped being conventions held by individuals and became properties of the repository itself — inspectable by a reviewer, and enforceable without relying on the person who happened to build the asset.
