What to Put on a Presentation Slide

Ask what a slide is for before you decide what goes on it. Its job is not to document everything you know about a topic — that is what a report is for. Its job is to give an audience one thing to look at while you make one point out loud. The moment a slide is asked to carry two points, the audience has to choose which one to follow, and most will follow neither closely.

You can test this on any slide you have already made. Cover the slide and try to state its point in one sentence. If you need "and" to finish that sentence — "this slide shows our growth and our biggest risk" — it is two slides pretending to be one. Split it, and each half gets easier to design, because it only has to serve a single job.

This rule also changes how you should feel about slide count. A deck built on one idea per slide will usually run longer, not shorter, than one where each slide is stuffed with everything related to a topic. That is fine. A longer deck of single-point slides moves faster for an audience than a shorter deck of crowded ones, because nobody has to stop and parse.

Compare "Q3 Retention" to "Retention rose 22% after we shipped onboarding v2." The first is a label — it tells the audience what the slide is about but not what it means. The second is a claim: read it on its own, out of context, and you already know the point. Assertion-style headlines like this do most of the work a slide needs to do, before a single bullet is added.

Once the headline is doing that work, the support underneath has one job: prove it, not restate it. Three or four short bullets, a single chart, or one well-chosen number is usually enough. If you find yourself adding a fifth or sixth supporting point "just in case," that is usually a sign the point needs a second slide, not a longer one.

The test for whether support belongs on the slide is simple: would removing it make the headline less believable? If yes, keep it. If it is interesting but not load-bearing — background, a tangent, a caveat that only matters to one person in the room — say it out loud instead. It still gets communicated; it just is not competing for space with the point.

Numbers belong in a chart, not a sentence describing the number. A trend that took you three sentences to explain in a doc — "revenue grew steadily through the first half, dipped in Q3 due to seasonality, then recovered" — is one glance as a line chart. The audience reads the shape faster than they can read the words, and they remember shapes longer than sentences.

The same logic applies to process and comparison. A workflow described in prose ("first we do X, then Y depends on whether Z happens") is a diagram: boxes and arrows tell the same story with no reading required. A comparison between two options is a short two-column list or table, not a paragraph weighing pros against cons — the structure itself is the argument.

This is where having your source material already in editable form pays off. If your slide content started life as a long report, spreadsheet, or set of notes, the raw material for a chart or comparison is usually already there — it just needs pulling out, not re-writing. Eazy reads PDFs, Word docs, PowerPoint files, spreadsheets, and web links into editable content up front, so the numbers and structure you need for a visual are sitting in the document rather than buried in a paragraph you have to re-derive.

1. One-idea check. Cover everything but the headline and state the slide's point in a single sentence. If you need two sentences or an "and," the slide is carrying two ideas and should be split before you touch design.

2. Headline check. Read only the headline, nothing else on the slide. If it is a label ("Pricing") rather than a claim ("Our pricing is the main blocker for mid-market deals"), rewrite it as a sentence that states the point.

3. Minimum-support check. Count what is backing the headline. If it is more than three or four bullets, one chart, or one strong example, ask which pieces are proving the point and which are just true but unnecessary — cut the rest to notes.

4. Visual check. Look at anything written as a sentence or paragraph and ask whether a chart, diagram, photo, or short list would make the same point faster. If yes, that is usually the better slide.

A useful split: the slide is what the audience needs if they are looking at it silently; the notes are what you add by talking. The retention number goes on the slide. The story of the specific customer conversation that explains why retention moved goes in your notes, or in your mouth, not in a smaller font at the bottom of the slide.

Caveats and qualifiers are the most common thing that leaks onto slides that should stay in notes. "This excludes enterprise accounts, which we are tracking separately" is true and worth saying, but it dilutes the headline claim if it is printed underneath it. Say it out loud when someone asks, or say it proactively as you present — keep the slide itself clean.

Transitions are another example. "Now that we have covered the problem, let us look at the cost" is something you say, not something you print. It belongs to the flow of your talk, not the content of any one slide. Treating your speaker notes as a real, separate layer — not an afterthought — is what makes it possible to keep slides this lean without losing anything you actually wanted to say.

If you want the deeper version of that split, see how to write speaker notes and how to write bullet points for slides for the mechanics of turning a slide's remaining content into short, scannable lines.

Every check above — one idea, a headline that states the point, minimal support, a visual instead of a paragraph — is a decision about content, not layout. Making those calls is much easier when you are writing in a real document than when you are already inside a slide editor moving text boxes around. That is the case for working content-first: write your headline and bullets as text, get the one-idea rule right on the page, and only then design.

In Eazy, that document is the deck. You write in a real editor — headings for slide breaks, bullets for support, toggle lists for the details you are not sure belong yet — and it is what gets designed, not a summary of it. Bring in a source you already have, too: drop in a PDF, Word doc, PowerPoint, spreadsheet, or a web link and Eazy reads it into editable content, so the trimming described above starts from your real material instead of a blank page.

Once the content is right, Eazy designs every slide for you and keeps it on-brand by default, and you can restyle the whole deck by applying a theme. If a slide still is not carrying its idea cleanly, change that one line and only that slide rebuilds — you are not stuck re-editing a whole deck because one headline needed to say something sharper. Start with a thought, not a prompt.