John Honovich, on his IPVideoMarket.info blog, posted an interesting article on ease of use or user interface design and how it applies to products typically found in the video management space.
I found his article http://ipvideomarket.info/report/easy_to_use_video_management_software a very compelling read and wanted to compare some of his findings to our experience here at Envysion.
His first and most important point is “Training = Failure” – I couldn’t agree more. Our goal at Envysion is to build software that does not require any training to use. Our goal is that with at most a 5-10 minute demo, most users should be able to navigate the software, search for recorded video with data, and share that video with others. Based on customer feedback to date, we seem to be generally reaching that goal.
John also raises a very interesting point about the type of person and their skill sets for whom the video application is designed. My general sense, especially when walking the floors of a conference such as ASIS, is that nearly all vendors design their system for the security professional, who is typically located in a video room with a wall of monitors. Their user interfaces are focused around cramming as many features into a single screen as possible. How else, for example, might you come up with the idea to display 48 thumbnail sized live video channels on a single screen? These professionals may represent perhaps less than 1% of the total population of a company that has video cameras in use.
At Envysion, on the other hand, we design our application for the other 99% of the population of the company. This includes marketing, sales, IT, operations, management, human resources, and so on. To be successful in this, we constantly have to balance complexity and features with ease of use and simplicity.
Use of icons, as John points out, is a great example of this balance. With Envysion, we used to use a number of icons for functions such as “edit user” or “remove user”; based on customer feed back we have found it much more effective to use simple words such as “edit” or “delete”. As a result, we’ve removed many of these icons and replaced them with text.
Another challenge that we face, especially with a web-based application, is consistency of style. Just because you may have hundreds colors doesn’t mean that you should use them all. We have found it important to be very consistent with respect to fonts, colors and general style-sheet items. A great example of this is the design of buttons. We have found it very helpful to insure that buttons have an identical look and feel. In addition, our users appreciate that fact that the most commonly pressed button in a specific situation (e.g., the “OK” button in a search dialog”) is highlighted to stand out. You’ll find this technique used in many web sites today. (Hint: look for the shape and size of the “purchase” or “buy” button on any commerce web site).
This same approach applies to links within a page. Users always appreciate common indicators that a link exists – e.g., the link is always a specific color and has the same behavior when you hover over it. Wikipedia is a good example of this behavior.
For those of you who are curious about our application, I’ve posted a short demonstration of our application below.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=f624b8d3-a876-4069-b1ac-c9c167ac7528)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=46200602-3db7-4fb4-981b-a02e3e00c8c8)