Every media team we've worked with has the same complaint, almost word for word: we spend too much time looking for things. They mean files, versions, the final cut of a video, the right export of a photo, the original sound design without the music bed. The cost feels invisible day to day, but it's enormous.

The five-percent problem

When we audit how a small in-house team spends its week, somewhere between five and fifteen percent of working time goes to finding, requesting, re-downloading or recreating assets. For a ten-person team, that's the equivalent of half a person's salary spent on searching. Most teams have no idea the number is that high - they treat the friction as part of the job.

"The cost of bad asset management isn't downtime - it's the steady drain of people doing slightly the wrong thing because they couldn't find the right thing."

The three failure modes

The problems we see are remarkably consistent. There are three patterns, usually all three at once:

Naming as memory

"Final_v3_USE_THIS_ONE.mov" is funny until it's the actual filename of the cut that aired. When the only memory of which version is correct lives in the filename, every handoff creates a tiny risk of error. The teams that survive scale move that information into metadata - version, status, approval, intended use - and out of the filename.

Storage as archive

Most teams treat their file server as both a working space and an archive. The result is that the working space slowly fills with old assets, and the archive is full of working files. Searching either one becomes painful, so people stop bothering, so duplicates proliferate.

Rights as folklore

"I think we can use that - ask Sarah" is not a rights management strategy, but it's how most teams operate. Music licences, stock photo terms, talent releases - they end up scattered across emails, contracts and people's memories. When a clip needs to be re-used three years later, nobody is quite sure if it's allowed.

What a good DAM actually does

A digital asset management system isn't really about storage; cloud storage is cheap and easy. What it provides is structured metadata, controlled vocabulary, version history, rights tracking and a search experience that actually returns the right asset. Done well, it pays for itself within a year - usually faster.

The trap is over-spec'ing. Most teams need maybe a third of the features in the platforms they shortlist. Start with the assets that hurt most (usually video or licensed imagery), get those onto a system that just works, and expand from there.

A small case study

We worked with one regional broadcaster who estimated they were re-licensing about £40,000 of music a year because they couldn't reliably find what they'd already paid for. After six months on a properly structured DAM, that line item dropped by more than two thirds. The system paid for its first three years inside its first year. Not glamorous, but real.

If your team is in the "we spend too much time looking for things" stage, it's almost certainly costing more than you think. Happy to take a look.