I came across to some interesting articles related to what in modern language called UX (User Experience). Articles are from UX Magazine. One of them catch specifically my interest with the topic of Dashboard Design. The another one is more generic – Rich Internet Application Screen Design.
Dashboard UI’s is designed to provide rapid contextual information regarding some higher task or goal, to which the majoritythe user’s attention is directed. This stands in high contrast with regular desktop applications, where the UI is (usually) designed to fulfill a specific task or goal in itself.
Navigation across multiple dashboard pages is a tough subject. There are lots of navigation controls available, but most of them are designed for desktop use. Tabs are an oft-used means of navigation, but they’re only useful if there are few of them. More specifically: any more than seven (plus or minus two) are too many. When the amount of tabs reaches that number, thetime needed to locate the desired tab takes too long for comfort.
Dashboard UIs are an interesting subset of interfaces, and there are some considerable differences between dashboards anddesktops. The examples mentioned in this article show that principles that work in regular desktop interfaces don’t necessarily apply to all types of dashboards. As usual, knowledge of your user, her motivations, and her environment is vitalwhen designing helpful dashboard interfaces. of
I think everybody like Dashboards. In my view, an idea of a dashboard came to the software in general and to the PLM specifically as the way to resolve the complexity of user interaction. However, the idea that in the beginning was clean and bright passed through several conversions and a result is not a good as expected.
Multiple PLM Dashboards I’ve in PLM applications are often becoming a place where a huge amount of information is concentrating. Lots of them actually running so after the goal to bring as much as possible information to the display, and it makes Dashboard absolutely un-usable.
My conclusion- in order to make a successful dashboard, you need to know your user. Dashboards cannot be created for multiple types of users and several goals. The single goal and user-oriented scenario is absolutely needed to create a successful one. The general purpose dashboard has no chance to get their original goal – simplicity. Absence of focus on the specific goal does not allow to show only needed information and in the comfort way for understanding (graph, map, gauge, etc.).
I’m very interesting to hear what is your experience in dashboard creation. What are the successful ones and what are those dashboards that failed? I’m looking forward to our discussion.
Best, Oleg
