Another DAM Blog

Blog about Digital Asset Management


4 Comments

Is Digital Asset Management a temporary task?

Some people believe Digital Asset Management (DAM) is a temporary task. However, I would caution them with the following questions to truly answer this for themselves.

  • Are you only accumulating digital assets on a temporary basis? (did you stop accumulating, creating, using, reusing and/or re-purposing digital assets?)
  • Are you seeing any less digital assets over the past few years? (regardless of whether you outsource some of these tasks or not)
  • Are you finding it easier to locate all the digital assets created or acquired by your organization over the past few years? (Research shows that is not the case)
  • Have you seen a complete stop in the production or acquisition of digital assets for any purpose?  (while you still have a job and your organization is not bankrupt yet)
  • Is the rest of the work on your organization’s Enterprise Content Management (ECM) solution a temporary task as well?

The answers to these questions are likely the same. What is the word I am looking for? No.

There are exceptions, of course:

  1. You could live in cave with no internet connectivity (and happen to read this blog on printed paper)
  2. More likely, you really did not stop to think about it that way.(And that’s okay because this blog was written to help inform you.)

Read on and I will explain further.

One of my poll questions asks, “How do you use a DAM?”

The results are quite clear. DAM is mostly used for both archive and production purposes.

Another of my poll questions asks, How often do you add assets to the DAM?

Those results are quite clear as well. Since most people answered daily or weekly, it seems DAM is an ongoing task. Sometimes, it is even a constant business need.

If we have multiple projects with several production cycles creating or acquiring more digital assets and this is ongoing on fairly regular basis, where does the temporary task of digital asset management fall in the equation?

If you answered ‘at the end,’ please explain:

  • The end of what?
  • End of production?
  • End of a whole project?
  • And this was budgeted (with time and money) as a temporary task, right?
  • Oh, forgot to do that again so the next project will pick up the slack?
  • Wait, we need some of those assets NOW (in the middle of this project or another project), but they are nowhere to be found because we have not uploaded/ingested them to the DAM yet. That’s okay, we’ll get to it as soon as we get through the other temporary tasks. Meanwhile we’ll burn more time and money recreating/reacquiring the same assets repeatedly.
  • We have over-inflated budgets for a reason. We will always have over-inflated budgets for every projects, but we don’t get to those temporary tasks. This is a cyclical pattern, even for temporary tasks. And that is why we have temporary positions for temporary tasks because we don’t want consistency or accountability (these are very long words rarely followed).
  • Wait a second, how would other project teams know these digital assets already exist?
  • How would project teams search and find what digital assets were created or completed or cleared for use if that temporary task is not accomplished.
  • How will we volunteer someone to do this temporary task. Repeatedly. And they will know what to do based on all that documentation available, right?

If you answered ‘DAM is not a temporary task,’ you are ahead of the class. Congratulations. You likely understand that DAM involves a regular set of tasks which are part of the production/archival process today. DAM is often an ongoing task.Why would you hire temporary help to do these regular, ongoing tasks?
Is it because you can’t find anyone experienced enough, skilled enough and/or willing enough to do this type work? Where are you looking?

Is it budget issue? (Are you really expecting your budgets to get better “soon” and then make it a priority “someday”?)

Is it a time issue? (Keep waiting so it will only get worse and cost more to fix.)

That will change as soon as the mindset and training of your organization does. It should start with the top of the organization mandating this going forward.

Don’t believe me? Want to continue ignoring the issues? Be forewarned. There will have a rude awakening in the coming future if you do. Here is a refresher in case you forgot why you may need a DAM. It helps to use a DAM properly too.

Let us know when you are ready for some vendor neutral consulting on Digital Asset Management.


2 Comments

What are some DAM job descriptions?

“Mind readers wanted.”

This is first line from an actual Digital Asset Management (DAM) job description posted this year. More on that later.

Aside from asking where to post and find DAM jobs, several people are asking what are typical DAM job descriptions. After presenting this information during a DAM Conference, here are parts of actual DAM job descriptions and knowledge shared by several DAM professionals on the job market today.

