By applying the following good dashboard design principles, this dashboard could have been improved dramatically
1. The 5 Second Rule
Your dashboard should provide relevant information in about 5 seconds.
Your dashboard should be able to answer your most frequently asked business questions at a glance. This means that if you’re scanning the information for minutes, this could indicate a problem with your dashboard’s visual layout.
When designing a dashboard, try to follow the five-second rule — this is the amount of time you or the relevant stakeholder should need to find the information you’re looking for upon examining the dashboard. Of course, ad hoc investigation will obviously take longer; but the most important metrics, the ones that are most frequently needed for the dashboard user during her workday, should immediately pop from the screen.
2. Logical Layout: the Inverted Pyramid
Display the most significant insights on the top part of the dashboard, trends in the middle, and granular details in the bottom.
When designing a dashboard, it’s important to follow some kind of organizing principle. One of the most useful ones is the [removed] [removed]
How does a journalistic technique relate to dashboard design? Well, business intelligence dashboards, like news items, are all about telling a story. The story your dashboard tells should follow the same internal logic: keep the most significant and high-level insights at the top, the trends, which give context to these insights, underneath them, and the higher granularity details that you can then drill into and explore further at the bottom.
3. Minimalism: Less Is More
Each dashboard should contain no more than 5-9 visualizations.
Some dashboard designers feel the need to cram as many details as possible into their dashboard in an effort to provide a fuller picture. While this might sound good in theory, cognitive psychology tells us that the human brain can only comprehend around 7+-2 images in one time — this is the number of items you want in your dashboard. More than that just translates into clutter and visual noise that distracts and detracts from the dashboard’s intended purpose.
You can avoid visual clutter by using filters and hierarchies (e.g. instead of having one indicator for amount of sales in North America and one for South America, give the user the option to apply a filter which changes the same indicator between one and the other) — or simply by breaking your dashboard into two or more separate dashboards.
4. Choosing the Right Data Visualization
Select the appropriate type of [removed] according to its purpose.
We’ve written before about [removed] so I won’t go into too much detail here — suffice to say that data visualization is intended to be more than mere eye candy — they should serve a specific purpose and convey specific facts in a more effective way than the basic tabular format.
Before choosing a visualization, consider which type of information you are trying to relay:
- Relationship: a connection between two or more variables
- Comparison: compare two or more variables side by side
- Composition: breaking data into separate components
- Distribution: range and grouping of values within data
Dashboard Design: What Else to Consider
Choosing the right visualization is key to making sure your end-users understand what they’re looking at, but that’s not all you should consider. When thinking about how to design a dashboard, you need to also take into account who will be the end-user of the dashboard in the first place.
For example, when designing a dashboard for an end user-focused on ad platform optimization, you probably want to focus your widgets on metrics that will increase conversion rates. Because your end-user is in the thick of what goes on with every ad on a day-to-day level, looking at the nitty-gritty measures such as CPM (cost per mille) makes a lot of sense. However, a VP of Marketing probably just wants to see, at first glance, the more broad strokes on how ad performance changes leads brought in.
To that end, as we mentioned earlier, before diving headfirst into dashboard design, sit with your end-users in order to gather requirements, and define KPIs. Without doing that, you can design the most beautiful dashboard in the world, but it won’t change the way users make decisions in the long run.
What are your experiences with dashboard design?
Can you help me with pros and cons?
A good [removed] design is one that: