Review of Edward Tufte's Presenting Data and Information course

First, let me set the stage. I’ve been reading stumbling across interesting data information articles by Edward Tufte for years now, have been interested in getting his booksimage for a while now, and was excited when my manager offered to send me to his one day course, and am quite grateful to have had the opportunity to go. So, I definitely went into this with good expectations.

30 Second Summary:

The first two thirds were not bad. The second two thirds sucked. The type of people who would appreciate this course the most are ones akin to the woman in front of me who wore red velvet pants, a scarf that probably cost $60 and from the Museum of Fine arts, dangly earrings of semi-precious stones, and, were you to talk to her, would be sure to let you know that she’s “an artist.” She loved it. You, on the other hand, should buy his books and skip the course.

[Update] Actually, skip buying his books, unless you really want them. Everything you wish was in his course can be found in The Back of the Napkin: Solving Problems and Selling Ideas with Pictures. I simply can not recommend that book highly enough to people wanting a practical guide to the visual presentation of data.


The first two hours were pretty informative, and essentially all of my notes that didn’t involve expletives came from that portion of the talk. But, there were two quotes (taken completely out of context here) that pretty much summed up his course

“…I prefer text.” and “Well this is all very interesting but…”

After the first intermission Edward made sure to let everyone know about his wonderful four hundred year old books by by Euclid and Gallileo which he held aloft, and flipped the pages of with his oily ungloved hands, thus guaranteeing they will not survive the next four hundred years as they have the last. He even made sure to carry it down a couple of aisles and show it to the people on the end, whilst frustrating and / or boring the other 95% of the audience.

After lunch he talked about visual interfaces which was comprised almost entirely of him telling you how cool his iPhone was. According to Mr. Tufte the only major thing that Apple got wrong with the iPhone was using icons on the main interface instead of text. Just imagine how many more items you could fit on that screen if it used text instead of icons! Oh the joy of having to read through text lists to find the fucking calendar app instead of just poking a fingertip sized picture of a calendar. Gallileo was so cool. Did you see this section of my book by Gallileo? To be fair he pointed out some valid ways they could improve the weather and stock apps.

Much time was spent making fun of PowerPoint, “bullet grunts”, and “chartoonists”. A grand total of zero minutes were spent discussing the pros or cons of any standard graphing technique: bar graphs, line graphs, area graphs, pie charts, scatter plots, etc.. Zero minutes were spent discussing what graphing techniques were best suited for what kinds of data (unless you count the 3 minutes spent on vertical scaling of graphs). Did you see the picture of Gallileo? There aren’t many pictures of him but I have an etching of him in my 400 year old book right here.

In between jabs at PowerPoint he discussed his technique for speeding up time in meetings, which is to start out with a “massive data dump” (giving the participants stuff to read before you talk), and then to ask if there are any questions. He guarantees this will make your meetings at least 30% faster. I guarantee that if you ever try that with a potential customer you won’t make the sale. He repeatedly used this technique on the audience by saying “now turn to page x in my book titled y” and waiting silently until everyone in the audience had read the whole page. Oh have you seen my book by Euclid?

He repeatedly advised people to clarify confusing data by adding more detail. While there are a handful of situations where this may actually be good advice it’s incredibly bad advice to give to an audience without clarifying when, why, and how to do so, which, of course, he never did. I will note that I found at least one good example of this technique while flipping through his books. The iPhone is so cool, but AT&T’s Edge network is the reason it isn’t cooler.

Edward also seems to be laboring under the mistaken impression that people actually want to understand all of the details of all the data you’re presenting to them. It is my experience, and many concur with me, that most people want to be shown the high-level “bullet grunts” of whatever data you have so that they can have a clue what the hell they’re looking at. Only then do they actually want nitty-gritty details, and usually they want the details on just a subset of the information. Aren’t Gallileo’s etchings of these sun-spots wonderfully detailed?

Documentation. All(?) graphs need documentation. The names of everyone who contributed to them should be present in big bold letters just like Gallileo did in this really old book. He even put his picture in it. Isn’t Gallileo cool? Also, descriptions: lots of descriptions, and annotations, and annotated descriptions, It’s fine if it the text required to describe the graph requires the same, or more, space than the graph itself. One of the techniques that he mentioned multiple times for making data more approachable was using annotations, which is great if your data isn’t going to change the next time the person looks at it (any stats on constantly changing things), but doesn’t seem to grasp how incredibly difficult it is to write software that can intelligently find a point to annotate that is either interesting or indicates some causality, never-mind trying to write software that will generate useful text about it. As an example, check out the Google Trends for “git”. When this was written only one of the annotated points had any causal effect on the data that’s being graphed (the one about Git software being released).

