The 10/20/30 Rule for Presentations: A Comprehensive Guide
Trace Guy Kawasaki’s venture-pitch heuristic, understand the problem each number addresses, and learn when the context calls for adaptation.
By htmlslides EditorialReviewed
From reading to making
Build the presentation your audience actually needs.
Create the HTML with your preferred AI coding agent or by hand, then sign in and import the finished HTML into htmlslides for playback and sharing.
Create with htmlslidesBottom line
The 10/20/30 rule is Guy Kawasaki’s heuristic for a venture-capital pitch: about ten slides, delivered in twenty minutes, using text no smaller than thirty points. It is useful as a pressure test against bloated pitches, not a universal law for lessons, technical talks, board reviews, or accessible documents. Preserve its intent—focus, brevity, legibility—while adapting the numbers to audience, venue, evidence, and purpose.
Where the rule came from
Kawasaki’s original 10/20/30 explanation proposes ten topics for a venture pitch: problem, solution, business model, underlying advantage, marketing and sales, competition, team, projections and milestones, status and timeline, and summary with call to action. He argues that presenters should plan for interruptions and technical setup rather than fill an hour.
That context matters. A ten-slide investor conversation is not the same artifact as a safety training, academic defense, courtroom demonstrative, or asynchronous report. Treat the list as one experienced investor’s framing, not evidence that every effective presentation has exactly ten pages.
What “10 slides” is trying to solve
A small slide budget forces prioritization. It discourages repetitive market claims and long product tours. To use it well, write the audience decision and identify the minimum evidence needed. Combine adjacent ideas only when the relationship becomes clearer; do not compress three unreadable tables onto one slide merely to hit ten.
Keep detailed assumptions, technical architecture, cohort data, and citations in an appendix. A concise main narrative is credible when it can answer questions with evidence, not when complexity has been hidden.
What “20 minutes” is trying to solve
Finishing early preserves time for questions, disagreement, and next steps. Rehearse with realistic interruptions and handoffs. Allocate time by importance rather than giving every slide two minutes. A live demo needs a buffer and a recorded fallback.
For a scheduled twenty-minute slot, the spoken portion may need to be shorter. Confirm whether introductions and questions are inside the allocation. Do not speed-read a script to satisfy the clock; reduce the argument.
What “30-point type” is trying to solve
Large text improves distance readability and exposes overstuffed writing. But a point value does not map consistently across software, fonts, screens, and rooms. Test the actual display from the farthest expected seat. Data labels and source notes still need to be legible, even when they are visually secondary.
The W3C presentation guidance recommends clear language, adequate contrast, descriptions, captions, and accessible materials. Font size alone cannot make a slide accessible. Reading order, color use, media alternatives, and delivery also matter.
When to adapt the rule
A five-minute product update may need three slides. A doctoral defense may require more than ten because the audience must inspect method and evidence. A workshop uses activities rather than a single linear pitch. An asynchronous deck needs more self-contained explanation. An accessible handout may use a different layout from the projected version.
Keep the rule’s constraints as diagnostics: if the deck is long, explain why each section changes the decision; if the talk fills every minute, identify what happens when questions arise; if type is small, decide whether detail belongs in an appendix or companion document.
Applying it to HTML slides
Use responsive type and layout, but set tested bounds so a narrow viewport does not shrink critical content. Add speaker notes and a print stylesheet. Keep interactions optional and provide a stable PDF. Avoid using scroll or animation to smuggle multiple dense “slides” into one counted page.
If importing into htmlslides, sign in first and verify sharing permissions afterward. Rehearse the hosted and offline paths. The browser format changes production options, not the audience’s attention limit.
A practical checklist
Write the decision, draft ten claim titles, attach evidence, move detail to appendix, rehearse under time, test from the back of the room, and invite a skeptical reviewer. If the result needs twelve slides or twenty-four minutes for a defensible reason, use them. The rule succeeds when it improves judgment and clarity—not when the arithmetic is perfect.