A metadata strategy isn’t documentation—it’s architecture. Every field, tag, and rule is a structural beam that holds creative work together.


⚠️ The Challenge

After a major platform migration, Horizon Collective’s new DAM system looked perfect on launch day—custom fields, a polished taxonomy, everything color-coded and approved.

But six months later, searches failed, folders multiplied, and the taxonomy became more wish list than system.

The strategy had been written, but not lived.

The team needed more than metadata fields—they needed a backbone.


⚙️ The Approach

Rebuilding began with one question: What decisions should metadata make easier?

From that answer came a modular strategy built on five layers:

  1. Field Design: Align every field with a user question or system function.
  2. Taxonomy Mapping: Create crosswalks between content types, departments, and platforms.
  3. Governance Workflow: Define ownership by function, not hierarchy.
  4. Training Materials: Turn documentation into living guides—embedded where work happens.
  5. Audit Cadence: Review every six months for drift, redundancy, and new use cases.

Each phase connected design to behavior. The Metadata Strategy Toolkit became both reference and ritual—the living manual of the system.


🎯 Takeaway

A metadata strategy isn’t complete when it’s documented—it’s complete when it’s understood.