Second Instalment of David Diamond Interview – DAM Vendors and Partners


Earlier this week, we published the first instalment of an interview I conducted with David Diamond, author of the DAM Survival Guide, founder of The DAM Guru Program and former Marketing Director of vendor, Picturepark.  In this second excerpt, he goes on to discuss whether the characterisation of vendors as villains of DAM by some really is legitimate  and also whether the role of partners is increasing or decreasing: https://digitalassetmanagementnews.org/features/interview-with-david-diamond-part-2/

David’s answers to the vendor question reflect my own views about the subject.  Portraying them as disreputable or untrustworthy just because there are a few who have over-aggressive marketing and a track record of over-promising is not entirely valid as a criticism of the whole market.  There are many firms that do want to deliver value for their end users – and who agonise over whether or not they really are (many of whom I have some lengthy and in-depth conversations with).  A far more significant (and widespread) issue, however, is their lack of vision and inability to genuinely to properly get to grips with the problems faced by their end users.  Our recent coverage of what Ian Matzen has referred to as a DAM Crisis illustrates this point, DAM software still depends excessively on the skill, tenacity and information management expertise of its users to generate ROI.  To implement DAM initiatives effectively, in-house DAM experts are more or less essential in a way that is not the case with other enterprise solutions.

Moving onto the second question about partners, David has some very interesting insight into the right and wrong way for vendors to manage implementation and professional services partners.  As I write, there is a near complete lack of information about how to manage a partner program successfully (certainly in the context of Digital Asset Management) and I know from the numerous questions I get from vendors about this topic that it something else where there are often significant gaps in their understanding.

As we have discussed on DAM News before, partner relationships are one of the methods in which relatively under-capitalised vendors can scale and gain access to horizontal and vertical markets which they might not have been able to justify the cost or risk of on their own.  As such, many would do well to read what David has to say about this subject:

Partners who are more on the development side of things will need to choose their vendor partners carefully. Not only do you have the concept of developer friendliness, in terms of API capabilities; but you have to consider where the vendor sees itself in terms of offering its own services. Will it pull a Canto and compete with partners? Does it have a good track record with regard to warning partners about API breaks and other system changes? Is it transparent with partners with regard to what add-ons or features it plans for the future?  To proclaim a product as “API-first” goes only so far. Is the vendor also “partner-first”? Is it proactively building a partner network, or just allowing one to exist?” [Read More]

In addition to the two parts we have published already, there are several more excepts from the interview I conducted with David which I am in the process of editing (with both his help and guidance).

I don’t think there are many people who consider themselves DAM aficionados now who do not know about our forthcoming webinar, but next week on Tuesday 16th April 2019 at 11am ET, David, Carin Forman and myself are participating in a collaborative webinar panel on The State of DAM Today which will be moderated by Frank DeCarlo and hosted by the London DAM and New Jersey DAM Meetup groups.   If the topics under discussion in this series are of interest to you then I highly recommend tuning in.  I gather from Frank that there will be a recording made, but ensure you register if you want to get notified when it is released.

Share this Article:

Leave a Reply

Your email address will not be published. Required fields are marked *