This is part of the equation that involves people along with process and technology for DAM.

While some people may use Digital Asset Management (DAM) sometimes within an organization, there is an increase in the need for people who may work full-time on DAM within an organization. We’ll explore several of these positions so you can have an idea of what some organizations have for talent and resources for those who do this type of work.

Here is a part of a job description for a Digital Asset Manager:

  • Responsible for leading overall strategy, implementation and workflow of the Digital Asset Management system for [organization]
  • Acts as primary liaison between [organization] and various photo studios with regard to image names, new photography and archiving
  • Responsible for assigning appropriate metadata for assets to ensure accurate usage rights
  • Manages the Digital Asset system and facilitate the uploading of assets as well as maintaining and upgrading the system
  • Registers internal and external users to the Digital Asset Management system based on permissions
  • Facilitates retrieval of previously cataloged images/shoots
  • Processes raw images using the appropriate software
  • Archive assets as necessary
  • Generates asset download reports
  • Maintains accurate procedures and records for the system
  • Keeps informed of latest Digital Asset Management technology trends and innovations
  • Other duties as identified and assigned

What are we looking for when filling the human resources gap with people needed to help manage your organization’s digital assets?  There are no hard and fast rules, but rather guidelines. Any of these could be staff or contractual positions:

  • Administrator (DBA)
  • Archivist
    • With Digital, not just analog (print) experience
  • Analyst
  • Consultant
    • Either an internal, permanent staff for ongoing consultation OR an external (temporary), outside perspective looking in with a fresh viewpoint
    • Advisor, coach and/or functional role
  • Digital Asset Manager
    • Support DAM system and users
    • An industry expert in the field
  • DAM Specialist/Coordinator
    • Organize and upload assets
    • Metatag assets
  • Data Entry Specialist* (depending on volume)
  • Engineer/Developer/Programmer/Information Architect
  • Help Desk
  • Intern
    • Temporary position (more on this in a future blog post)
    • Willingness to:
      • Learn about DAM
      • Work on metadata and taxonomy
      • Upload assets
  • Librarian
    • With Digital, not just analog (print/physical cataloging) experience
  • Metatagger (aka Metator, Cyberian)
  • Project Manager
  • Sales
  • Taxonomist

What we call the position (job title) is less important than what they actually do.

DAM professionals who communicate with management need to have an understanding of high level business needs and how DAM can meet those needs. Why? Because it is important to quantify:

  • Cost savings
  • Time savings
  • Reductions in risk (with knowledge of rights)

Yes, Digital Asset Management is a business need, not just a technology or another database.

If you are looking to hire a DAM professional, such as Digital Asset Manager, have potential candidates include their answers to the following questions as part of the job application:

  1. Have you worked with a Digital Asset Management System? Where? How long?
  2. How much experience do you have creating Metadata Schema?
  3. Do you have any training experience? What type?

That should help gauge the level of experience of most candidates.

Now about that “mind reader” job posting. Often, management and human resources do not know what DAM professionals are supposed to do (a bit difficult to write a job description that way), but they are slowly realizing there may be a need for Digital Asset Management and that is followed by realizing the need to fill a position with a DAM professional. That professional may be assigned (or volunteered) within the organization. The professional may be hired from the outside. Beside that, DAM professionals should use best practices and notice common behaviors when these practices are not followed. How?

  • Communicate
  • Evaluate
  • Recommend
  • Reference
  • Document
  • Estimate
  • Train
  • Plan
  • Budget
  • Deliver
  • Report
  • Anticipate
  • Follow up

That does not take any mind reading. I am not a mind reader. I am a Digital Asset Manager.

Besides, I forgot my mind reading hat at home.

What is your DAM job description?

Administrator
Business Analyst
Consultant
DAM Architect
DAM Director/DAM Manager/Digital Asset Manager
DAM Specialist/Coordinator
Digital Archivist/Librarian
Engineer/Developer/Programmer
Intern
Project Manager
Taxonomist/Metatagger (aka Metator)


