Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Book Review: Presentation Patterns 27

MassDosage writes "In a remarkable show of good timing Presentation Patterns turned up on my desk for review within days of me having been asked to give a presentation at a large tech conference. So I decided to read the book as I worked on my presentation and apply any lessons learned as I worked my way through it. The word "patterns" in the book's title will be known to most software developers as a reference to the seminal 'Gang of four' software design patterns book which codified common solutions to software problems. The concept of patterns originated in building architecture with the idea being that by categorizing and naming solutions to problems, a common vocabulary could be built up that allowed practitioners in a certain field to communicate more effectively. This was hugely successful and has spawned the idea of looking for patterns in many other areas which is where this book comes in." Read on for the rest of Mass Dosage's review.
Presentation Patterns: Techniques for Crafting Better Presentations
author Neal Ford, Matthew McCollough, Nathaniel Schutta
pages 265
publisher Addison-Wesley
rating 7.5/10
reviewer Mass Dosage
ISBN 978-0-321-82080-8
summary Techniques for Crafting Better Presentations
Presentation Patterns aims to apply patterns to the task of creating and delivering presentations and for the most part it succeeds. The format of the book is slightly biased towards those in the software industry as the authors all have software backgrounds. However after reading the introduction which explains the rationale behind patterns in general, as well as the specifics of how they are covered, this book should be useful to anyone interested in improving their presentation skills. The book is divided into chapters which follow the timeline of creating a presentation — starting with patterns on preparing a presentation (e.g. "Know your audience" and "Narrative Arc) through to actually building a presentation (e.g. "Defy defaults" and "Infodeck") and ending with patterns related to the final delivery of the presentation (e.g. "Seeding satisfaction" and "Breathing room"). This temporal categorization of patterns is logical and worked very well for me as I could read through a section and apply it to the part of the presentation I was working on at the time before moving on to the next section.

Each pattern is described using a standard format which includes: other names for the pattern; a definition of the pattern; a motivation for why it is relevant; a discussion of where it is applicable as well as the consequences of using it; and a list of related patterns. Because each individual pattern is described in the same way it's easy to compare them and see why and how they should be applied. While patterns give advice on things that one should do, just as important is advice on what not not to do. The authors include plenty of this in the form of "antipatterns" which are described in the same way as patterns, the only difference being that they are things to avoid in a presentation, some examples being "Ant fonts" and "Disowning your topic".

Scattered throughout the book are anecdotes from the authors that describe real world situations where certain patterns were useful and some additional back stories to how they were discovered or applied. These add some welcome variety to the text while also showing that this isn't pure theory but has been derived out of the actual experiences of the authors (all of whom are regulars on the presentations circuit). Presentation Patterns can be read from beginning to end but after an initial read it will probably be even more useful as a reference — particularly by those who present regularly as they can look up information on a specific pattern that is of interest at a particular time.

While a lot of the patterns and antipatterns covered are fairly general and not tied to any particular technology, the authors do assume that most presentations will be created and delivered in a digital format. They try to avoid discussing any specific presentation software but in a few cases they go into more depth and describe how a certain technique would be implemented using Microsoft's Power Point and Apple's Keynote software. I'm a Libre Office user but fortunately most of their descriptions were easy enough to translate to another tool . Having said that, these cases are not the norm and if you are looking for a tutorial or manual on how to build presentations using a certain piece of presentation software then this book is not for you. I got the feeling that the authors were aiming for their advice to be timeless and have tried to describe generalities rather than the specifics of a particular tool.

Presentation Patterns is well written and contains lots of good advice, backed up by concrete examples from the authors' past experiences. A wide variety of patterns are covered and the breadth and the depth of these mean that there should be something relevant for most possible usages. Not every pattern is applicable to every type of presentation so it is up to the reader to understand when and where to apply specific patterns. For example, if your presentation is primarily going to be delivered by e-mail and read by people as opposed to you presenting it in person then certain patterns make more sense than others. The patterns are cross-referenced against each other so you can see how using one might influence the use of another. This is slightly annoying at the beginning when you are not familiar with all of them but as you expand your pattern vocabulary it starts to make a lot more sense.

I finished reading this book at around the same time I completed and then delivered my presentation and I definitely learnt some lessons that, when applied, made my presentation better than it would have been without them. At the end of the day most of the content is common sense and probably won't be that surprising to anyone who has given or viewed presentations in the past but it is still useful to have it all written down in one place. I will definitely use the book again, probably not to read it from cover to cover but more as a checklist and refresher of what to aim for and what to avoid when I work on my next presentation. The patterns format might not be for everyone and will take a bit of getting used to by those for whom it is new but on the whole I think it works very well for this material and would recommend it to anyone hoping to improve how they prepare, create, build and deliver presentations.

Full disclosure: I was given a copy of this book free of charge by the publisher for review purposes. They placed no restrictions on what I could say and left me to be as critical as I wanted so the above review is my own honest opinion.

You can purchase Presentation Patterns: Techniques for Crafting Better Presentations from Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.


This discussion has been archived. No new comments can be posted.

Book Review: Presentation Patterns

Comments Filter:
  • Antipattern #1 (Score:5, Insightful)

    by CarsonChittom ( 2025388 ) on Friday November 09, 2012 @04:51PM (#41935537) Homepage

    I'm sure this is a great book and all (actually, it does sound interesting), but seriously, if we could just stop people from making dense slides and then reading every single word off of them in a monotone, the quality of presentations worldwide would go up ninety gazillion percent.

    • Re:Antipattern #1 (Score:4, Insightful)

      by dkleinsc ( 563838 ) on Friday November 09, 2012 @05:16PM (#41935753) Homepage

      Another way of putting it: Your slides are not your presentation. Your slides are what's going on behind you while you give your presentation.

    • by damitr ( 1795258 )
      Edward Tufte in Cognitive Style of Powerpoint has a lot to say about slides their format and content and is against their indiscriminate uset. This is from a perspective of an information designer. [] "Alas, slideware often reduces the analytical quality of presentations. In particular, the popular PowerPoint templates (ready-made designs) usually weaken verbal and spatial reasoning, and almost always corrupt statistical analysis. What is the problem with PowerPoint?
    • I second that!
  • by Anonymous Coward

    Type: Presentation

    Problem: You want to warm up your audience.

    Context: Nobody in the audience has ever heard of you. While they are generously giving you the benefit of the doubt, privately the harbor misgivings about wasting time sitting through your speech

    Proposed Solution: Tell a joke that starts off sounding like a personal anecdote tied in to your present circumstances. For example: "On the flight over from Seattle, I was putting some finishing touches on my Power Point deck when I noticed the passen

  • by Seor Jojoba ( 519752 ) on Friday November 09, 2012 @05:02PM (#41935627) Homepage
    Thanks for writing the article. I would have liked it if some concrete examples of patterns were described in the review (like you did for "antipatterns"). That would help me judge if there was much insight offered by the book.
  • No, thanks . . . I'll just wait and watch for the presentation about it to come out . . .

  • You know because you can't have a incredibly amazing keynote without the sheer massive amounts of wonderfully delightful hyperbole. Also if there is not a presentation pattern that involves people in dark clothing in front of white backgrounds raving about the most mundane things then the book is utterly useless.

  • by Neil_Brown ( 1568845 ) on Friday November 09, 2012 @05:48PM (#41936119) Homepage

    by Carmine Gallo.

    I bought this a few years back — the , and thought it was a hugely helpful guide to improving the quality of my presentations. I speak on a reasonably regular basis, in all sorts of different places and before a range of different audiences (technical and legal, mostly, sometimes students) and this book gave me more than my money's worth in hints and tips. Nothing groundbreaking, but a good refresher — geared towards sales, but useful for pretty much anything. (Some presentation guidebooks suggest that all presentations are sales pitches, where you are selling an idea or a theme if not a product.) It reinforced that I was not crazy to aim to use slides to support what I was saying, and drive home my message, rather than me narrating a series of screens, nor mad to keep to fewer than five words a slide where possible, in the face of an increasing number of presentations which appear to have been dumps on documents onto slides — so far, this approach seems to get really rather good reactions from audiences.

    I found Craig Valentine's "World Class Speaking" rather turgid and disappointing, and I stopped reading about a third of the way through as a result. The style grated on me, and so others may find it more appealing.

    Scott Berkun's "Confessions of a Public Speaker" was interesting, and a fair insight into the life of someone for whom speaking was a living, but, in terms of improving my presentations and my approach, Gallo's book was better, in my opinion.

    With that being said, there's nothing better for learning than getting out there and doing it and trying different things, and trying to get some honest feedback from the audience afterwards.

  • by mspohr ( 589790 ) on Friday November 09, 2012 @06:02PM (#41936311)

    I found this book to be invaluable.
    It gives a simple plan to create presentations where you can get your point across in 7 minutes leaving 8 for Q and A.
    If your presentation is more complicated than that, you will lose your audience. []

  • Design patterns led to "programming by buzzword". And perhaps as bad, interviewing by buzzword, so people who could recite pattern names by rote would get hired. I suspect they also led to all the terrible syntax around iterators in the STL, but maybe that's just Stroustrup.

    Presentation patterns would likely screw up presentations the same way, except they're already screwed up. So maybe no loss.

    • Design patterns led to "programming by buzzword". And perhaps as bad, interviewing by buzzword, so people who could recite pattern names by rote would get hired.

      Although this may be OT, I do ask design patterns to my interviewees. However it's not like "tell me what a Visitor is", rather "you have this problem, how would you solve it?". The good ones come up with several solutions, some of which resemble (or exactly overlap with) a design pattern, and that's enough. If they are also aware of this, it's a bonus.

      Said that, the value of patterns is not just in using them (they originate from common sense after all) but also in creating a common ground for communicatio

news: gotcha