3.1Creating a presentation from Word or a prompt
The essentials in 30 seconds
- Two starting points, only one reliable: a well-styled Word document (Heading 1/2) produces a structured deck — a prompt alone only produces a draft to check.
- Copilot delivers a 70% skeleton: slide breakdown, titles, bullets, speaker notes — the structure is there, the finishing is yours.
- Outline first, design second: validate the story (the slide sequence) before designing — and check every figure against the source.
Running mini-case — Hicham turns his report into a deck
Hicham, administrative assistant in Algiers, must present his 10-page Word report on department activity to the committee on Monday. Instead of copying it by hand, he asks Copilot in PowerPoint: “Create a presentation from my report, 10 slides max, one summary slide, speaker notes”. He gets a skeleton in one minute: he validates the outline, deletes two weak slides, checks every figure against the report, then applies the house theme. The committee sees a clean deck — Hicham kept control of the story.
This same case returns in the lesson, the diagram, the script and the 48h challenge.
1. Two starting points: styled Word or framed prompt
Copilot creates a presentation in two ways. From a Word document: “Create a presentation from this document” — Copilot turns the report into structured slides, titles and bullets. Or from a simple prompt: “Make an 8-slide presentation on our quality plan”. Hicham chooses the first route: his report from Algiers, already structured with headings, produces a faithful outline.
The most reliable path remains a solid source document: slide quality directly depends on source quality — a clear document produces a clear presentation. From a prompt alone, demand the frame: number of slides, audience, tone, expected sections — otherwise you get a generic draft to redo line by line.
2. 70% skeleton: validate the outline, iterate, verify
Copilot generates a skeleton: slide breakdown, titles, key points, sometimes visuals and speaker notes. This is not a final deliverable, it is a 70% starting point. Reflex: first validate the outline (does the sequence tell the right story?) before polishing the design — reorganizing a skeleton is easy, doing it on a finished deck is painful.
Then iterate in natural language: “add a conclusion slide”, “summarize slide 3 in 3 bullets”, “add speaker notes”. Safeguard: figures and claims picked up by Copilot must be checked against the source document, especially when they come from a prompt. A wrong slide shown in a meeting is costly.
The press-button deck
Generate fast, always verify: the committee remembers.
🔎 Concrete example — A project report turned into a presentation
Hicham has a 10-page Word report to present to the committee on Monday.
In PowerPoint: “Create a presentation from [activity-report.docx]: 10 slides max, one summary slide, speaker notes.”
Then: “Add a risks slide” · “Summarize slide 4 in 3 bullets”Reading: a complete skeleton in one minute, ready to refine slide by slide.
Lesson: your 30% — validate the sequence, check the figures, polish the visuals.
Section vocabulary
- Presentation from Word
- “Create a presentation from this document”: Copilot turns a report into structured slides.
Simple example: Hicham's activity report turned into a 10-slide deck.
What it is not: manually copying the report slide by slide.
Reflex: style the Word document (Heading 1/2) before generating.
- Presentation from a prompt
- “Make an 8-slide presentation on X”: Copilot starts from a simple description — less reliable than a sourced document.
Simple example: A quick draft of the quality plan requested by Hicham.
What it is not: a sourced deck checked against a document.
Reflex: frame slides, audience, tone and expected sections.
- Skeleton
- The slide breakdown, titles, key points, visuals and notes — a 70% starting point, not a final deliverable.
Simple example: Hicham's V1: right outline, design still to do.
What it is not: a finalized presentation ready to present.
Reflex: validate the outline before any formatting.
- Speaker notes
- The supporting text under each slide, generated by Copilot: a speech base to rework.
Simple example: The notes Hicham rereads before the committee.
What it is not: the text shown on the slide itself.
Reflex: systematically request them at generation time.
- Validate the outline first
- Check the slide sequence (the story) before polishing the design: reorganizing a skeleton is easy.
Simple example: Hicham deleting two weak slides before designing.
What it is not: formatting first then redoing everything when the story changes.
Reflex: reread the narrative thread before the theme.
In practice — Generate a presentation from a real document
- Pick a solid Word document (report, memo) to present.
- In PowerPoint, request the presentation from that document, framing the number of slides and the notes.
- First validate the outline: does the slide sequence tell the right story?
- Refine with instructions (add/summarize/rephrase a slide), then check figures and claims.
Ready-to-say script — presenting your V1 to your manager (30 s)
“I generated the deck from my report: 10 slides, summary and speaker notes in one minute. I validated the outline, deleted two weak slides and checked every figure against the report. Only the house theme is left before the committee.”
Say in a progress check; show the V1 and the source side by side.
Copy-paste template — generation prompts
“Create a presentation from [activity-report.docx]: 10 slides max, professional tone, one summary slide, speaker notes.”
“Add a risks slide after slide 6.”
“Summarize slide 4 in 3 bullets and suggest a message-style title.”Freelancer
One well-styled report is enough: one framed generation produces a presentable client deck in one hour.
SME in Algiers
Hicham generates from the department report, checks the figures with his manager, then applies the house theme.
Project team
Standardize: start from the house .potx template before generating to keep the theme, then iterate slide by slide.
Beginner
This week: one styled Word document, one 8-slide generation, one outline review.
✓ Best practices
- Start from a solid Word document rather than a simple prompt: source quality makes slide quality.
- Validate the structure (the outline) before the design: reorganizing a skeleton is far simpler than a finished deck.
- Systematically add speaker notes: Copilot generates them and they save you real time.
✗ Common pitfalls
- Polishing the formatting before validating the sequence: you will have to redo everything if the story changes.
- Presenting unchecked figures from a prompt: a wrong slide in a meeting is costly.
- Expecting a final deliverable: the skeleton is a 70% start, the finishing is yours.
Key takeaways
- Copilot creates a presentation from a Word document or a simple prompt — the sourced document is more reliable.
- It generates a skeleton (slides, titles, notes): a 70% start, not a final deliverable.
- Validate the OUTLINE (the story) before the design: reorganizing a skeleton is easy.
- Check figures and claims before presenting: a wrong slide is costly.
48h challenge — apply tomorrow
Generate 1 deck from 1 real Word document (8-10 slides + notes), validate the outline and check 3 figures against the source.
- I generate from a styled Word document or a framed prompt.
- I validate the outline before any formatting.
- No figure goes into a meeting without verification.
Frequently asked questions
Is the generated presentation pretty?
Structured yes, finished no. Copilot sets the skeleton (titles, bullets, notes); design, pace and accuracy remain your 30%. The PowerPoint Designer then helps with formatting, and our PowerPoint levels 4-5 guides take over.
Is it better to start from a Word document or a prompt?
From a solid Word document: slide quality follows source quality. A lone prompt works for a quick draft, but needs more checking — then frame slides, audience, tone and sections.
What must you validate FIRST on a Copilot-generated presentation?