Why do so many media-oriented applications, particularly in the broadcast domain, have such awful user interfaces? One answer could be that whilst software engineers in the media technology space are very clever people, and have solved a lot of very hard problems inherent in manipulating, managing and storing video, none of them would ever be hired as UI designers. Many of them wouldn't actually ever be hired as systems architects either - but that's for another day and another blog post...

At times it is almost like there is a button in the design environment called "Make Crappy" that spits out a standard terrible looking Microsoft based interface, preferably in light sludge grey.  Media asset management/content management applications can be singled out particularly for attention - or lack thereof - most of the UIs on MAMs tend to look as if they were added in a couple of weeks at the end of development - when Marketing reminded Engineering that most creative professionals tend to stay away from the command line. Craft video editing applications tend to be better, but then they should be, as they have had substantial user input over the years.

Hopefully this will change.  There have been a couple of good blogs recently that touch upon this, and I would urge people to send these links to as many vendors as they know.

http://www.marketingtechnologydiary.com/2009/11/dam-20-user-experience-p...

http://www.alistapart.com/articles/the-wisdom-of-community/

There has been some progress - BT Mosaic's UI was actually designed by proper designers and it shows, but I do wonder just how good it would look on the 17inch or 19inch screens that are prevalent in most media organisations, as opposed to the glorious widescreen monitors that you see it running on at trade shows. Regardless of this, they deserve credit for realising the importance of providing tools that actually look and work as if they are intended to be used.

Longer term, this issue may naturally fade away. We are starting to see the emergence (or re-emergence) of 'middleware' tools in media technology that naturally separate the underlying engine that carries out tasks like indexing, searching, moving and conforming, and the user interface into which this functionality is exposed.  As an example, BT Mosaic itself is based on this architectural approach, where the underlying engine is a mixture of off-the-shelf components from vendors such as Oracle and Blue Order, and BT's own custom development, coupled with a rich, browser-based user interface. This emerging architectural approach opens up a lot of interesting potential, and in particular raised the question of just how much of a content/asset management system do most users need to see, and how much functionality should simply be accessed by users from within their existing applications, through mechanisms such as plugins.

Adobe is moving in this direction - several applications in the Creative Suite have, or are expected to have the ability to integrate external functionality using Adobe's Flash technology with a technique called Flex Panels. As an example, editors could search for library content, request transfers and even log data from within an Adobe CS5 or 6 UI, with the asset management system being only a back end that deals with requests from the Adobe tool.  This would allow the software engineers to focus on the hard back end stuff and leave the UI stuff to the Mac-heads. 

There are some systems and technologies coming on the market that support this approach - Alfresco is an advanced and feature rich open source content management system for rich media and documents, and is in fact used by Adobe in its LiveCycle workflow suite.  Vidispine is a new entrant offering media enabled middleware, which specifically does not have a UI, but which is designed to be integrated into other systems.  Even the larger Enterprise Content Management vendors, such as OpenText have the capability to support this approach through their adoption of more open technology standards (despite the fact that the Artesia UI was actually pretty decent).

But to be fair, this is not just about engineers.  It is about technology companies understanding their target users and why they buy products.  And one of the best, and graphical explanations of why we need a step-change in thinking and execution in this area can be seen by following this link.

http://www.scottmonty.com/2009/10/why-apple-google-win-and-your-company....