Resolution. He makes a really big deal about resolution. He applies it to media (screens, paper, etc.), as well as the resolution of information in a graph. He makes a lot of valid points about resolution, then talks about how some typographers designed their fonts at a resolution of two thousand grid lines per inch, and how his “Sparklines” have “two significant digits of resolution”. But he utterly fails to grasp that there is a point at which adding resolution is useless. In print his Sparklines may very well be precise to within a hundredth of an inch, but no fucking reader can tell the difference.

Imagine a typical ruler with precision down to a sixteenth of an inch. Now put ten times as many tick marks in each inch and you’re roughly at one half the resolution of print on good paper. Even at half the resolution of print you’re still going to have a really hard time telling the difference between 23/160ths of an inch and 21/160ths. But, after telling you how amazingly high the data resolution is in his Sparklines he proceeds to tell you it’s not enough and that he’s started work on displaying information in “High-def” Which bewilders the mind when you consider that you’re very lucky if your “High Def” screen is one third of the resolution of paper. Have you seen the resolution in this etching of Gallileo’s sun-spots? By giving the iPhone a higher resolution screen they more than doubled the amount of information they could fit on it relative to a normal phone! If only Gallileo had of had an iPhone…

Throughout the presentation I arrived at the following conclusions (potentially wrong) about Edward Tufte.

  • He has great distain for software developers.
  • He has no clue about the problems involved in displaying dynamic data.
  • He has no clue about how to run a presentation.
  • He has no clue why software works the way it does and berates it for not working the way he thinks it should.

BUT It didn’t all suck. As I said there were a number of good points in the first two hours, and all attendees got a box with all four of his books in it. You will need these if you attend the course because a third of the time he’s referring to pages in them like a typical college professor, and the other two thirds of the time you’ll need them to entertain yourself while he tells you about his four hundred year old books and his iPhone. I’ve read a few articles that went into one of them and I’ve skimmed through the rest and I do think they’re actually worth the cover price. He makes a lot of good points in the books and has a lot of good examples, although I don’t think that all of his suggestions actually play out in the real world.

Notes from the course (in case anyone cares):

  • Focus on causality when presenting information.
  • Data visualizations should be content driven not method driven.
  • Strive to invoke content responses / questions in your users.
  • Data should tell a story
  • Provide a context for the data.
  • Annotations: choose a point, explain it, then tie tangentially related facts to that explanation (not sure I agree with that last part)
  • Try and make the “smallest effective difference” when trying to emphasize some point.
  • Order data by the most important aspect, not alphabetically.
  • Find a way to connect your data to your users on a personal level (for example when dealing with data on neighborhood fires plot it on a satellite image of the town so that your users can find their house and thus connect to it personally).
  • Try to eliminate legends. You don’t want your users to have to look up details of your graph. It should all be integrated. For example if you’ve got a line graphing Bananna sales put “Bananna” on the line.
  • Keep related items adjacent in space.
  • It’s easiest to see variations in a slope when it is roughly at a 45 degree angle.
  • Make comparisons.
  • Attempt to overcome recency bias.

Also, some paraphrased questions to ask when consuming presentations:

  1. What’s their story?
  2. Can I believe them?
  3. What is the “domain specification” of this presentation.
  4. What do I want to see? Is that what I was shown?

Some questions to answer when presenting information:

  1. What is the problem I’m addressing?
  2. Who is it relevant to, and why?
  3. What is the solution I am presenting?

Mr. Tufte, if you’re reading this, I appreciate and respect the work you have done, but you need some serious lessons on how to give a course. I’d recommend spending some of the millions people have given you for these courses on some private lessons with Tony Robbins. Whether or not you agree with what he has to say it’s hard to deny that that man knows how to convey lots of useful techniques to his audience in a way that is both memorable and entertaining.

P.S. Gallileo did, in fact, rock. However, if I wanted to see a historically significant book I’d go to the museum or the library (Boston happens to have a kick-ass library with regular, and free, exhibitions). The iPhone also rocks, and is a triumph of interface design, but if I wanted to see a video of someone using it I would go to