Dashboards tell us about critical business or operational metrics. Key features include:
“Dashboards are not an appropriate venue for artistic impression.” -- Stephen Few
There are three major types of dashboards we will cover today:
These different dashboards fit the differing needs of an organization.
Operational dashboards provide “day-to-day” data that assist line employees in making decisions. They tend to be specific to the nature of the user.
Operational dashboards drive action by informing that a process may be “out of control” and helping operators find the cause.
Strategic dashboards focus on KPIs tracked periodically and displayed at an aggregated level.
Tactical dashboards show strategic data at an almost-operational level.
We can intuitively see that this is not a good dashboard, but we might not be able to explain all the reasons why. The rest of this session will give us the tools we need to understand why this is not a good dashboard.
A great dashboard evokes one of two emotions from your intended audience: happiness or anger.
If a dashboard evokes neither emotion in your intended audience, it isn't working.
Key factors in knowing your audience:
For each of these, we display different measures in different ways.
This dashboard is great for a line worker, but a board member likely won't care about operational metrics.
How will users make use of your dashboard? What actions do you want them to take as a result?
Your job as a dashboard creator is to provide relevant metrics in an easy-to-understand way, requiring the user to get relevant information as easily as possible in order to make good business decisions.
Critical considerations:
Are you showing the right measures in the right way? For a sales team dashboard, you want to include sales-centric measures like leads in different steps of the pipeline, likelihood of a contact making a purchase, and number of sales by person against a quota. You don't want to include measures like server uptime, net margin, or number of high-severity issues.
What cultural differences might matter?
The meanings of colors can differ between cultures. For example, in European and American culture, red typically has one of two major meanings: love and danger. In finance, we use red to indicate negative values (going back to danger).
By contrast, in China, red has historically indicated prosperity--people give gifts of money at weddings and during major holidays in small red envelopes.
In this section, we will look at six important visual principles:
Our working memory can hold approximately 3-7 items at one time. Think of this working memory like registers and our long-term memory like RAM: we move information out of long-term memory into working memory and (sometimes) vice versa.
Because of this, we want to look for ways to reduce mental load. Techniques include:
Remove unnecessary clutter.
After removing the clutter, notice how much easier this is to read.
Reduce your color usage. Keep color usage limited and consistent and ensure colors add value.
In this case, it's clear that the colors were not in fact helping anything.
I can now highlight a particular value with color, a pre-attentive attribute.
Color is also an associative property, meaning people tend to link similar things with the same color together. If you break that pattern, you can confuse people.
Humans have trouble with precise 3D measurements. In rare cases, a 3D image is better than a 2D equivalent, but that is never the case for bar or column charts. 3D "gloss" is also not helpful for getting your point across.
In European languages, we read left-to-right, top-to-bottom.
In European languages, we read left-to-right, top-to-bottom.
In ancient Asian languages (especially Chinese), we read top-to-bottom, right-to-left.
Color is also an associative property, meaning people tend to link similar things with the same color together. If you break that pattern, you can confuse people.
In modern Chinese, we read left-to-right, top-to-bottom.
In modern Japanese, we read left-to-right, top-to-bottom (except when we don't).
These layouts tend to work for evenly distributed, homogeneous data, things like newspaper articles which are text-heavy in content. For image-heavy dashboards, people follow a different principle: focal points.
The Rule of Thirds applies to images, but also to dashboards.
The strategic dashboard (sort of) follows the Rule of Thirds.
Glanceability is the idea that a human can, at a glance, gain important information from your dashboard. Things which help glanceability include:
The Badlands, as seen by drone:
The Badlands, with protanopia:
The Badlands, with deuteranopia:
The Badlands, with tritanopia:
Remember the old SSIS?
SSIS 2008 with tritanopia:
SSIS 2008 with protanopia:
SSIS 2008 with deuteranopia:
Possible solutions:
SSIS 2008 with deuteranopia:
Great when users need to compare data directly. Tables and matrices generally don't belong on strategic dashboards, but do belong in tactical dashboards and sometimes operational dashboards.
Great when there are few categories but potentially many periods.
Great when there are few periods with many categories. Also good when labels are lengthy.
Choose a bar chart if:
Choose a column chart if:
Bar and column charts should start at the origin (0).
Named after Bill Cleveland, this is a minimalistic visual for comparing categories.
Dot plots are not native to Power BI, but there are a couple of custom visuals which give you dot plots. They can provide a lot of information in a very small amount of space, making them great accompaniments for tables or larger visuals.
My fondness of radar charts comes from playing Madden NFL in franchise mode.
Great for time series data stretching over many periods with non-cyclical data, but showing few categories. You can also use a column chart here, especially with only 2-3 categories
Risky chart, but works well with two inter-related but distinct variables. Often used with stock market levels and volumes.
For bar charts, we want to start at the origin. For line charts (and dot plots), we don't need to. Instead, Cleveland, McGill, & McGill proposed making the average line slope 45 degrees. This principle reduces the potential for confusion when viewing a line chart and is why it's fine to have the bottom of a line chart start above 0.
Power BI and Excel (as well as many data visualization tools) automatically do this for you.
Great for showing relationships between two variables over a relatively small number of categories.
Great for showing relationships between three variables, but as bubbles get larger, the image becomes harder to follow.
Risky chart, but great for showing the relative share of value for a medium to large number of hierarchical, categorical values.
The following charts are ones which have their uses, but I'm not particularly fond of them.
We will look at potentially good use cases, but also look at why I don't much like these charts.
Best use: simple share of a static total.
Best use: showing progress toward a target or as a percent full.
Gauges are okay, but they need to show progress toward a goal or provide an intuitive status.
Best use: showing relative and absolute differences of data which changes over time but has relatively few periods.
Looking at this again, what information can we know for sure? Just the top line and the bottom category.
Instead, you can show information more clearly with a line chart. The downside is that you'll have to calculate the total yourself if you want it to show.
Ribbon charts show rank changes but tend to be noisy and only useful when users can mouse over the data points.
Keep these tips in mind when creating a dashboard:
To learn more, go here:
https://CSmore.info/on/dashboards
And for help, contact me:
feasel@catallaxyservices.com | @feaselkl
Catallaxy Services consulting:
https://CSmore.info/on/contact