1 Comment

Createasphere DAM podcast interview

Aric Allen of Createasphere interviewed the author of this blog post about what companies need to think about when implementing Digital Asset Management (DAM) and what will be presented at the Createasphere Digital Asset Management Conference in New York in late September 2010.

This interview was recorded as a free podcast which you can listen to now.


Leave a comment

Were you volunteered to work on DAM?

Interestingly enough, many people today do not (yet) plan on a career in DAM, but rather a career in DAM picked them. Sometimes, they were volunteered for the position. Getting volunteered is obviously less of a choice than actually volunteering for a DAM position. This is not likely what you were originally hired to do, but something often quite different with a change in responsibilities. I was lucky enough to volunteer for a DAM position. And yes, I am paid to work on DAM within an organization. I am not the first to do so.

Why would someone be volunteered to work on DAM? Well, let us see. Someone may:

  • Have thrown darts at an organizational chart and guess who was picked?
  • Have been the closest person around when the question of who would do this work came up
  • Have dabbled with image viewers to organize photographs on a personal, hobby or even professional level
  • Have read The DAM Book which is a nice start however it does not touch on the needs of digital asset management for an entire organization (such as an enterprise, hosted or SaaS DAM) with multiple users collaborating with the same assets at the same time with version control and reporting capabilities. And that is just skimming the surface. DAM has a multitude of layers (like an onion) which are often linked and related. That is okay because they will find out soon enough.
  • Know what the acronym ‘DAM’ stands for and is capable to spell it out properly. Many people have difficulty understanding or even explaining what is DAM (I will keep that question open for Another DAM blog post coming in the near future).
  • Show interest in DAM over a period of time. Likely more than once.
  • Be closely tied to the use of the assets (and they may not call them “assets” yet). So the person kind of made sense to ask/volunteer to work on DAM.
  • Be the ‘people’ part of the equation along with ‘process’ and ‘technology.’
  • Have worked with DAM before coming to this organization. Prior experience helps.
  • Have tried the ‘if you build it, they will come‘ strategy. Often, it is realized that does not work (after the fact). Without people working behind the scenes with the DAM, there is often little user acceptance (people actually using it),  few assets uploaded (stuff to find, preview, download) and little metadata (how to find the stuff and tell you about the stuff). Obviously, a fair number of assets with metadata need to be in the DAM before you initially launch it to the users within your organization.

While the DAM vendor may be able to help an organization to a degree, those assets will not automagically get uploaded into a DAM with metadata unless they are supplied by someone. Volunteers? Anyone?

Luckily, whether you volunteered to work on DAM or were volunteered, you are part of the much needed information management group which has a growing group of skilled people. As more DAM solutions are implemented, more positions are opening up. There is a supply and demand equation which favors the employee, even in this economy.

The real issue is once you are there, you have an uphill battle:

  • You will likely need to prove yourself and your recommendations regularly to the stakeholders with results and reach milestones (progress), at least in baby steps.
  • If you are not sure, do not be afraid to seek professional DAM advice (whether internally and/or externally). It is very likely someone has been in your situation before, regardless of the industry. They should be able to advise you and the organization on the best paths to take and the pitfalls to avoid. This can be in the form of consulting. DAM mentoring may be available as well on an individual basis.
  • Document the advice/plan (both the paths and pitfalls in writing) and share it openly within your organization. This should not be a secret, but instead hold the decision makers accountable for what they decide on and advisors accountable for their advice. Even if someone chooses to do differently than what was advised, chances are that at some point, the sound advice given will be revisited, if documented. Give it a few weeks/months and observe.
  • Don’t expect everyone to understand it at your level. For many people, this may be all new, complex and very confusing to them. You will lose their interest, patience and support if you dive into the nuances of various metadata, file versions or permission structures.  Keep it at high level and simplify it unless they specifically ask to follow you down the rabbit hole. And be aware of what pill you take.

Were you volunteered for DAM?