Short answer: A good presentation helps a specific audience understand a decision, remember the reason, and know what happens next. It has one clear through-line, a deliberate slide sequence, readable visuals, evidence matched to the claim, and a delivery plan that leaves room for questions.
The 10/20/30 rule is a useful pitching heuristic, not a universal law: about ten slides, twenty minutes, and no font smaller than thirty points. The stronger principle is to match content to the audience, the decision, and the time available.
Start with the Audience and the Decision
Before you choose a theme or write a title, complete this sentence: “After this presentation, this audience should be able to ___.” The blank should name an observable action such as approve a project, choose a vendor, understand a research finding, or practice a new process.
Record the audience’s starting knowledge, likely questions, available time, and decision rights. A board update, sales proposal, and classroom lesson may use the same visual tools, but not the same sequence or level of detail.
| Audience situation | What the deck must make clear |
|---|---|
| Decision meeting | The recommendation, evidence, trade-offs, owner, and decision needed. |
| Sales or pitch meeting | The buyer’s problem, your approach, proof, risk, and next step. |
| Research or report | The question, method, result, limitation, and implication. |
| Teaching or training | The learning goal, explanation, practice, and check for understanding. |
Build a Narrative Arc, Not a Stack of Topics
A presentation is easier to follow when each section answers the question created by the previous one:
- Context: What situation or audience problem matters?
- Question: What must the group decide or understand?
- Evidence: What facts, examples, or observations support the answer?
- Recommendation: What should happen and why?
- Action: Who does what next, by when, and how will progress be checked?
This structure does not require dramatic storytelling. It gives every slide a job. If a slide cannot answer “Why is this here?” or “What should the audience do with it?”, move it to the appendix or remove it.
Give Every Slide One Primary Job
Use a slide outline before writing full copy. This is a practical starting point for an eight-slide business update:
| Slide | Primary job | What to show |
|---|---|---|
| 1. Decision | Orient the room | The question, recommendation, or outcome in one sentence. |
| 2. Why now | Establish relevance | One change, risk, opportunity, or audience need. |
| 3. Evidence | Support the claim | The strongest chart, example, quote, or comparison. |
| 4. Diagnosis | Explain the pattern | Drivers, segments, assumptions, or constraints. |
| 5. Options | Make trade-offs visible | Two or three viable paths with comparable criteria. |
| 6. Recommendation | Choose a direction | The selected path and the reason it fits the goal. |
| 7. Plan | Make execution concrete | Milestones, owner, dependencies, and review signal. |
| 8. Ask | Close the loop | The decision or next action required from this audience. |
Longer presentations can add detail, practice, or an appendix. The principle remains the same: one primary job per slide, with the title carrying the point rather than merely naming the topic.
Choose a Slide Count That Fits the Task
There is no universal number of slides that makes a presentation good. Slide count is a constraint, not a quality score. Start with the available time, the audience's familiarity with the topic, the complexity of the evidence, and the decision the presentation must support.
Build the shortest sequence that completes the narrative arc. A five-minute update may need three to five focused slides; a technical review may need more evidence and appendix slides. Estimate how long each slide needs in rehearsal, then cut or split slides that force you to rush. Keep detailed backup material outside the main path so questions do not overload the core story.
Practical check: remove a slide and ask whether the audience can still understand the problem, evidence, recommendation, and next step. If yes, the slide may not belong in the main deck.
Use the 10/20/30 Rule Only When It Fits
The 10/20/30 rule is a useful pitching heuristic: roughly 10 slides, 20 minutes, and type no smaller than 30 points. It can encourage discipline, but it is not a general definition of presentation quality. A board update, workshop, lecture, and product demo have different evidence and interaction needs.
Use the rule when you need a simple constraint for a concise pitch. Adapt it when accessibility, required disclosures, audience questions, or technical detail demand a different format. Our dedicated guide explains how to apply the 10/20/30 rule without treating it as a rigid law.
Practical check: if meeting the rule makes you omit necessary evidence or shrink labels, prioritize comprehension and credibility instead.
Make the Visual Hierarchy Do the Work
- Use a sentence-style title that states the finding or decision.
- Give the primary evidence the largest visual area and reduce competing decoration.
- Use one accent color for emphasis and neutral colors for context.
- Align elements to a repeatable grid and keep spacing consistent.
- Prefer a chart, diagram, or short example when a paragraph would be hard to scan.
- Check contrast, font size, captions, and labels on the actual display or a realistic preview.
One visual does not mean one object. A slide can contain a chart and a short annotation when they answer the same question. It becomes noisy when each element argues for a different idea.
Match Evidence to the Claim
| Layer | Example wording | Required check |
|---|---|---|
| Observation | “The three largest segments account for most of the recorded requests.” | Confirm denominator, date range, and source. |
| Interpretation | “The pattern may indicate onboarding friction is concentrated in those segments.” | Show supporting segment or qualitative evidence. |
| Recommendation | “Test a revised setup guide with those segments next month.” | Name owner, test, signal, and review date. |
Label illustrative numbers, forecasts, estimates, and examples. A polished chart can make an unsupported claim feel certain, so the source note and limitation belong on the slide or in the speaker notes.
Plan the Delivery, Not Just the Slides
Rehearse transitions between ideas, not only the words on each slide. Prepare a one-sentence answer for likely objections and decide which evidence belongs in the appendix. Test the deck on the actual screen when possible.
During delivery, give the audience a moment to read a chart before explaining it. Do not read every visible sentence aloud. Pause after the recommendation and invite the question that will move the decision forward.
For a remote session, plan for smaller windows and participants who may not see fine labels. Provide a concise written follow-up with the source, decision, owner, and next review date.
Build and Review a Good Presentation Step by Step
A strong deck is produced through a visible chain of decisions. In Presenti's current workflow, you can describe a topic or provide source material, generate an editable first draft, and then edit and export it. The generated deck is a starting point; the presenter remains responsible for the argument, evidence, accessibility, and delivery.
Step 1: Write a one-sentence brief
Input: audience, purpose, time limit, and desired action.
Action: write: "After this presentation, [audience] should understand [idea] and decide or do [action]." Add the tone and any non-negotiable evidence.
Output: one brief that can guide every later choice. Check: two editors should interpret the desired outcome the same way.
Step 2: Collect and label the evidence
Input: research, internal data, customer examples, quotations, and required disclosures.
Action: place each source beside the claim it supports. Record the owner, date, unit, and URL or file location. Separate verified facts from assumptions and illustrative numbers.
Output: a small evidence set with provenance. Check: every important factual claim has a source that another reviewer can open.
Step 3: Build the narrative arc
Input: the brief and verified evidence.
Action: arrange the story as context, tension or problem, evidence, recommendation, and next step. Write one sentence for each section before creating slides.
Output: a logical outline. Check: reading only the section sentences should reveal why the recommendation follows from the evidence.
Step 4: Assign one job to every slide
Input: the outline.
Action: turn each necessary idea into a slide job, such as "establish the baseline," "compare the options," or "request approval." Write the headline as the takeaway rather than a topic label.
Output: a slide-by-slide plan. Check: merge or remove slides with duplicate jobs, and split slides that make two unrelated claims.
Step 5: Create the first editable draft
Input: the brief, outline, and source material.
Action: use the Presenti AI presentation maker to describe the topic, paste a source URL, or upload supported source material, then review the generated deck in the editor. For a prepared script or outline, start with the text-to-presentation workflow. Keep the generated structure only where it supports the brief.
Output: an editable visual draft. Check: compare every generated slide with the outline and source material; delete unsupported claims and generic filler.
Step 6: Review facts, charts, and accessibility
Input: the editable draft and evidence set.
Action: verify names, dates, calculations, units, citations, and chart mappings. Add alt text where supported, use sufficient contrast, avoid color-only meaning, and check that body text is readable at presentation size.
Output: a defensible deck. Check: a reviewer should be able to trace each key claim and read each chart without your narration.
Step 7: Rehearse with a timer
Input: the near-final deck and real time limit.
Action: deliver the presentation aloud. Mark slow transitions, unexplained terms, and slides that consistently take too long. Revise the deck instead of merely planning to speak faster.
Output: a timed version with deliberate transitions. Check: finish with enough time for the planned next step or questions.
Step 8: Run the delivery check
Input: final deck, destination, and presentation environment.
Action: open the exported or shared version on the device that will be used. Confirm fonts, media, links, presenter notes, permissions, and backup access. Record the final version so collaborators do not present an outdated file.
Output: a presentation that is ready to deliver. Check: the first slide, final call to action, and every linked asset work outside the editor.
Common Presentation Problems and Fixes
| Problem | Likely cause | Fix |
|---|---|---|
| The deck feels long | Slides repeat context or evidence. | Give each slide a job and move detail to the appendix. |
| The audience asks “so what?” | Titles describe topics instead of decisions. | Rewrite titles as findings, implications, or asks. |
| Slides are hard to read | Text is compensating for an unclear narrative. | Reduce copy, enlarge the key point, and explain the rest verbally or in notes. |
| Questions derail the meeting | Definitions, sources, or limits are hidden. | Add a methodology note and an appendix with traceable detail. |
| The close is vague | No owner, deadline, or decision rule was assigned. | End with one explicit next action and a review signal. |
Good Presentation Checklist
- The audience, decision, and time budget are explicit.
- The opening slide states why the topic matters now.
- Each slide has one primary job and a title that carries the point.
- Evidence uses honest scales, clear sources, and visible limitations.
- Text and visuals are readable on the actual display and for remote viewers.
- The deck distinguishes observations, interpretations, and recommendations.
- The presenter has rehearsed transitions, questions, and timing.
- The final slide names the decision, owner, date, and next review signal.
Frequently Asked Questions
Is the 10/20/30 rule right for every presentation?
No. It is a focus and legibility heuristic created for pitches. Use the audience’s needs, room, format, and time as the governing constraints.
Should every presentation have a story?
Every presentation needs a logical path. It may be a problem-solution story, a research question, a teaching sequence, or a decision review. Narrative means the ideas connect; it does not require drama.
How can AI improve a presentation?
AI can help organize an outline, propose slide titles, and draft layouts. Review the result for factual accuracy, source handling, readability, accessibility, privacy, and audience fit.
Bottom Line
A good presentation respects the audience’s attention. Define the decision, build a clear arc, give each slide one job, show evidence honestly, and close with an owned next step. Use the 10/20/30 rule when it helps you focus, and use Presenti AI to accelerate the first editable draft without outsourcing judgment.
