
Eariler this week, us first year students from PLW took a quick trip to New York to attend Edward Tufte’s workshop. The train ride into New York was plesant, but the ride back was a total disaster. Also, thanks to my good friend Jeff (happy birthday buddy!) for letting me crash at his place. Anyway, back to the workshop, here’s the trip report.
To Tufte or not to Tufte…
Trip Report for Tufte Trip, August 23, 2006. New York City.
Takashi Okamoto
Overall, I enjoyed the Ed Tufte workshop in New York. His talk was divided into two parts, pre-lunch and post-lunch sessions. The first half of the workshop was great. He explained in detail, the “Fundamental Principles of Analytical Design,” which breaks down to:
- Comparisons
- Causality, Mechanism, Structure, Explanation
- Multivariate Analysis
- Integration of Evidence
- Documentation
- Content Counts Most of All
He emphasized that “content” is most important; design won’t help if the content is weak (Principle 6.) So get better content! “Resolution” is the other key point, and he claimed that advances in science and our technical ability to achieve higher resolution is equivalent. Relating to higher resolution, he said everybody should work with two monitors in order to aid in comparison. So having two monitors is very important! Good thing John sets all of us up with a two monitor setup. Tufte says content needs to be dense, you shouldn’t cherry pick anything, and that the high resolution design will make that dense information more accessible. Cherry picking relates to something he emphasized over and over throughout the workshop. The main point to the workshop seemed to be about one thing: Content Integrity. As presenters of content, we need to make sure the content is credible, and not cherry picked to advance our own agenda; and as consumers of content, we need to make sure we question the validity of the content. He pushed this point over and over again.
In terms of technical instruction, the topic floated around Sparklines. Sparkline is “data-intense, design-simple, word-sized graphics,” which is a visual technique that can install high resolution information inline, within texts. I think Sparklines are useful, but only for two dimensional data, where one is temporal. His examples didn’t help much either, since he only talked about stock market data and sports scores, so I felt he made a huge deal about something you can explain in one sentence. He should have talked about links and causal arrows instead.
The second half of the talk was awful and there’s not much to say. He became preachy and cultish and went on and on about how bad powerpoint is. He basically blamed Microsoft for Columbia’s burn up in the atmosphere, because NASA engineers used a badly designed powerpoint presentation instead of writing a full technical report of the foam hitting the shuttle’s wing at lift off. It was so awful I wanted to walk out and curse at him for cherry picking (Kyle passed me a note pointing that out.)
One of my interest at the lab is to make information more accessible. With effective design (and interaction) you can make dense information accessible to a wider audience. Tufte’s workshop did shed new light into this, and I think once I finish reading all of his books, it would make me a better deliverer of information (and hopefully a non-biased credible one.) The lesson on good content is a relevant one for the whole group, especially for PLWire. I think whenever we post new content onto the site, we should make sure that the content is relevant and the viewers find it interesting and comprehendible.