10 short questions that assess your DAM system needs
A key part of demoing DAM systems, writing a request for proposals, and evaluating providers is understanding why you need a DAM system. Looking at your current workflow is a great place to start.
The list of questions below is designed to get you thinking about how your assets are being handled from creation to distribution, and who is accessing them.
The information you gain from this self-assessment will inform the use cases in your request for proposal and request for demo and be beneficial when you begin implementation. It will also help you prioritize requirements into “must-haves,” “nice-to-haves,” and “future needs.”
Prioritized requirements and user scenarios are key to finding a DAM system that meets your needs.
If you are using a DAM system already or want a more in-depth look at auditing your DAM system, check out the post How to effectively audit your Digital Asset Management software.
Auditing systems and workflows helps paint a picture of who handles assets along the way and what they do with them. For example, a graphic designer creates assets, and then puts them into a repository or sends them to someone. Somewhere along the way, the assets are approved and final versions are made. Where is the repository for final versions, or who receives the final assets?
10 questions to ask yourself and your stakeholders
- What type(s) of digital assets do you use?
- Who creates digital assets for your organization?
- Who approves digital assets?
- What happens to your assets once they are approved?
- Where are digital assets stored?
- If someone requests an asset, who fills the request? Identify all the parties involved.
- How are the digital assets delivered?
- How are use policies or copyright guidelines delivered?
- Where are original files or raw files stored?
- Where are expired assets stored?
- What are some things that have spun out of control in the creation, management, distribution, or preservation of digital assets in your organization?
You might want to map out your current workflow on a blackboard or pieces of paper. Seeing your current process as a whole is a great to determine who your users are, what areas of the current workflow are troublesome, where you want to see improvements, and where potential risks lie for losing assets.
Do you see any questions or considerations missing from the list? Add your suggestions in the comments.