If you’ve seen me present in the last 3 years, you’ll probably have seen me show the Iraq Bloody Toll chart. Then you’ve seen me turn it upside down to create an entirely different message (full post here).
I still love showing this example to new audiences. I love seeing the light bulb go off as they realise that a data and a chart is just a method of communicating a message: facts are not neutral.
But it’s time to find a new example and for that I turn to you for help.
Have you got any other great examples of charts where the message can be transformed in as simple a way as this one?
(Note: I’m only looking for examples that stay true to good practice. Truncating the y-axis doesn’t count!)
How do you communicate what the dots, marks, and lines on your chart show? Most often, you’ll use a legend. They work well, but check out the this from the Huffington Post. They created a Paragraph Legend (as I’m going to call it).
Why’s this great? I mocked up what this might look like if we used a regular legend. Try and decipher the chart using the “traditional” approach:
In order to decipher the chart you need to read the paragraph. Then the chart. Then go to the legend. Then back to the paragraph. Then back to the chart. Finally you might understand what’s on show.
Now look at the Paragraph Legend. Read the paragraph, look at the chart, and then maybe back to the paragraph once more. I found it much much easier to decode the chart with the Paragraph Legend. Like all small things, this is harder for the designer, but an improved experience for the audience.
[This is the second time I’ve reused Andy Kirk’s amazing idea to blog short posts on great things they see in dataviz. All credit goes to Andy for the idea. I’m going to call my series “It’s the small things….”]
A perennial problem with filters: how do you make your users aware they are there ? How do you wrench their eyes away from the marks and headers and over to the filters on the right?
To fix this, I stumbled across another potential method: replace the Column Headers with Filters. I say stumbled because I wasn’t consciously trying to solve the problem when I implemented it. It’s only afterwards that I realised what I’d done!
What’s the advantage of doing it this way?
People are looking at the top left of your chart, so they are more likely to register that they can filter the dimensions.
It’s a cleaner view. The top banner is freed to have just my dashboard title. The right hand side doesn’t have that unusual blank space beneath the filters.
To implement this, it was simply a case of floating the filters over the column headers. For a design aspect, I ensured they were the same width as the columns in the view itself. I also tweaked the colours to bring attention to the dropdown itself.
Tableau 9.2 was released this week, along with some amazing new features. One nice feature is “Match Mark Colour.” I believe it has all sorts of creative possibilities for your views. For example, above you can see I’ve got two labels on a bar chart. One shows the numbers, while the other, aligned left, shows the categories themselves, nicely using Tableau’s algorithm for matching useful colours.
How do you make the labelled chart above?
To make this labelled bar example, I created a dual axis bar chart, duplicating the SUM([Number]) measure, and synchronizing the axes.
Both measures were labelled. One Measure was labelled with [Colour], aligned to the left. The other was labelled with [Number], aligned to the right. Finally, right click on the [Colour] dimension on the Row shelf and untick “Show Header”
Simple! What other nice design tricks can you do with colour matching?
Stephen Few’s excellent book about dashboards: “Information Dashboard Design“. If you are just starting out in visual analytics, this is a must-read book. It’s balanced and sets out good principles which, once learned, can be adapted.
Iraq’s Bloody Toll. This is one of my favourite charts/dashboards of recent years. So simple and yet so effective.
Over the past month, I’ve deconstructed a dashboard I made for Tableau’s internal VizWhiz competition. Below is an attempt to quantify the Impact and Difficulty of each of the design choices I made. You can click on each one to go read the post describing the design choice:
If you’ve enjoyed these posts and want to continue reading my blog, please subscribe to my RSS feed or connect with me on Twitter (@acotgreave)
Why did I bother changing a dashboard that looked pretty fine in the first place? Why did I write 14 posts about this single dashboard?
Simple: I wanted to really think about the design choices and share the process of taking a perfectly functional dashboard and trying to make it into a thing of beauty.
Stepping back made me realise how many and what type of choices I make. Each choice has a highor low impact and is easy or hard. I quantified that in the viz above. As Michael Mixon pointed out in a comment, as we become experts we take this stuff for granted.
You are fighting for viewers’ attention with any visualization you produce. One of the few things you can guarantee they will look at and process is the main title. Therefore you better be 100% sure this is both:
Explains the chart or asks a question
Your title is your one chance to grab the reader and convince them it is worth focusing on. This is not a new lesson: Willard Brinton was talking about this 100 years ago:
Subtitles are just as important. Consider the titles on each view:
I’ve numbered them. This helps guide the user through the view. Sure, the left-to-right nature determines the flow but numbering the titles helps.
I bolded the pertinent data-related facts. I’m using the title to communicate the data itself.
I’ve also added contextual text. Notice the “All” in the second view title. If you filter down to a single year in the highlight table (you can do this in the interactive version), “All” changes to the relevant year: To learn how to make dynamic titles in Tableau,click here to see a post on The Information Lab’s blog.
Annotate marks to add context
Imagine I’d left the annotations off the charts. You can see the effect above. What are you left with? A chart with a really interesting trend that gives no clues as to what causes it. The viewer is left with their interest piqued but with no answer. This is a serious failure. Adding the annotations answers those initial questions.
My first iterations of this dashboard did not have any annotations. It was only when I got feedback from people that they pointed out the problem. That’s the importance of getting feedback!
Below is the annotated time series: it’s much more useful:
My final word on these annotations – I deliberately aligned the annotation arrows to be vertical to give them consistency
Tooltips – ALWAYS be customizing your tooltips
Followers of this blog will not be surprised that all the tooltips are customized. If you want to know more about the importance of tooltips, and techniques to use them in Tableau, check out this series of posts. Summary: ALWAYS customise your tooltips; it is the easiest way to improve your dashboard.
Finally, don’t forget to turn off the command buttons: these are great for exploration in Tableau but a distraction for end users.
I’ve only considered a tiny set of considerations when using text in your visualizations. What else do you consider important for text on your visualizations?
Come back tomorrow for the final post in the Tableau Design Month series – a big wrap up of everything I’ve covered.
For this post, one of a series supporting Tableau Design Month, I’ll explain the colour choices made in design the dashboard above. There are three points I will highlight in this post:
Simplify the colour scheme as much as you can
Choose a colour that relates to your topic
Soften the darker tones
Simplify the colour scheme
Let’s see what Tableau’s default colour scheme would have been:
Tableau, or any visualisation tool, cannot know what the purpose of your vizualisation is. Therefore its choices should be appropriate to the chart being built. But in the above, the end result is overwhelming. There are colours everywhere.
It turns out that using just 2 colours: red and grey, you can tell the exact same story more clearly. You can even test your dashboard by trying it in greyscale: is the story still visible in the version below:
Choose a colour that represents your topic
I chose red to evoke the emotional aspect of this dataset. Red is powerful and emphasises the reality of fatalities. What if I’d have chosen a different colour? Blue, for example:
In this case the dashboard is much more neutral. It’s less provocative. It’s less opinionated.
Your colour choice should depend on your audience and your goal.
Soften the darker tones
You can choose palettes to emphasise just the parts of the data you want to. Tableau defaults to a perfectly serviceable green gradient palette.
My goal was to make the 3 most lethal seasons (Jan 1, Jul 4, Dec 25) pop out. A simple red palette didn’t do it so I tried red-black, but the black was too prominent. I settled on a red-white diverging as this really popped the days I wanted to focus on. All my choices can be seen below:
I went a lot further in this dashboard to soften the dark tones. For example, all the fonts are softened from black to a lighter grey. As I write this post, I’m unsure now whether that was a successful choice. Check out the image below. Which do you think is more successful – the dark font or the light font?
Colour isn’t easy. In this post I’ve covered just 3 choices. You also need to consider cultural implications, colour-blidness, publication type, and much much more. As always, I am very interested in your thoughts – let me know in the comments.
For my Design Month dashboard, I chose to go with a Menu action. I like the fact that when a user hovers their mouse over a mark, a nice customised tooltip with a call to action appears right where their eyes are looking.
I used a Menu action but a similar trick can be achieved with a Select action. Using a Select action gives you more control over the format of the Call to Action. I like this example from another recent Viz of the Day:
This technique is not perfect:
There isn’t a Hover equivalent on a mobile interface.
What if the user DOESN’T move their mouse over the viz?
Which actions do you prefer in your dashboards? What else do you consider when instructing people about interactivity?
When you design a chart, just how many borders and lines can you remove to maintain clarity? Do you improve clarity by removal?
Could I have gone any further? Sometimes I will hide the y-axis completely and just label the max value but I think that’s pushing it a little too far:
That’s what we’ll look at in this post. I’ll cover axis ranges and tick marks separately. In this post, I’m going to focus on what’s available from the formatting pane.
In the image above, you can see that my formatting approach is to reduce the lines as far as possible while retaining the meaning. Did I go too far? I think I got it about right.
Let’s look at how my end result compares with the defaults:
Default formats on the right, extreme reduction on the left. There’s nothing wrong with the defaults – the gridlines and borders are very sensible choices for a default setting. I do think I have emphasised the data more by reducing the lines.
Here’s how you can reduce the borders and grid lines in Tableau:
Remove all of the outer borders by selecting Format…Borders from the menu and then turning off all dividers at the sheet level:
I owe a hat-tip to Nelson Davis (@nelsondavis) for suggesting that it’s great to show only the horizontal grid lines in a view.
To achieve the effect, just go to the Format…Lines pane and set the Columns Grid Lines to None:
I like the end result, it’s very crisp. One bonus is that because there’s no border at the bottom, it makes it less likely someone will think the y-axes start at zero.