Expressing the Why of the Dashboard
Posted By DashboardWire / 13th June 2010
I would first like to thank Hubert aka the Dashboard Spy for providing the opportunity to blog!
A fellow dashboard designer asked me to reprint this article. He’s asking if anyone can add to this explanation of a business dashboard and the explanation of the dashboard metaphor
So what’s behind the dashboard? Is it really like a auto dashboard?
Why do you need a dashboard? What are you measuring? Why are you measuring it? Why is it important? Is it really important or just nice to know? Now that you have this information, what are you going to do with it? Will this information change how we make decisions? If we had this information X month’s ago, would we be somewhere different today? I.e. would it have caused a change in prior behavior that would have led us down a different path? Does another “dial” on the dashboard tell me the same thing in a different way? Do I need to know this information every day/week/month/year? What is the relevant timeframe to provide the information? I STRONGLY encourage everyone to ask these questions of their dashboards. Write out the answers. REALLY, write them out. Take the time and you will gain new insight that you may not have had before, and may eliminate some extra stuff on you dashboard.
The Tach.
Here is a real world example of what I mean (with a real dashboard). My car has an automatic transmission. It also has a tachometer on the dashboard. Why? What does knowing engine speed tell me, other than how fast the engine is running and that it is running? Nothing. It is just extra stuff to fill up my head as I drive down the road. If the engine quit running, all the other dash lights would come on and tell me the engine was stopped, my speed would be dropping, etc. If I know engine speed that’s ok, but I cannot do anything about it other than step on the gas or brake (as opposed to a car with a manual transmission where I need to know engine speed to optimize gear changing for either fuel economy or performance). It really is useless to know since I can get the same information elsewhere. I watch the tach go up and down and I can tell that the car shifted gears since I can feel it usually. But again, why do I care, I don’t care what gear I am in since I bought an automatic transmission. It takes care of that for me.
The Temp.
I like having the outside temperature gauge on my car so I know how hot or cold it is outside. But didn’t I know that before I got in the car (other than long road trips where you might really have a large temperature change). Again, WHY do I need to know that? Is in nice to know? Probably, but can I do anything about the outside temperature? Can I make it hotter or cooler? Now what if the temperature has dropped below freezing on a trip? Then I really need to know so that I can be more alert for icy patches of road. Now it is something I NEED to know. But only during certain conditions. So there is value to it, but not all the time.
So What?
I hope these two examples will get everyone to think about why they are putting information on a dashboard and how frequently that information needs to be presented. Sure there are a lot of things that are nice to know, but don’t we all have too much information coming at us from all directions? Let’s try to make our dashboards really stand out by having just what we need on them to really manage a company/division/department/process/etc. Just because you can put something on a dashboard does not mean that you should. Think of networking your toaster in your kitchen. You can put it on your home network but WHY?
Thank you for your time reading this. I would like any feedback or your thoughts.
Paul


