How to turn a written document into a presentation

You’ve written the doc. It’s thorough, it’s well organised, and everyone agreed it was useful. Now someone says, “Can you present this on Friday?” and you’re staring at four thousand words wondering how they become twelve slides.

The good news: a written document is a great starting point for a presentation. The thinking is done. What’s left is translation, and translation follows a repeatable process. This guide walks through it, using a product proposal as the running example.

Why you can’t just paste it in

Documents and presentations do different jobs.

A document is read at the reader’s pace. They can skim, scroll back, check a footnote and come back tomorrow. It can afford detail, caveats and full sentences.

A presentation is mostly heard. The audience moves at your pace, reads each slide once, and needs to get the point in a few seconds while also listening to you.

So copying paragraphs onto slides gives you the worst of both: too much to read, and nothing left for you to say. The aim is not to shrink the document. It’s to pull out its skeleton and its few most important details.

Step 1: Write the one-sentence message

Before touching slides, finish this sentence: “After this presentation, the audience should…”

For our example proposal, that might be: “…agree to fund a two-person team for one quarter to build an offline mode for the field app.”

That sentence is your filter. Every slide should help the audience get there. Sections of the document that don’t help can stay in the document, which you can share afterwards.

Step 2: Know who’s in the room

The same doc becomes a different deck depending on the audience.

Audience	What they care about	What to emphasise
Leadership	Cost, impact, risk	The ask, the expected result, the trade-offs
Engineering	Feasibility, scope	Approach, dependencies, timeline
Sales or support	What changes for customers	Use cases, launch timing, what to tell people

Pick the primary audience and build for them. If you need to present to two groups, it’s usually quicker to make two short versions than one long one that tries to please everybody.

Step 3: Map the structure

Look at your document’s headings. They’re probably a decent first draft of your slide outline. A typical proposal doc might have:

• Background
• Problem
• Research findings
• Options considered
• Proposal
• Cost and timeline
• Risks
• Open questions

Now reorder for a listener. Readers are happy to build up to the conclusion. Listeners would rather hear it early, then see the reasoning. A presentation outline for the same content might be:

1. The ask (one slide)
2. The problem, in the customer’s terms (one or two slides)
3. What we learned (one or two slides)
4. The proposal (one or two slides)
5. Cost, timeline and risks (one or two slides)
6. Decision needed (one slide)

Options considered and open questions can go into a backup section at the end, ready if someone asks. If your source is a Word file rather than a workspace page, from a Word document to a presentation covers what to keep.

Step 4: One point per slide

For each slide, write a headline that states its point as a full sentence. Not “Research findings” but “Field staff lose work when signal drops, several times a week.”

This does two things. It forces you to decide what each slide is actually saying. And it means someone who reads only the headlines still gets the story.

A quick check: read your headlines in order, out loud. Do they make sense as a short paragraph? If yes, your structure works. If a headline feels out of place, move it or cut it.

Step 5: Cut the text down

Now fill each slide. This is where most of the work is. Take the relevant section of the doc and reduce it hard.

Turn paragraphs into a few short lines. A paragraph explaining three reasons becomes three short phrases. Your speech carries the rest.

Drop the qualifiers. Documents need “in most cases” and “subject to further review”. Slides usually don’t; say the caveat out loud if it matters.

Keep the numbers, lose the prose around them. “In our interviews, we spoke to 14 field staff, and 11 of them mentioned losing work” becomes a single figure with a short label. (Those numbers are just an example.)

Move the detail into speaker notes. Anything you want to remember to say, but don’t need the audience to read, goes in the notes. This is often a good home for the paragraphs you cut.

A rough guide: if a slide needs more than about thirty words to make sense, it’s probably two slides or it’s carrying detail that belongs in your notes. There’s more on this in writing pages that turn into good slides.

Step 6: Turn structure into visuals

Documents often hide visual ideas in their text. Look for:

• Tables of numbers. A small table comparing options can become a simple bar chart. Keep the table in the appendix for anyone who wants exact figures.
• Sequences. “First we… then… finally…” is a timeline or a process diagram.
• Comparisons. “Option A is cheaper but slower; option B…” is a two-column layout.
• Lists of parts. Three or four related ideas can sit side by side as short cards instead of a bullet list.
• Quotes from research. One strong, short quote from a user interview, shown large, can do more than a paragraph of summary. Use real quotes only, and only with permission.

You don’t need a visual on every slide. One clear chart or diagram where it genuinely helps is better than decoration everywhere.

Step 7: Add an opening and a close

Documents often open with background. Presentations work better with a hook: the problem, a moment that illustrates it, or the ask itself.

For the example: “Last month, a field engineer in Pune filled in a site report, lost signal on the way out, and lost the whole thing. That’s the problem we want to fix.” (An illustrative scenario.)

Close with the one-sentence message from step 1, stated as a clear ask. Then stop. A final slide that just says “Questions?” wastes the most-looked-at moment of the talk; leave your ask on screen instead.

Step 8: Keep the doc as the companion

Your document didn’t stop being useful. Share it before or after the presentation as the full reference. You can mention it in the deck, for example on the last slide: “Full proposal, research notes and cost breakdown are in the project doc.”

This takes pressure off the slides. They don’t have to contain everything, because everything already lives somewhere. If the doc lives in Notion and you want the slides in PowerPoint, a Notion to PPT converter can give you a first draft to edit.

Step 9: Rehearse with the doc closed

Run through the deck once without looking at the document. Where you get stuck, either the slide is missing a cue or the point isn’t as clear as you thought. Fix it and run through again.

Time yourself, too. A useful pace for most business presentations is around one to two minutes per slide. If you’re well over the time you’ve been given, cut slides rather than talking faster.

A quick worked example

Here’s how one section of the example doc translates.

In the document (about 120 words): a paragraph describing the interview process, three paragraphs summarising what field staff said, and a note on limitations of the sample.

On the slide:

• Headline: “Field staff lose work when signal drops”
• One short quote from an interview, shown large
• Three short lines: lost reports, duplicate visits, workarounds on paper

In the speaker notes: who you interviewed, how, and the limitations of the sample.

Same information, three layers: what people see, what they hear, and what they can read later.

The checklist

Before you present, check:

• Can you say the main message in one sentence?
• Does the ask appear near the start and at the end?
• Does each slide have a sentence headline that makes one point?
• Do the headlines, read in order, tell the story?
• Have long paragraphs moved to speaker notes or the appendix?
• Is there at least one visual where the content is naturally visual?
• Is the original doc ready to share?

The steps here work for any doc, whether it’s a spec, a research summary or a strategy note. If your doc already has clear headings, Notion2Deck can take the page and handle the first draft of this translation for you, so you can spend your time on the parts that need your judgement. For decks that don’t start from a page, an AI presentation maker like Presentations.AI can draft the slides from a short description.