Starting from this week and during the rest of the semester I will be writing a new series called “Course Diary” where I report about my experience while teaching Information Visualization to my students at NYU. Teaching to them is a lot of fun. They often challenge me with questions and comments which force me to think more deeply about visualization. Here I’ll report about some of my experiences and reflections on the course.
Lecture slides for this class: http://bit.ly/infovis14-l2
In the second lecture of my course (the first was a broad introduction to infovis) I introduced basic charts: bar charts, line charts, scatter plots, and some of their variants. These basic charts give me the opportunity to talk about two important concepts: the relationship between data type and graph type (even though in a somewhat primitive way) and graphical perception.
In order to let students absorb graphical perception I spend a lot of time playing graphical trick rather than talking about theory (I’ll do that later on extensively). For instance, I show the “barless bar chart” a bar chart with dots in place of bars:
But I don’t limit myself to showing these are sub-optimal charts, I invite the students to think about why, and I’ve found this very nicely and naturally introduces broader and more relevant concepts. Let me explain with an example: a line chart without lines.
It’s easy to argue this does not work well. Especially when you show it paired with a proper line chart. But then you ask: why? Why it does not work as well as the version with lines? I’ve found that students have to stretch their mind and think much more deeply about the issue. Heck I have to think much more deeply myself!
For instance, I realized while discussing this example in class, that a line chart without lines is a very good example of why and when visualization works best: when data understanding is supported by perceptual rather than cognitive processes. A line chart without lines forces us to trace a line between the points. We desperately need that line! It’s not that we don’t use that line at all, it’s more than we draw it in our head rather than seeing it with our eyes. We can still judge the slope and detect patterns of course but it’s much much harder (slower/less accurate)! This simple concept can be applied everywhere in visualization. You get it here, with a simple time line, and you can re-apply it in a thousand different new cases.
Another example I have shown which spurred some interesting discussion is the “colorless divided bar chart”.
Once again, this one forces you to think more deeply about graphical perception. A divided bar chart with color is clearly better right? But why? Why is it better? Most students said there reason is because it’s easier to detect which bar is which: red to red, blue to blue, etc. And then I say: yes ok, but why? Why is color helping you here? After all each bar has its own position, and position is a pretty strong visual primitive to encode data (hint: it’s actually the best one). And then I explain that position here is overloaded, that is, it’s used to encode two things at the same time: the groups and the categories within each group and they get mixed up more easily without color. That’s when everyone nodded in class.
At some point I showed four different ways to display a time series (there are many more of course):
When I showed that, a couple of students raised some interesting questions. One was about the line chart vs. the area chart. The area chart looks pretty good, when is a good idea to use it? One students suggested the area chart has more contrast than the line chart and this made me think that area charts are probably very good when we have lots of them in a small multiple fashion as they they create a closed shape and as such are easier to compare.
By using this technique of starting from a basic chart and stripping it down of some fundamental design elements I have found I can teach a lot. I almost stumbled into this technique by chance but I think it’s very effective and I will use it over and over again in my course.
Besides dissecting charts, another recurring question I get in class is: how do we judge if a visualization is better than another? That’s a super hard question and I am glad I get it all the time. There’s not enough space here to articulate the answer but there is one thing I stress a lot in class: you cannot judge visualization without specifying a purpose.
I think everyone in this field has a tendency to judge visualizations in absolute terms, without considering their context (I have done that multiple times too). Too many believe data visualization is only about “data + visualization” (hence the name right?), forgetting that visualization with a purpose attached is impossible to judge. And again, basic charts, in all their simplicity, offer several opportunities to expose this concept: divided or stacked bar charts? area or line chart? multiple superimposed time lines or small multiples? There’s no absolute best here.
I have only one last comment from this lecture: Tableau is awesome. Coming up with examples and quickly tweaking them by adding and removing graphical properties saved me hours and hours of time. I was initially tempted to draw these examples on my whiteboard and take pictures, then I tried Tableau and it made me smile. A big smile. This makes me also think that Tableau other than being a great analytic and presentation tool can also be used as an excellent didactic tool.
That’s all for this week. Wish me luck for my next class!