Someone sends me a deck for review, and within the first few slides I can usually tell whether they've heard of the 10/20/30 rule. Not because they followed it — because they're apologizing for not following it. "I know it should be ten slides, but…" That reflex is worth examining, because the rule has become one of those pieces of advice people repeat without checking whether it applies to what's actually in front of them.

What the rule actually says

Guy Kawasaki proposed it years ago, aimed mostly at investor pitches: no more than ten slides, no more than twenty minutes of talking, no font smaller than thirty points. It's a constraint set, not a design philosophy — three numbers meant to force discipline onto founders who wanted to explain everything they'd ever thought about their business in one sitting.

That context matters more than most summaries give it credit for. The rule wasn't written for a technical review, a board update, or a training session. It was written for a specific, high-stakes, time-boxed pitch scenario. Stripped of that context, it turns into generic advice — and generic advice applied to the wrong situation is where decks start going wrong.

Where it genuinely earns its reputation

In my experience, the part of the rule that survives contact with real work is the font-size constraint, not the slide count. Thirty-point type is a forcing function: you physically cannot cram a paragraph onto a slide at that size, so you're pushed toward one idea per slide almost by accident. I've watched people "fix" a cluttered slide simply by increasing the font until the excess text stopped fitting — the editing happened as a side effect of the constraint, not because anyone consciously decided to cut.

The twenty-minute cap holds up too, though for a less obvious reason than "attention spans are short." Twenty minutes is roughly the length before a room's energy shifts from listening to waiting for questions. I wouldn't recommend treating that number as sacred, but as a rough ceiling for a single uninterrupted stretch of talking, it's a reasonable rule of thumb.

Where ten slides stops being useful

The slide count is the part that causes the most damage when applied literally, and it's worth being specific about when.

  • Data-heavy or regulated content. A hypothetical clinical-trial update or a compliance review often needs enough slides to show the underlying evidence, not just the conclusion. Compressing that into ten slides doesn't make the presentation sharper — it just moves the missing detail into an appendix nobody reads during the meeting, or worse, off the deck entirely.
  • Technical audiences. Engineers, analysts, and domain specialists frequently want to see the mechanism, not just the headline. A ten-slide architecture review for a hypothetical infrastructure migration will get interrupted by "wait, go back" the moment it skips a step the room actually needed.
  • Long-format internal updates. A quarterly business review covering multiple departments has multiple audiences in the same room, each caring about a different section. Ten slides forces you to either shortchange half the room or split the content — at which point you've built two decks anyway, so the constraint hasn't saved any effort, just relabeled it.

One thing people overlook: the rule was never really about the number ten. It was about resisting the urge to explain everything. You can honor that intent with fifteen slides just as easily as with ten — the count is a symptom of discipline, not the source of it.

A version of the rule that survives more situations

What I'd actually recommend is treating the three numbers as starting constraints you're allowed to break, provided you can justify why. In practice that looks like:

  • Set a font-size floor for your specific audience and room — thirty points if you're presenting to a group across a conference table, smaller if it's a screen-share with a handful of people who can zoom in. The point isn't the number thirty; it's picking a floor and sticking to it so text-cramming has nowhere to hide.
  • Budget your talking time in minutes, then let the slide count follow from that — not the other way around. If a section genuinely needs four slides to land, four slides costs you less than one overloaded slide that takes three times as long to explain out loud.
  • Reserve a hard ten-slide cap for the specific scenario Kawasaki was addressing: a pitch where you're asking for a decision from people meeting you for the first time. That's the environment the rule was built for, and it's still close to ideal there.

I wouldn't recommend defending a slide count to a stakeholder by citing the rule itself. "It should be ten slides because Kawasaki said so" doesn't hold up against "the reviewer needs to see the risk data before they'll approve this." Rules borrowed from a different context lose their authority the moment someone asks why they apply here.

The trade-off nobody mentions

Following the rule strictly trades completeness for pace. That's a fair trade when the goal is momentum — get the room excited, get a yes, move to the next conversation where detail can follow. It's a bad trade when the goal is scrutiny — when the audience's job is to poke holes, verify numbers, or sign off on something they'll be accountable for later. Matching the trade-off to the actual goal of the meeting is the part most summaries of the rule skip entirely, and it's usually the difference between a deck that works and one that just looks disciplined.

Before your next deck, the more useful question isn't "does this follow 10/20/30" — it's "what is this audience in the room to do, and does my slide count help or fight against that?"