Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Edward Tufte Talks information Design

Posted by samzenpus on Mon Aug 21, 2006 07:09 PM
from the good-design dept.
BoredStiff writes "The Weekend Edition of NPR ran a story on Edward Tufte — the outspoken critic of PowerPoint presentations — he has been described by The New York Times as "The Leonardo da Vinci of Data." Since 1993, thousands have attended his day-long seminars on Information Design. Tufte's most recent book is filled with hundreds of illustrations that demonstrate one concept: good design is timeless, while bad design can be a matter of life and death."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Read his books! (Score:5, Interesting)

    by BWJones (18351) * on Monday August 21 2006, @07:11PM (#15952175) Homepage Journal
    Tufte is absolutely one of the world experts on presentation of design. We have absolutely strived to adopt his principles of data design and presentation in almost all of our work and its paid off in terms of data interpretability. My dissertation work was presented for two years in a row at our big vision meeting getting no attention until I used some of Tufte's principles in presentation of data and the third year I had several hundred of the worlds scientists in vision research gasping, oooohing and aaaahing. It was awesome. Of course Keynote [apple.com] and a cool animation [utah.edu] of a degenerating retina helped, but still......

    His books are required reading in our lab and I encourage everyone who is involved in presentation of data of any kind to spend some time with his books.

      • Re:Hmm.... (Score:5, Informative)

        by Otter (3800) on Monday August 21 2006, @08:51PM (#15952655) Journal
        Tufte's reputation is usually boiled down here to "the world's foremost critic of PowerPoint" but that's hardly what he's about. He's a wizard at explaining how to present data more effectively, not just an unusually articulate "M$ teh sux!!!" nitwit.
      • by AlpineR (32307) <wagnerr@umich.edu> on Monday August 21 2006, @08:53PM (#15952664) Homepage
        I believe that Tufte's biggest gripe with Powerpoint is that it encourages low information density. If you use the default templates you will have just a few bullet points on each slide and lots of space lost to border embellishments. But if you know what you're doing, then you can put much higher information content into a presentation (especially when it's projected from a laptop, allowing animation). Even Tufte himself used transparencies and videos when I saw his seminar.
      • Re:Hmm.... (Score:5, Informative)

        by BWJones (18351) * on Monday August 21 2006, @09:11PM (#15952754) Homepage Journal
        Yes, I *am* saying that I used a presentation software package, yet in using that package, I kept the "chartjunk" to a minimum, used graphics effectively where appropriate and used simple data and clear presentation to deliver the message.

        This can be done with Powerpoint, Keynote and a variety of other packages. However, the problem with them is that people often use things like 3D graphs where inappropriate, fill up screens with lots of little text whereupon they say "don't read this, I just wanted to show......". Also the distracting use of transitions that flip and pop and such and cute little sounds that do nothing for the message except cloud it are common things that folks like Tufte and interestingly enough David Byrne have also commented on.

  • Wouldn't that describe pretty much every person who came across powerpoint and is not a manager?
    I did about 5 months of powerpoint stuff in the army (after which i was released for mental health reasons.. =\), and from my experience powerpoint has no use other than make managers and commanders feel important.
    • whilst I was a first year at uni all my lecturers put together power points and they were available online, it was brialliant compared to what we got last year; word documents. Word makes presentations to a standard so low you'd be shocked and bored more than you ever thought possible.

      Compaired to Word, power point is a feast for the eyes!
      • by OnanTheBarbarian (245959) on Monday August 21 2006, @07:51PM (#15952379)
        I think the standard Tufte line on this, is that if a 'few words' are all you're going to get up there, then why not just say the words and leave the screen blank?

        As a side bonus, you'll get eye contact from your audience rather than the disconcerting experience of looking out at a sea of faces who are all looking slightly to one side, peering at:

        - Standard Tufte line

            * high-data essential

        - Good to have eye contact ... or some low-information drivel like that.

        But on the whole I agree that PowerPoint isn't inherently evil if used as a way of doing a nice slide-show of reasonably detailed elements (graphs, pictures, movies). The only problem is that the resolution of projectors is still pretty wretched compared to printed graphs.
        • by Rakishi (759894) on Monday August 21 2006, @08:02PM (#15952429)
          I think the standard Tufte line on this, is that if a 'few words' are all you're going to get up there, then why not just say the words and leave the screen blank?

          Not everyone pays attention to the speaker all the time, never missing a single word or meaning.

          Also, pretty pictures keep people from deciding their text messages are worth more attention than your presentation or so a professor of mine says.
      • by The Great Pretender (975978) on Monday August 21 2006, @08:02PM (#15952430)
        As a veteran on massive data presentations (scientific), globally, to very different audiences, I concur with megaditto. Any presentation software is most effective when viewed as a direct replacement for the slide projector. No animations, no sounds. A few rules I live by:

        1) No matter what my company says, they get a white background presentation with a small logo in the bottom left corner of each slide. I refuse to use background templates of "company colors" 2) No crap on the borders. I can't stand the waste of space that borders use up. I would rather make my table 20% bigger than have a pretty pattern of lines off-setting the slide 3) Text titles no bigger than 36 font, text subject matter no smaller than 24 font 4) Preferably 1, if I must then 2 plots to a slide 5) No test describing the plots on the slide, I should be doing that 6) No bar charts! I hate bar charts 7) Bold primary colors, none of this 'earth shades' 8) Plots imported from a graphing package. I use Sigmaplot of Origin. Excel is the armpit of graphing.

        Bottomline is that if you have to use sounds and animations to capture the audiences attention, you're not doing a good job as a presenter, or the audience is just plain not interested in your subject (which happens).

  • by Anonymous Coward on Monday August 21 2006, @07:16PM (#15952196)
    Edward Tufte's site [edwardtufte.com].
  • by imaginaryelf (862886) on Monday August 21 2006, @07:21PM (#15952225)
    Gettysburg address in powerpoint: http://www.norvig.com/Gettysburg/ [norvig.com]
  • "If you're words aren't truthful, the finest optically letter spaced typography won't help," he says. "And if your images aren't on point, making them dance in color in three dimensions won't help."
    This is true, no doubt. However, it is helpful from the position of the viewer of the presentation more so than from the presenter. What I mean is this: many times people have to make presentations that
    1. Don't have anything to say and or
    2. Whose words aren't truthful
    For these people in either or both the above categories, PowerPoint can be a huge g-dsend, allowing them to execute a praise-generating (or, sales-generating) presentation that, had the person followed Tufte's advice, would have (rightfully) bombed.


    PowerPoint: stretching Truth and Content since 1997.

    People ready software, indeed. Lots of people have nothing to say or lie when they say it.

    Example: the Vista project manager giving a status report on features implemented, bugs solved and milestones met (this needs "filler") and projections for hitting delivery dates (this needs "less than truthful"). PowerPoint to the rescue!


    Seriously, though. In Tufte's world, those without something truthful to say simply would say nothing. I like that world. But, I live in the Internet Age and know that world, perfect as it is, does not exist.

  • Wikipedians (Score:5, Interesting)

    by mnemonic_ (164550) <jamec@@@umich...edu> on Monday August 21 2006, @07:29PM (#15952266) Homepage Journal
    Reading his thoughts on borders [edwardtufte.com] (scroll down) reminds one of a flaw of Wikipedia's HTML/CSS design. "Strong frames ... produce content-diminishing effects," says Tufte. I seldom see borders around tables or equations in textbooks, and it does look very clean. On the other hand, Wikipedia's CSS styles place borders and underlines superfluously about everything, from blocks of code, images and underneath headings. It seems the Wikipedia web designers try too much to make "pretty pages" when, to an academic eye they look ugly and cluttered.

    Every page element should signify some meaning; a heading should be underlined to distinguish it, but only if it is not otherwise distinguished by font size, vertical whitespace or some other typesetting. One element variation should suffice, as long as it's a bold change. A table should have borders only if the data are unclear otherwise. It's sad that as useful as Wikipedia can be, it still suffers from so many flaws [slashdot.org]. Wikipedians could learn much from Tufte, or from any study of technical communication.
  • Bad Design (Score:4, Insightful)

    by Simonetta (207550) on Monday August 21 2006, @07:37PM (#15952305)
    Bad design is giving a program an insufferablely cute name that does absolutely nothing to describe its function. Like "TWiki". At best, the name of the program should be a very short two word description of the program's function and at worst, a metaphor of the program's function. In the above example, "TWiki" should be called "GroupEditor" or at worst, "BullPen".
        But TWike like OggVorbis, is a ridiculous name that actually hurts the program by alienating people from exploring what it does after they see or hear the Program name referred to in some random context. Giving programs stupid names is a deep disfunction of the Linux/Open Source community. Seriously, we need to get over this.
    • by version5 (540999) <altovideo@h o t m a il.com> on Monday August 21 2006, @08:44PM (#15952625)
      "TWiki" should be called "GroupEditor" or at worst, "BullPen"...

      Wiki is a Hawaiian word meaning 'fast' or 'quick', so it does at least partly describe the function of the software. You might complain that not everyone is familiar with Hawaaian words, but then not everyone is familiar with baseball terminology from which you derived "BullPen". Open source software tends to have a very cross-cultural, cross-language audience. Do you suggest that projects rename themselves for each language they target? Projects are named for marketing purposes, to be memorable and appealing. It sounds very much like you just hate the idea of marketing, so I will rename you CrankyBastard, which I think we can all agree is memorable, appealing and accurately describes you!

    • Re:Bad Design (Score:5, Insightful)

      by waveclaw (43274) on Monday August 21 2006, @09:30PM (#15952858) Homepage Journal
      Bad design is giving a program an insufferablely cute name that does absolutely nothing to describe its function.

      Actually, Tuffte talkes about this very phenomina using terms familiar to anyone in design: affordances. Affordances are learned aspects of a particular domain. Affordances, as Tufte has touched upon in his design for information clairty are to be used, not avoided. Everyone had to learn what MP3 meant. Everyone had to learn how to read a chart (or, if they weren't a jock on a fast road to CEO at Daddy's firm, fail High School geometry.)

      For example, I am a big fan of functional naming. Instead of a variable named $CORNED_BEEF I would use $HASH_PIVOT. However, if you are an ESL like 95% of the world, it won't matter what you call your variables becuase the non-native aspect will always stand in the way. You will have to learn what those identifiers mean and then remember that.

      The same holds for software. The 'lingua franca' of Computer Science, hence much programming and software marketing, is English. The language of musical notation is Italian. From study I know what agitato and determinato are. But it does not help me that they are Italian for agitated and determined, respectfully, because I had to learn their definitions in English. If I spoke Italian I could have pulled the names for those musical styles out of thin air just listening to music. However, they are just words attached to those concepts for me, abstract labels and nothing more. However, I do not see any difference between this hundreds of year old phenomina and sotware naming.

      But TWike like OggVorbis, is a ridiculous name that actually hurts the program by alienating people from exploring what it does after they see or hear the Program name referred to in some random context.

      I don't think we'd get a lot of benefit if TWiki had been called VersionGroupwareType003.

      People hunting online for MP3s might dissagree. After all, MP3 just says 'music file' doesn't it? MP3 is a Motion-Picture Experts Group layer 3 file. Yes, I looked that up. I might think that has something to do with the movies, but music? Wiki means HTML TEXTAREA editor with special markup for you web browser. (Really the groupware aspect of Wikis is kinda of a dominating secondary effect.) Ogg Vorbis stands for Vorbis encoded audio inside an Ogg format container.

      This is far from the point thougt. Tufte's expertise is to spot on eliminate distracting garbage in a design. Powerpoint is very good at packing in garbage, hence his critisim of it. Simple, silly names are appripirate when differentiating. When they are clutter, like bullets points that take up 40% of the slide, names won't serve this purpose. For evern search.com there is a competitor not wanting to lose mindshare (or trademark infringement lawsuits) by having a very similar name. But pardon me, I have more google'ing to do before I can flesh out that point.
  • by OnanTheBarbarian (245959) on Monday August 21 2006, @07:39PM (#15952317)
    I imagine that many people will get on and post all sorts of breathless praise about Tufte. This is well deserved. His design sense is first-rate, but what's really impressive to me about him is his emphasis on intellectual honesty and detail.

    What I really would like to see is a new widget set (with lots of data presentation support - obviously most of the widgets should be quantitative displays) and a style written in some already well-supported widget set (Qt, Swing, ...) that lives up to Tufte's ideas about maximizing data ink and minimizing junk. While I really admire the effects that Tufte and some of his acolytes achieve, quite frequently it seems that they achieve these effects by painstaking work in drawing or desktop publishing packages. More than once, I wince at some bit of graphics or interface that I've designed, thinking, "Damn, that's an embarrassing bit of work for someone who has read Tufte, but I just don't have the time or skills to fix it..."

    This makes it a lot harder for schlubs like me who don't really have skills in this area, and don't have time to develop them. Further, it makes it more or less impossible to achieve these sort of fine effects programmatically - I'd like to see interactive displays that are informed by his sort of design sense, not just nice presentations (using hand-outs, of course :-) ), papers and books.

    If anyone is interested in this - or knows of systems that go any decent way in this direction - please post or e-mail me at:

    geoff AT cs DOT usyd DOOOOT edu DoT au

    (sorry about the stylized "dot" silliness, but something tells me that the traditional foo AT bar DOT com is probably already being mined by spammers - or will be soon).
    • While I think that you have a nugget of a good idea, I have my doubts that it's possible to make a software tool that encourages or enforces good design. Software can't legislate good taste, and a lack of good taste is the problem.

      Now for a crass generalization: techies always think that a problem can be solved with software and/or obsession. But sometimes, it takes actual skill to do good work. After all, programmers rarely hesitate to get pissy with some noob who works in Visual Basic, but they somehow think that art and design are skills that can be picked up from a book.

      If it's really important to you to have attractive visuals, then don't be an arrogant asshole, and hire someone to do the work. It doesn't have to be expensive (go to any art school, and you'll find dozens of young, eager artists and graphic designers looking for a break, and willing to work for reasonable rates), and it will go a long way to making you look more professional and polished.
      • Alright, you have a good point there, but to some extent you're attacking a straw-man. I don't imagine that a software library can magically make good visuals for me. Also, I never said that we'd get together a bunch of programmers (and only programmers) and make the perfect, beautiful widget set - obviously, designers need to help with individual components (and the overall layout if the overall layout can be determined ahead of time - see ahead).

        However, there are so many cases where there are existing cliches that could be improved. For example, Tufte has a brilliant redesign of a scatterplot that uses pretty much every bit of ink on the screen to convey useful data (for example, the X and Y axes become range bars that show the univariate distribution of data). This could be hacked once and for all into a TufteScatterplot widget. And so on.

        One of the major problems with the 'hire a graphic artist' approach is that frequently, we're dealing with systems that will display unanticipated data. I'm working with a statistical problem at the moment (and building some generalized tools to deal with it) and I have no way of knowing ahead of time whether someone is going to work with a model with 60 factors of which 5 are significant or 10 factors of which 7 are significant. I don't know what sort of names the person will give the factors. I don't know whether the significant factors will be all pretty much the same size (e.g. 1.5%, 2.2%, -1.3%) or hugely different (200%, -50%, 10%). When presenting 'significance' in a system, I can't have the system automatically call the nearest design school to handcraft a nice display. Thus, a system that makes a programmatic attempt at trying to achieve ideals of good design is much better than a system that doesn't even bother.

        Of course, anyone will be able to cobble together a rotten-looking, dishonest and confusing interface out of these kind of components. So what?

  • by Anonymous Coward on Monday August 21 2006, @09:08PM (#15952741)
    Here's a link to a long interview with Tufte.
    http://www.edwardtufte.com/tufte/s15427625tcq1304_ 5.pdf [edwardtufte.com]

    The interviewer asked him about why he self-published:
    "After moving to Yale University, I finished the manuscript in
    1982. A publisher was interested but planned to print only 2,000
    copies and to charge a very high price, contrary to my hopes for
    a wide readership. I also sought to design the book so as to make
    it self-exemplifying--that is, the physical object itself would
    reflect the intellectual principles advanced in the book. Publishers
    seemed appalled at the prospect that an author might
    govern design."

    So, here's a guy writing a book on how to present information and the publisher thinks he knows better. LOL. Naturally, Tufte chose to keep control of the process. In other words, we are to do as he does. (as opposed to do as he says.) This approach reminds me of a lecture our principal used to give. The lecture was on how to lecture. He gave seven different techniques. He delivered each technique by using that technique. This is what Tufte refers to as self-exemplifying. Our library doesn't know it yet but they are buying copies of his books. :-)
      • Re:HTML Design? (Score:4, Interesting)

        by moosesocks (264553) on Monday August 21 2006, @09:46PM (#15952923) Homepage
        It's not nearly as bad as Jakob Neilsen's site [useit.com].

        I'm using a 1680x1050 monitor, and I personally have no problem with Tufte's website. If you've got a huge high-resolution monitor, you're pretty foolish to be browsing with your windows maximised. With the window open to about 2/3 the width of the screen, the content fits perfectly.

        The absolute *worst* UI paradigm that has plagued the computing world for the past decade is the maximize button. Ever since multitasking was supported at the OS level, we've had the marvelous ability to work on more than one thing at a time. I don't spread every page of my newspaper out across the kitchen table when I read it. Why should I do the same for my web pages?

        Apple was smart to have left it out of OS X, and Microsoft should have left it out of Win95, or killed it with XP. For the first week, it's annoying to drag the corners of the windows around, until you realize how much more productive you can be by having two pieces of work side-by-side. Heck, even for single-tasking, multiple windows are great. If I'm writing a research paper on Shakespeare, I can have a copy of Hamlet open right alongside the paper for quick reference and easy quotations.

        Of course, those 14" 1600x1200 laptop screens *are* a problem, because they make text and images unbearably tiny. Apple's the first (mainstream) vendor to tackle this issue head-on, and the next version of OS X should be resolution-independent [tuaw.com], which should open the door for smaller, higher-resolution screens that won't kill our eyesight.