How long should it take to find a known asset?

Under 30 seconds for any asset a regular user knows exists. Over a minute means your search, your taxonomy, or your file naming is broken, and the fix usually starts with metadata, not search software.

What is a healthy metadata-completeness rate?

Above 90 percent for required fields on assets created in the last 12 months. Anything below 70 percent means the upload workflow has a hole, not that users are lazy. Fix the workflow, not the users.

Why do users keep their own folders?

Because they do not trust the DAM. Trust is rebuilt by making the library faster, more complete, and more current than their local folders. Once one or two power users see the DAM beat their workflow, the rest follow.

How many approval steps is too many?

More than two is usually too many. The teams that solve approval bottlenecks do not add reviewers, they remove the decisions that did not need a person looking at them in the first place.

Should rights metadata be required or optional?

Required, with a clear default for the most common case. Optional rights fields stay empty, which means assets get used without anyone knowing if they should be.

How often should I run this diagnostic?

Quarterly. The questions are designed to surface drift. Programs that score well one quarter often slip two quarters later when a new platform integration, leadership change, or content campaign shifts behavior.

How to tell if your DAM is actually working

A six-question diagnostic for operators. Answer honestly. The pattern of your answers tells you where to focus.

Most DAM programs are judged by whether the software is installed and the contracts are signed. That is the wrong test. The real question is whether the library is the first place your team goes when they need an asset, and the easiest place to put one when they make a new one.

Six questions tell you whether your DAM is actually working. Answer honestly. The pattern of your answers points to where to focus next.

Take the interactive diagnostic →

Question 1: How long does it take to find a known asset by name?

Good: under 30 seconds, every time. Broken: over a minute, or the user gives up and asks a colleague.

If finding takes too long, the problem is almost never search software. It is your taxonomy or your file-naming conventions. Consistent file names do more for findability than any search feature a vendor ships.

Question 2: What percentage of assets have all required metadata?

Good: above 90 percent for assets created in the last 12 months. Broken: under 70 percent.

A completeness gap is almost always a workflow gap. The upload form is too long, the required fields are unclear, or the AI tagger missed a category. The fix is to walk through one upload as a real user and find the friction.

Question 3: Can a user see at a glance who can use this asset, where, and for how long?

Good: yes, on every asset, with no further clicks. Broken: rights information lives in a spreadsheet, a contract, or someone is head.

If rights are buried, assets get used out of bounds. That is a brand and legal risk, and it shows up as a problem long before anyone connects it back to the DAM.

Question 4: How many approval steps does an asset pass through before use?

Good: two or fewer for most assets. Broken: four or more, with frequent reviewer absences blocking the queue.

Approval bottlenecks are governance design problems, not workflow software problems. The teams that solve this do not add more reviewers. They remove the decisions that did not need a person looking at them in the first place.

Question 5: Are people reusing assets, or making new versions of things you already have?

Good: high reuse, low duplication. Broken: the same asset exists in five variants, each made by a different team that did not know the others existed.

Duplication is the symptom of failed discovery. Users do not duplicate on purpose. They duplicate because they cannot find what already exists.

Question 6: When someone needs an asset, do they go to the DAM first?

Good: yes, by reflex. Broken: they go to a colleague is folder, a shared drive, or Slack search.

This is the meta-question. If users go elsewhere first, all the metadata in the world will not matter. Trust gets rebuilt by making the DAM faster, more complete, and more current than the alternatives.

Scoring yourself

Count how many questions you scored Broken on. Three or more means the foundation needs work before any AI feature or new platform will help. The fastest path is usually to fix question 1 or 2 first, then questions 3 and 6 will start to fix themselves.

Where to go next

If the foundation is broken, the next move is to measure rather than guess. MQS scores your library against your taxonomy and tells you exactly which fields, which assets, and which workflows are leaking. The diagnostic above is the qualitative view. MQS gives you the numbers.