I have already posted about our experience at this years Henry Stewart DAM Symposium. Here are a few other observations I made and discussed about on Linkedin.
Although I have attended HS many times in a different capacity, this was the first time OpenEdit has exhibited . I didn't have high expectations regarding attendance but it was better than I had imagined. Our booth had steady foot traffic the entire show, 35 one on one demos!
I was also somewhat concerned how this crowd would respond to open source - they responded VERY positively.
Perhaps it was because we are open source, I noticed that most visitors to our booth were technical staff, not so much the end user.
There were only about a dozen vendors but considering many companies have come and gone or been purchased by others and accounting for the economic conditions, seemed about right.
Some attendees were looking at DAM for the first time but most already had commercial systems installed, although a few of those folks were looking for alternative solutions, such as EnterMedia. :-)
There were sessions sponsored by vendor's but most sessions had a nice array of users who spoke about their general experiences with DAM. I've always thought that both new and experienced DAM users get the most out of those sessions.
One very nice aspect of having HS at the Hilton rather than Javits Center is that it's more personal for attendee's. For instance, refreshment breaks and meals turned into round table discussions about DAM, I don't recall that happening so easily at Javits. Best idea's come from impromptu meetings like these.
Would be nice to see a session or two dedicated to open source. I know HS has done this in the past but my experience says the time is ripe to offer it again.
Julie - one way to help sell OSS for those who are skeptical (and unwilling to simply look at EM as another product) is to highlight all the OSS components they already use, both at home and in the enterprise, and high-profile, successful businesses running on top of these tools. FireFox and Webkit (Safari); Apache, Tomcat; Postgres and MySQL (Facebook); PHP (Facebook), Ruby(Twitter), Drupal (TheOnion), and on and on.
Once you've gotten the notion that OSS is inherently unprofessional or non-enterprisey out of the way, then you can focus on your product on equal footing. While licensing costs are one point of comparison, for many DAM projects it's only one piece of the pie, often not even the largest. Ease of development for customizations and integration are important to highlight - this is one area where OSS can shine, simply because you're more likely to attract more developers willing to play with your product *at home* when they are working with it at the office (I'm not suggesting you'll get lots of 3rd party contribs, but I've seen over and over that when an enterprise product makes itself easily available to devs to install and play at home, they thrive on it - this doesn't have to be OSS, it can simply be a free, downloadable license for non-commercial use... something more flexible than just the dev instance we get with some enteprise deals).
Some early morning coffee thoughts,
- Roger Howard
twitter://rogerhoward
rogerhoward@mac.com