Digital Asset Management Best Practices

With the questions people currently fail to answer, not with a feature list. Write down the searches that go wrong today — "the approved logo", "photos we may still use", "the final cut" — and design metadata that makes those specific searches succeed. Our step-by-step checklist covers the sequence from goal setting through to adoption.

Export and inspect before you move anything. Keywords, captions and rights fields sit in different metadata standards, and a naive copy silently drops the fields the new system does not recognise. Migrate a representative sample first, verify the fields survived, and only then move the library. Our migration guide covers the order of operations.

A taxonomy should encode what people search for and what governs use — subject, campaign, rights status, approval state. It should not encode what the file system already knows, such as format or resolution, and it should not mirror your org chart, which changes faster than your archive does. Fewer, well-governed fields beat many optional ones.

By measuring the current cost before you buy. Time spent searching, assets recreated because the original could not be found, and licence renewals paid for images already owned are all countable, and all invisible once the system is in place. Our ROI guide covers how to baseline those numbers so the comparison later is real.

History is not the same as control. A version history tells you what changed; version control decides who may supersede an approved asset and what happens to the links already pointing at it. Teams working on editable design files rather than finished exports usually need check-in and check-out, not just a timeline.

Rarely because the software could not do the job. The recurring causes are a migration that carried the old mess across, a taxonomy nobody owned, and a rollout that trained people on the interface rather than on the workflow. Our analysis of failed projects covers what distinguishes the recoveries from the write-offs.

It removes the informal channels that distributed teams otherwise fall back on. When the current asset lives in one addressable place with its approval state visible, the file no longer travels by chat attachment and nobody has to ask which version is current. That matters more the fewer hours the team shares.

The DAM holds the assets; the guidelines say how they may be combined. One answers "which logo file", the other answers "how much clear space, on which background, in which market". Stored together they reinforce each other, which is why our guidelines material sits alongside the brand management guide rather than apart from it.

Decide early which formats are masters and which are derivatives, and generate the derivatives rather than storing them by hand. The alternative — every export saved as its own asset — is the fastest route back to a folder tree. Our multi-format guide covers where that boundary usually falls.

On a schedule, not on complaint. Vocabularies drift, rights expire and campaign assets outlive their usefulness, none of which announces itself. A periodic pass over expiring rights, unused terms and assets with no downloads keeps the library trustworthy, and is far cheaper than the cleanup that follows years of neglect.