As companies grow, the amount of assets grows with them. The difficulty of organizing them increases. Different departments/groups use their own methods of file naming convention, labeling and organizational structure to house their valuable assets. Technology companies took notice and have started developing platforms and software to capitalize this challenge.
Here is a list of common features clients look for in a DAM system:

- Search by Keyword and Filters
- Organize / Collection / Metadata
- Gatekeep / Permission / Share
- Report
Bynder - A good system with many useful out of the box solutions; it has a clean brand forward UI design. Desired features can be expressed to account managers and be considered for future roadmaps. My experience with this system is the oldest so they most likely won't be applicable to their latest version.
BrandMaker - A basic system with potential once more features are fully realized. UI design is simple and clean. Desired features can be expressed to account managers and be considered for future roadmaps.
- It has the ability to use auto generated tags. Accuracy needs improvement.
- It incorporated search within each menu which is user friendly especially filters and tags tend to grow continuously.
- Some functionalities are made available to users but they don't work appropriately. Such as marking an asset being used in particular project (project management is another module the company provides) in the DAM but doesn't show up in the project management module.
- It lacks administrative tools to make adjustments and corrections to metadata.
BrandFolder - A great system with many useful out of the box solutions; it has a clean visually pleasing brand forward UI design. Desired features can be expressed to account managers and be considered for future roadmaps. πThis is the one I would recommend to use π.
- Along with the basic features listed above, it has useful tools for admins to make changes and correct user errors efficiently. Example, consolidate or correct tags with multiple spelling (Smiling and smiling).
- Since DAM systems lean heavy on visuals, much like the ones listed here, it too lacks the ability to view assets simply as file data. Think of the detail views in Windows or Mac. When naming conventions are followed, one of the best way to weed out errors is through sorting through details without the need of any image thumbnails taking up monitor real estate.
- Search is its best attribute with keyword search and filter search methods. Other systems have caught up to this and have made better iteration of this combination.
- It has many out of the box solutions users look for but sadly they don't work well. Common things I've heard from users are the system is very clunky on both functionalities and its UI.
- It has a lot of potential but it requires a lot of development time to get it to work.
- Support team is slow which affects communications and requires a lot of follow up creating back and forth.
- Latest iteration, AEM Cloud, maintenance update may be made across for all clients who use this cloud based system. Example, client A requested an updated to a feature that they had a problem with or an opinion on how it should function for their particular use. A change is then made across the entire system which now affects client B's process.
- Knowledge base is vast, convoluted and outdated. There are articles upon articles to help you understand the system and how to use it but it is often written in technical terms and structure. It is so dry you will be dehydrated after a few articles. Some of the information is outdated because changes are made fast and furious. My guess is no one can keep up with the changes to make updates to their documents/articles.

