Fix the Asset Hunt Before Buying a DAM

What follows is a composite, written for this article. No real company, no real brand.

A marketing coordinator needs the logo for a print supplier. She finds four files. Two are named for the year, one has a transparent background, one came from a previous agency. She asks in the team channel. Two people answer, and they answer differently. She walks over to the brand manager, who looks at all four and says: that one, and stop using the others.

The obvious conclusion is that the files were badly organised, and the obvious remedy is a digital asset management platform — software that stores, tags, searches and distributes brand assets from one place.

But the hunt ends only when the brand manager makes the missing decision.

Two hunts that look identical from outside

Both begin the same way: a person needs a file and struggles to produce it. From the outside, that is one problem. Underneath, it is two.

In the first, a standing answer already existed, or an existing rule made the right asset determinable from context, but the person could not retrieve it efficiently. The file was buried somewhere outside the usual path, or named in a way that made searching useless, or sitting in someone’s downloads. Everyone would agree once the relevant rule and asset were visible. That is a retrieval problem.

In the second, several plausible files existed and no standing answer covered them — which logo is current, which product claim survived legal review, which photograph may still be used now the model release has lapsed. Somebody has to decide, and they have to decide at the moment of use, under time pressure, and the person looking for the asset may not have the authority to make that decision stick. That is a decision problem.

The test is one question, asked of hunts that already happened. When the asset was finally produced, could the right one have been determined from a rule that already existed — or did somebody have to make a new decision at the moment of use?

What the platform is built for

A digital asset management platform is genuinely built to improve retrieval. Indexing, filtering, metadata, previews, permissions and controlled distribution can make a known asset much easier to retrieve, and can keep it findable as the library grows past the point where any folder structure holds.

It can also enforce a decision once the organisation has made one. It can mark an asset approved, restrict access to superseded versions, require fields to be filled before an upload is accepted, and control who may download what. Those are real governance features and they work.

What it cannot supply by itself is the decision. Which version is current, which claim is approved, which logo belongs in this market, which image may still be used — a platform can enforce every one of those, and it can invent none of them. Load an undecided library into a system with approval states and you get an undecided library with empty approval states, retrieved faster.

The ladder, cheapest first

A missing decision cannot be repaired by better retrieval. Several failure points can be resolved by making a decision before adding software, so work up the rungs in order and stop when the hunting stops.

Define the rule for one asset class

Pick the class that caused the most recent hunt. Decide what makes an asset valid for use: perhaps one logo is current everywhere, or perhaps the correct version depends on market, language or channel. Write that decision down for this class alone. This costs a conversation. The asset stays exactly as hard to retrieve as it was, and every other class stays exactly as it was.

Write the decision where people are already looking

The decision has to survive the person who made it being on leave. A line in the folder, a pinned message, a note in the shared document — the mechanism matters less than the location. This fixes recall, and it leaves the superseded copies sitting exactly where they are, which is why people keep finding them.

Give the answer an owner

New cases will still arrive: a new market, a new campaign, a photograph whose licence is approaching its end. Someone needs the standing authority to answer without convening anyone. This fixes the flow of new decisions, and leaves the backlog of old ambiguities where it sits.

Look at the hunts again

After the team has used the rule on real work, apply the test again to whatever hunting remains. If the hunts have stopped, the problem was a missing decision and it has been made. If the remaining hunts resolve through an existing rule but the asset is still difficult to retrieve, the problem has crossed into retrieval.

The Readiness Threshold

You cross the threshold when the organisation has already made the decisions needed to determine the right asset, and the recurring difficulty is retrieving or distributing it.

That is the state a DAM is designed to improve. Its indexing, metadata, permissions and distribution controls work best when the rules they encode already exist.

Below the threshold, the same features describe a library still waiting for a ruling. The approval states sit empty because no approval was ever given. The metadata fields stay blank because the answer they ask for has yet to be settled. The search works perfectly and returns four logos.

Take the last few asset hunts your team actually had and ask of each one: could the right asset have been determined from a rule that already existed, or did somebody have to make a new decision? The pattern will tell you whether the remaining problem is retrieval — and therefore whether a DAM is addressing the problem you actually have.

Before you bolt on another tool, it is worth knowing whether your business runs on systems or on you. I put together a free 2-minute assessment that gives you a straight read on exactly that, and the first thing to fix. Take the free assessment.