Information Dashboards could be defined as the interface for information systems, for example, displaying quality control measurments and the result of procesess. Here I am talking about the dashboards displayed on computer monitors, but keep in mind that dashboards could also be mechanical.
Here there are two examples from two different companies (this article is totally independent, images are just examples).
|
Image 1 by Bonavista Systems
Image 2 by Core Metrics
|
The examples give an idea of how critical information could be displayed in an information dashboard. As charts, clocks and colors are typically used all together it is very important to be very careful with the dashboard design. If not, it is highly possible that the dashboard will not help finding the important information in the right moment: imagine that the dashboard is telling the user that something is not working and he just don’t notice it.
Tips for a Information Dashboard Design
1- Do not make excessive use of colors. Filling the screen with a lot of flashy colors is not going to make the user to pay attention but to avoid looking at it. Try to use pastel colors instead of hot red, for example. Keep in mind that many people are blind color, so try not to use color as the only way of driving people’s attention.
|
Image 3 – A graphic like this is not going to help users to identify problems:
|
2- Put all the important information in one page. Try not to hide information behind menus, if you need to do so try to make the navigation fast. Splitting the information in different pages makes the dashboard less useful.
3- Do not display too much information, users can always look for farther details in another place. The aim of the control dashboard is usually to detect deviations and problems fast, not to provide reports.
4- Try to avoid unnecessary graphics. Have a look at the first example I gave (image 1), and notice all the excessive graphics.
5- Choose the right media. Be extremely careful if you decide to use videos, animated images or sounds. They could be very annoying.
Core Metris >> Core MetriCs
Hello Alexis, The Dashboard Spy here.
I always pop up when I see lists of what to do / what not to do when designing digital dashboards.
You said the first example has too much in terms of the graphics. Does that mean the second one is OK?
Isn’t that an opinion?
Take a look at the comments that this post spawned on my Dashboards By Example blog:
Are Digital Gauges Just Eye Candy?
Thanks for you comment.
Saying that first one has too much in terms of graphics does not mean that the second one is right. What I meant was that that one has too much unnecessary decoration.
Thanks,
Alex
Thanks, Mike. It’s fixed to Core Metrics.
Seeing as how this post is a gross simplification of many concepts to keep in mind while designing an informative display, you could have at least included some links to some of the experts in this area – like Stephen Few (http://www.perceptualedge.com) or Edward Tufte (http://www.edwardtufte.com/tufte) to name just a few.
Thanks, Doug, for those valuable links!
sorry,, may i ask something,,?
i was take a project about dashboard information system in small government,, how can i make that with limited scope of information? limited by population information.
i’m from indonesia,, a student. thanks before