Presentation Zen — The Discipline of LessGarr Reynolds & the empty space that lets an idea land

There is a Japanese word, ma (間), for the space between things — the silence between notes, the sky between eaves, the breath between characters. Reynolds carries ma into slide design: emptiness is not "unfinished," it is "deliberate." It leads the eye, gives weight to the important, and leaves room for the audience's mind to do its own work. A crowded slide is something to be endured; a restrained slide is something to be approached.

The cognitive-science name is signal-to-noise ratio. Every element that doesn't serve the message — decorative border, company logo, page number, template background, "Confidential" watermark — is noise. Noise isn't zero; it's negative. It steals from your signal's already finite share of attention. Reynolds cites Edward Tufte's chartjunk — most of what "looks professional" is camouflage for thin content.

Same Q3 strategy. The left is a speaker's notes; the right is a speech. Projectionist vs. presenter.

• External talks, keynotes, TED-style, all-hands, product launches
• Executive briefings — one clean core slide beats twenty pages (decision-makers hate noise)
• Skip for "slideuments" — decks meant to be both spoken and read alone. Split them in two: a presentation version (sparse) and a reading version (full)
• Use with care for deep technical reviews — they need specs, data, interfaces; restraint is not the priority

• Equating "empty" with "large font" — large but full is still noise
• Last-minute stuffing — afraid of looking "empty," you cram a logo, a page number, a divider line
• Template ornament as "design" — template aesthetics are average aesthetics, not your content's aesthetics
• Filling the emptiness with animations — animation is noise's fancier sibling
• Pasting the script into bullets — when the audience is reading, they aren't listening; when they're listening, they aren't reading

Garr Reynolds, Presentation Zen, ch. 4 — Crafting the Story / Simplicity · Edward Tufte, The Visual Display of Quantitative Information — chartjunk

Non-designers don't design with taste; they design with rules. Robin Williams (the designer, not the actor) gave us four — Contrast, Repetition, Alignment, Proximity — in The Non-Designer's Design Book. Reynolds carried them straight into Presentation Zen as an actionable checklist. Any slide that violates one of the four will "look unprofessional," and the audience won't be able to say why — but they will know.

First, signal-to-noise made concrete. Three decks with the same information, three different fates:

Then the CRAP checklist — walk every slide through it, line by line:

• Any deck that must "look professional" — fundraising, board, customer, public relations
• Designing a team template — CRAP as the review standard means new hires can't go wrong
• Skip for: whiteboard sessions, ad-hoc sketches — over-polish on a temporary surface looks affected
• Use with care in highly formal legal or compliance settings — follow the existing template rather than chase beauty

• Trusting the default template — default is "average," not "right"
• More than three colors — one brand color, one accent, one neutral. That's it
• More than two fonts — one serif, one sans-serif. No calligraphy, no WordArt
• Aligning by eye — use the software's alignment tools or a grid; don't trust the eyeball
• Every slide trying to be unique — consistency outranks per-slide "creativity"

Robin Williams, The Non-Designer's Design Book — origin of CRAP · Garr Reynolds, Presentation Zen Design — applies CRAP to slides

The brain processes images vastly faster than text — the often-cited figure is 60,000×. Reynolds's central claim is the Picture Superiority Effect: memory for image + text is roughly six times memory for text alone. So: one slide, one idea, one image. The image is not decoration; the image is the argument. The remaining text shrinks to a small label, a number, a quotation — a footnote to the image, not a substitute for it.

Reynolds sorts slide images into three kinds, with three different jobs:

• Symbolic — anchors an abstract concept in a single picture. A close-up of a cracked bowl for "broken trust" lands a thousand times harder than "trust erosion 28%."
• Evidential — charts and comparisons. One rule: let the data speak, and delete everything that isn't data (borders, shadows, redundant labels). Tufte's data-ink ratio.
• Narrative — a single photograph carrying a person or a scene; the visual embodiment of story. Jobs introducing the iPhone wasn't a demo table; it was a black background with one clean product shot.

Three iron rules for any image: (1) always full bleed (edge to edge — floating islands look amateur); (2) always high resolution — better none than blurry; (3) never use PowerPoint's built-in clip art or stock-photo libraries — they are the visual clichés of "looking like a presentation."

• Kickoffs, product launches, TED talks, brand storytelling, customer meet-ups — anywhere emotion comes first
• Executive meetings — decision-makers remember pictures far more often than they remember numbers
• Multi-language audiences — images travel through translation losses
• Skip for: audits, compliance, technical RFCs — evidentiary completeness outranks impact
• Use with care — a wrong image is harder to retract than a wrong sentence (culture, sensitivity, stereotype)

• Stock-photo clichés — businesspeople shaking hands, city skylines, applauding teams. Audiences have stopped seeing these
• Decorative images — picture unrelated to claim, "just to fill the page"
• Four to six thumbnails on one slide — dilutes the signal; equivalent to none
• Image at too low a resolution — pixelated on the projector is worse than no image
• Keeping every chart default — 3D + shadows + grid — data-ink drops to 30%

Garr Reynolds, Presentation Zen Design, ch. 3 — Working with Images · Nancy Duarte, Slide:ology — the grammar of visual storytelling

Guy Kawasaki — Apple's former chief evangelist, then a well-known investor — sat through more than a thousand startup pitches before writing the 10/20/30 rule in a 2005 blog post: no more than ten slides, no more than twenty minutes, no font smaller than thirty points. All three numbers are hard constraints designed for the audience. Reynolds promoted the rule in Presentation Zen as the default lower bound for any business presentation. It is not an upper bound — it is the red line past which you are wasting the audience's life.

Every number has a physical reason:

• 10 slides — "7±2" is the canonical memory span; ten is the engineering cap including open and close. An investor deck doesn't need to be comprehensive, only to cover the seven decision points (Problem / Solution / Market / Product / Traction / Team / Ask)
• 20 minutes — the first marked decline in adult attention. Kawasaki's logic is fiercer: in a sixty-minute meeting, reserve forty minutes for real conversation — Q&A, challenge, co-creation. Twenty minutes is the opener, not the whole thing
• 30pt — a content auditor. At 30pt, you fit perhaps thirty to forty English characters on a slide. Bullet seas are physically impossible. The slide forces you to keep only the core. This third rule is the most engineered and the most effective

• Fundraising pitches, board updates, product launches, external brand talks, TED-style keynotes
• High-density executive meetings — 20 minutes of talk plus 40 minutes of discussion is the golden structure
• Skip for: training courses (must be long and complete), deep technical reviews (need code and spec)
• Use with care for cross-timezone async — those situations want a written document (Amazon's 6-pager), not a meeting

• One deck for both speaking and reading — neither works. Split it into a talk version and a reading version
• Ten slides crammed with eighty bullets — page count obeyed, spirit violated
• "I can't fit twenty minutes, so I'll add more pages" — not finding the core, not lacking pages
• Small font as preservation — "I can't bear to cut" disguised as necessity
• Treating 10/20/30 as an aesthetic rather than an engineering rule — it is a hard constraint; enforce it like one

Guy Kawasaki, The Art of the Start 2.0, ch. 4 — Pitching · Garr Reynolds, Presentation Zen, ch. 2 — Preparation