Another DAM Blog

Blog about Digital Asset Management

Why do I need reports from a DAM?


If you select a Digital Asset Management (DAM) solution meant for an organization (rather than a DAM meant for an individual), you should be able to generate reports directly from the DAM.

Why do you need reports from a DAM solution?

Well, let’s see…

How do you measure the progress of your DAM? (How do you spell ROI?)

How often are specific assets used? What are the least used or most used assets in the DAM?

How do you evaluate the quality of all metadata in the DAM?

If you have a ordering system with your DAM, how do you review the orders in bulk?

How many users are actively registered with the DAM?

How many users are actually using the DAM?

Who are the most active users of the DAM?

All these questions can be answered by generating reports from a DAM. Often, the reports are generated by administrator. DAM generated reports hold a wealth of information that can be filtered and sorted to answer plenty of questions as to the progress of the DAM solution within your organization.

What reports can your DAM provide?

How do you use reports from your DAM?

Author: Henrik de Gyor

Consultant. Mentor. Podcaster. Writer.

2 thoughts on “Why do I need reports from a DAM?

  1. We use reporting directly from our DAM to capture user adoption metrics (visits, frequency, duration), downloads, orders. We also use it to measure data quality exceptions to generate reconciliation requests, measure performance of contributors and look for trends that would impact our taxonomy (blended folksonomy/taxonomy environment). We even use reporting to capture clickpaths when we are doing usability studies or rebuilding the search / navigation functions. I get about 15 reports from my dam that tracks more than 40 metrics.

  2. We measured assets added per month, total asset counts, storage size and asset type information. I had 7 different business models so coming up with a good side-by-side comparison was a challenge. We really used metrics as a indicator for user adoption and to recognize changes in usage over time. Even then, it generated some lively discussions.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s