How to Write a Presentation Outline

Start With the Through-Line, Not the Slides

Every presentation worth giving has one core message. The through-line is that message stated as a single, specific sentence — not a topic ("our Q3 results") but a claim ("we beat the plan by growing retention, and here is how we do it again"). Topics describe what you will talk about; through-lines commit to what you want the audience to believe or do. Write yours down before anything else and keep it visible while you outline.

A good test: if you had ten seconds in an elevator, could you say it? If the sentence needs qualifiers, sub-clauses, or a second sentence to make sense, it is doing too much. Cut until one clear idea remains. The discipline of compression here pays off everywhere downstream — a sharp through-line makes it obvious which sections belong and which are just interesting tangents.

The through-line also gives you a decision rule. Every section, every point, every piece of evidence you consider later gets held up against it: does this advance the through-line, or is it just true? Plenty of accurate, well-designed slides get cut by this test, and the presentation is better for it.

Give Each Section Exactly One Idea

Once the through-line is fixed, ask what the audience needs to accept, in order, for that sentence to feel true. Those become your sections. Most strong presentations have three to five of them — enough to build an argument, few enough to hold in memory. Fewer than three often means the idea is thin; more than five usually means two sections are secretly one, or the scope is too broad for a single talk.

Write each section as a claim, not a label. "Pricing" is a label; "Our pricing is the main thing blocking mid-market deals" is a claim you can argue. Claims force you to take a position, and a position is what an audience remembers. When you name a section and cannot phrase it as a sentence someone could disagree with, it is probably a bucket of facts rather than a point.

The one-idea rule is also your best editing tool. If you find a section drifting into a second theme, that is a signal to split it or move the stray material elsewhere. This is where a content-first tool helps: when your outline lives in a real editor, each section maps cleanly to a slide or a short group of slides, so a section doing two jobs is visible as clutter rather than hidden inside a design.

Support Every Idea With Evidence

For each section, write down the two or three pieces of evidence that would actually change a skeptic's mind. Be specific: not "customers love it" but "retention rose from 71% to 88% after we shipped onboarding v2." Concrete evidence is more persuasive and, conveniently, far easier to design a slide around than a vague generalization. Numbers, before-and-afters, named examples, and short quotes all work; adjectives do not.

Match the evidence to the claim rather than to what you happen to have. It is tempting to include the chart you already made or the anecdote you love telling, but if it does not support the section's one idea, it belongs in an appendix or nowhere. When a section has no strong evidence behind it, treat that as information: the claim may be true but unprovable here, in which case cut it, or it may be the weak link your audience will poke at.

This is also the moment to note what you will not cover. Good outlines are as defined by what they exclude as what they include. Jot the tempting tangents in a "parking lot" so you can drop them without guilt and keep each section focused on the single idea it needs to deliver.

Sequence the Sections and Write the Transitions

Sequence is argument. The same sections in a different order tell a different story — and sometimes a broken one. A reliable default is problem, stakes, solution, evidence, and what happens next, but the right order is whatever makes each section a natural consequence of the one before it. If you can shuffle your sections freely without the presentation feeling wrong, they are probably a list rather than an argument, and a list is harder to remember.

Test the flow by writing the transition sentence between each pair of sections: "so if that is the problem, the obvious question is what it costs us — which is where the numbers come in." When a transition writes itself, the sequence is right. When you find yourself writing "and another thing," you have found a seam where the logic does not connect, and it is far cheaper to fix in the outline than after you have designed twenty slides around it.

Finally, revisit the through-line one more time and read the section claims top to bottom as a single paragraph. It should sound like a coherent argument for that one sentence. If it does, your outline is done and you are ready to design — the hard thinking is behind you.

In a Content-First Tool, the Outline Is the Deck

The usual workflow throws the outline away. You draft it in a doc, then start a slide file from scratch and effectively re-enter everything, losing the clean structure in the process. A content-first approach removes that gap. In Eazy you write the outline in a real editor — headings for sections, bullets for evidence, dividers where slides break — and that document is what becomes the deck. Start with a thought, not a prompt.

Because the document is the source of truth, editing stays easy after you design. Change one line in the outline and only that slide rebuilds; the slides you already liked stay put. You can also bring existing material in — drop in a PDF, Word doc, spreadsheet, or a web link and it is read into editable content — so an outline can start from research you already have rather than a blank page.

When the argument is right, you design: slides are built for you, on-brand out of the box, and you can restyle the whole deck by applying a theme, then export to PDF or PPTX. The point is not the design step, though — it is that the outline never stops being the thing you edit. Get the through-line, the one-idea sections, and the evidence right on the page, and the finished presentation is mostly a formatting decision.

Related Guides

Related Use Cases