Your DAM Is Not a Production Tool
Digital asset management and production media management are two different problems. Most teams need both, and the systems don't talk to each other. Content that can't be found has no value.
Last year I spent forty minutes trying to find a specific shot from a shoot we'd done eight months earlier. I knew the shot existed. I could picture it, a wide of the factory floor with late afternoon light coming through the clerestory windows, forklift in the mid-ground, no people in frame. I needed it for a corporate sizzle reel and I knew we'd shot it on the second day.
I looked in the project folder on Google Drive, then the archive folder, then the backup drive, and then I asked the editor, who had moved on to another job and vaguely remembered the footage being on an external hard drive that might still be in the office. It was. The shot was in a folder called "Day 2, misc" with no metadata, no tags, no description beyond the camera-generated filename.
Forty minutes for a shot I knew existed and could describe in detail. If I hadn't known it existed, I'd never have found it at all. This is the asset management problem in production, and it's bigger than most people realise.
The DAM and MAM split
There are two categories of system that handle media assets, and they solve different problems. Digital Asset Management platforms, Bynder, Brandfolder, Canto, that category, manage finished, approved assets for distribution. They're designed for marketing teams who need to find the latest approved logo, the brand-compliant product shot, the Q3 campaign hero image. They do this reasonably well. Bynder in particular has a solid interface for brand asset distribution if you can stomach the price tag, which starts somewhere north of fifteen thousand a year and climbs from there.
Media Asset Management platforms, Iconik, CatDV, Dalet, manage production media. Rushes, rough cuts, sound elements, graphics packages, the raw material of production rather than the finished output. They understand proxies, timecodes, and media formats in ways that DAMs don't.
The problem is that production teams often need both, and the two categories don't integrate. Your DAM doesn't know about your project timeline. Your MAM doesn't connect to your task list or your budget. Neither one includes project management capabilities. So you end up with an asset system sitting alongside a project management tool sitting alongside a review platform, all operating independently, all requiring someone to manually keep them in sync.
The metadata problem
Nearly half of employees surveyed say their company's digital organisation system isn't effective or easy to navigate. The root cause is inconsistent metadata, and it's a harder problem than it sounds. One person tags a document "Marketing." Another person tags the same document "Advertising." Both are technically correct. Neither is helpful when someone searches for "brand campaign Q2" six months later.
Iconik has done interesting work on AI-powered tagging, and it genuinely works for visual content, identifying objects, scenes, and activities in footage without human intervention. That's impressive. But automated tagging only solves part of the problem. The project context, which client this was for, which campaign it belongs to, what rights are attached to it, whether the talent release covers international distribution, that still requires human input, and most systems make that input tedious enough that people skip it.
The archive as afterthought
Everyone skips archiving and everyone regrets it. Not immediately, but six months later when the client calls about re-licensing footage for a different market and nobody can find the talent releases. Or when a similar project comes in and the team recreates assets that already exist because finding the originals would take longer than making new ones.
Rights management is the layer that makes archiving genuinely complex. Stock footage licences expire. Talent releases have geographic and temporal limitations, a release signed for UK broadcast doesn't necessarily cover digital distribution in the US. Music licences may restrict usage to specific media or territories. All of this information needs to live with the asset, accessible to anyone who might want to use it, updated when terms change. In practice it lives in a contract folder that nobody opens until legal asks.
We're building Telova with archiving as a first-class stage rather than an afterthought, with rights tracking attached to the assets themselves. But honestly, even getting teams to treat archiving as a real step rather than something they'll get to later would be a significant improvement on the status quo.