An AI Workflow for Creating Presentations
A reliable AI presentation workflow moves through five stages in order: outline the structure first, draft slide content one section at a time, write speaker notes separately from slide text, add visual guidance, then review and export. Skipping straight to "make me slides about X" is what produces a wall-of-text deck that needs a full rebuild.
Picture it's 9 p.m. and tomorrow's lesson still needs a slide deck — a title slide, five content slides, and a wrap-up. Trying to generate all of that in one request tends to produce a rough draft that reads more like an essay chopped into pieces than a set of slides built to be presented.
Quick Answer: Build a presentation with AI in five stages: outline the slide count and structure first, draft each slide's content separately, write speaker notes as their own request, add visual/layout guidance, then review before exporting. Treating slide generation as one big request is the most common reason a deck comes back needing a total rewrite.
What an AI-Assisted Presentation Workflow Actually Looks Like
A presentation isn't one document — it's several different types of content stacked together: an outline, slide text, speaker notes, and visual layout. Each of those benefits from its own focused prompt rather than one request trying to do all four at once.
| Stage | What It Produces | Common Mistake at This Stage |
|---|---|---|
| 1. Outline | Slide count and section structure | Skipping straight to slide text without a plan |
| 2. Slide content | The actual text on each slide | Asking for a full deck's text in one request |
| 3. Speaker notes | What the teacher says while presenting | Letting slide text and notes blur into the same thing |
| 4. Visual guidance | Layout and image/diagram direction | Assuming AI-generated text implies finished visual design |
| 5. Review and export | A checked, classroom-ready file | Skipping the read-through before presenting |
This staged approach is the same underlying principle covered in AI Prompting & Content Workflows for Teachers (2026 Guide) — break a large content type into its real sub-parts, then prompt for each one on its own.
Stage 1: Outline Before You Generate a Single Slide
An outline decides slide count, section order, and each slide's one job — decisions that are much cheaper to fix at the outline stage than after ten slides already exist.
A Working Outline Prompt
- "You are a Grade 5 science teacher. Outline an 8-slide presentation on the water cycle: a title slide, 5 content slides (one concept per slide), a summary slide, and a discussion-question slide. List only the slide titles and one-sentence purpose for each, not full content yet."
Why Slide Count Belongs in the First Prompt
Stating slide count upfront prevents a common failure mode: a model that either crams too many ideas onto too few slides, or pads a simple topic out to twice the length it needs. Fixing an outline's structure takes one sentence; fixing ten already-drafted slides takes much longer.
Reviewing the Outline Before Moving On
A quick scan of the outline for logical order and one-idea-per-slide framing catches structural problems while they're still cheap to fix. Reordering two outline bullet points is a much smaller edit than reordering two fully drafted slides.
Stage 2: Drafting Slide Content One Section at a Time
Once an outline exists, draft slide text in small batches — two or three slides per prompt — rather than requesting the entire deck's content at once. Smaller batches are easier to review and far easier to revise without losing the parts that already worked.
The One-Idea-Per-Slide Principle
Cognitive-load research associated with Richard Mayer's multimedia learning principles has long argued that overloading a single slide with too much text or too many ideas at once makes it harder for an audience to process, not easier. A slide-content prompt should explicitly ask for this constraint, not assume the model will apply it on its own.
| Slide Text Style | What It Does | Prompt Instruction |
|---|---|---|
| Dense paragraph | Forces the audience to read instead of listen | Avoid — request bullets instead |
| Bulleted key points | Supports a spoken explanation | "3-5 short bullet points, no full sentences" |
| One concept per slide | Keeps pacing manageable | "Split this into 2 slides if it covers more than one idea" |
A Content-Slide Prompt Template
- "Draft the text for slides 2-4 of this outline. Each slide gets a title and 3-5 short bullet points, no full sentences, no more than 8 words per bullet. Flag if any single slide seems to be covering more than one main idea."
That last instruction — flagging overloaded slides — catches a real, common failure: a "concept" from the outline that actually needed two slides, not one.
Stage 3: Speaker Notes and Talking Points
Speaker notes and slide text serve different purposes, and asking for both in the same request tends to blur them into one another. Slide text is what the audience reads; notes are what the presenter says.
Why Notes Need a Separate Prompt From Slide Text
A single combined request often produces slide bullets that are really just shortened notes, or notes that just repeat the bullets word for word. Requesting notes as a distinct, second pass — after the slide text is finalized — keeps each doing its own job.
A Speaker-Notes Prompt Template
- "Write speaker notes for these 5 slides. Each note should expand on the slide's bullets in full sentences, roughly 3-4 sentences per slide, written in a conversational tone appropriate for explaining this to a Grade 5 class."
Notes written this way give a substitute teacher, or the same teacher a year later, enough context to deliver the lesson without having to reconstruct what each terse bullet point was supposed to mean.
Stage 4: Visual and Design Guidance
An AI tool can describe what a slide's visual should show even when it isn't producing the final graphic itself, and that description is worth requesting explicitly.
- "For the slide on evaporation, suggest what a supporting diagram should show — labeled arrows for the process steps, not a decorative stock image."
- "Note where a slide would benefit from a simple table instead of bullet points, based on this content."
Why "Suggest, Don't Assume" Matters Here
Slide text alone doesn't communicate layout. A prompt that explicitly separates "what to write" from "what a visual should show" produces guidance a teacher can act on when assembling the final deck, rather than a vague implication buried inside the bullet text itself.
Walking Through a Full Deck: A Worked Example
Seeing all five stages applied to one real 8-slide deck makes the workflow concrete rather than abstract. Say the topic is the water cycle for a Grade 5 science class, due tomorrow morning.
- Generate the outline first — 8 slides, one-sentence purpose each, reviewed for logical order before moving on.
- Draft slides 1-3 (title, evaporation, condensation) in one batch, checking for one-idea-per-slide framing.
- Draft slides 4-6 (precipitation, collection, a summary diagram) in a second batch, using the same bullet-style instruction.
- Draft the closing discussion-question slide separately, since its format — an open question, not bullet points — is genuinely different from the rest.
- Request speaker notes for all 8 slides in one follow-up pass, now that the slide text itself is finalized.
- Ask for visual guidance slide by slide, noting where a diagram or table would replace a wall of bullet points.
- Do a full read-through, checking science accuracy, slide count, and pacing before the file goes anywhere near a projector.
That sequence takes longer than one giant "make me a water cycle presentation" request. The payoff shows up in revision time: a five-stage draft built this way usually needs small, targeted fixes rather than a full regeneration, and the same seven-step shape works for almost any single-topic lesson, not just this one.
Adjusting the Workflow by Presentation Purpose
Not every classroom presentation serves the same purpose, and the five-stage workflow bends slightly depending on who the deck is actually for.
| Presentation Purpose | Slide Emphasis | Notes Emphasis |
|---|---|---|
| Teacher-led lecture | Concept explanation, one idea per slide | Detailed talking points |
| Student review deck | Question prompts, minimal text | Light or none — students self-pace |
| Parent-night or open house | Simple summary points, visual-first | Warm, brief, non-technical language |
Building a Student-Facing Review Deck
A deck meant for students to click through on their own needs a different content-slide prompt than a lecture deck: "Draft slides 1-5 as a self-paced review deck. Each slide should pose a short question or prompt a student can answer before revealing the next slide, rather than presenting a full explanation." Speaker notes are largely unnecessary here, since no one is presenting live.
The Same Five Stages, a Different Subject
The outline-then-draft structure holds regardless of subject — a world-language class needs the same staged approach, just with vocabulary-heavy slide content instead of a science concept. How to Write AI Prompts for Spanish covers how slide and worksheet prompts shift when the content itself is vocabulary and conjugation practice rather than a science process.
Building a Reusable Slide-Outline Library
A handful of saved outline shapes, reused across many topics, is what makes this workflow faster the second time and every time after that. Without one, each new topic starts the outline stage completely from scratch.
- Concept-explanation shape: title, 4-6 concept slides (one idea each), a summary slide, a discussion-question slide — reusable for most single-topic science or social studies lessons.
- Compare-and-contrast shape: title, one slide per item being compared, a side-by-side summary slide — reusable whenever a lesson sets two things against each other.
- Process/sequence shape: title, one slide per step in order, a full-sequence recap slide — reusable for anything with ordered steps, from the water cycle to a writing process.
Discussion Slides Feed Into a Larger Question Bank
A deck's closing discussion-question slide doesn't have to stand alone. Saving those questions alongside a larger item bank — see How to Generate 50 Quiz Questions in 5 Minutes With AI for building that bank at scale — turns a handful of one-off discussion prompts into a reusable review resource by the end of a unit.
Stage 5: Review, Export, and Reuse Next Year
A finished draft still needs a human read-through, and the right export format saves a real reformatting step afterward.
| Export Format | Best For | Note |
|---|---|---|
| PPTX | Editing further in PowerPoint or Google Slides | Most flexible for last-minute tweaks |
| Sharing a locked, non-editable version | Good for posting to a class portal | |
| HTML | Presenting directly from a browser | Useful when no slide software is installed |
EduGenius can generate slide content aligned to a saved class profile and export directly to PPTX, which is designed to skip the step of manually rebuilding a generated outline inside separate slide software. That same saved profile can carry over the next time a similar lesson topic comes up.
A saved, working outline is worth keeping past this one lesson — the same three-slide "concept" structure often reuses well the next time a related topic comes up, the same way a How to Batch-Generate Flashcards With AI term list reuses across a unit's review sessions.
Accessibility Considerations for AI-Generated Slides
A generated deck that reads well on screen doesn't automatically work for every student, and a couple of prompt additions close most of the gap.
- Request alt-text descriptions for any suggested image or diagram: "Include a one-sentence alt-text description for the diagram suggested on this slide."
- Ask for plain, direct language on any slide meant to be read independently, since dense academic phrasing is harder to process for students working in a second language or with a reading disability.
- Avoid relying on color alone to convey meaning in a suggested chart or diagram — ask the model to note this explicitly when it proposes a visual.
None of this replaces a school's own accessibility review process. It does mean the first draft arrives closer to usable, rather than needing every slide retrofitted for accessibility after the fact.
UNESCO's guidance on inclusive digital learning materials makes a related point about instructional content generally: accessibility considered from the start of a workflow is consistently less disruptive than a separate remediation pass applied to a finished document.
Pro Tips for a Smoother Presentation Workflow
- Never skip the outline stage, even for a short 5-slide deck — it's the cheapest point to fix structure.
- Draft in small batches, 2-3 slides per request, rather than the whole deck at once.
- Request speaker notes after slide text is finalized, not in the same prompt, so each stays distinct.
- Ask the model to flag overloaded slides during the content-drafting stage — this catches outline concepts that actually needed two slides.
- Save a working outline structure by topic type, not just by lesson, since a "5 content slides + summary + discussion" shape reuses well across many topics.
- Request alt-text and plain-language checks as part of the visual-guidance stage, not as an afterthought once the deck already feels finished.
- Keep a short log of edits made after each draft. A pattern of the same fix — too much text per slide, notes repeating bullets — usually means the prompt template itself needs a small permanent adjustment.
For a subject-specific slice of this same prompting skill, How to Write AI Prompts for English covers the writing side of lesson content, and The Best AI Prompts for Generating Quizzes is a natural next step once a deck needs a matching comprehension check.
What to Avoid When Building Presentations With AI
- Requesting the entire deck's text in one prompt. This is the single most common cause of dense, essay-like slides that need a full rewrite.
- Letting slide text and speaker notes come from the same request. Without separating them, bullets and notes tend to blur into repetitive versions of each other.
- Skipping the outline stage for a "quick" deck. A 5-slide deck built without a plan still risks one slide silently covering two ideas at once.
- Presenting a generated deck without a full read-through. Content accuracy and pacing both need a human check regardless of how well-structured the prompts were.
- Ignoring accessibility until the deck feels done. Alt-text and plain-language checks are cheaper to build into the visual-guidance stage than to retrofit across every slide afterward.
Key Takeaways
- A five-stage workflow — outline, slide content, speaker notes, visual guidance, review and export — produces a more usable deck than one large request.
- Cognitive-load research behind Richard Mayer's multimedia learning principles supports the one-idea-per-slide rule that keeps slides from overwhelming an audience.
- Drafting slide content in small batches of 2-3 slides is easier to review and revise than a full deck generated at once.
- Speaker notes deserve a separate prompt from slide text, requested only after the slide content itself is finalized.
- Asking a model to flag slides covering more than one concept catches a common outline-to-content gap early.
- A saved outline structure, organized by topic type, reuses across many future lessons, not just the one it was built for.
- A full read-through for accuracy and pacing stays necessary regardless of how carefully each stage's prompt was written.
Frequently Asked Questions
What's the biggest mistake teachers make when generating a presentation with AI?
Requesting the full deck's text in a single prompt is the most common one — it tends to produce dense, paragraph-heavy slides that read like an essay rather than a set of slides built for a spoken presentation.
Should speaker notes and slide text come from the same prompt?
No. Requesting them separately, with notes generated only after slide text is finalized, keeps each doing its own job — slide text stays scannable for the audience, and notes carry the fuller explanation for the presenter.
How many slides should one AI prompt draft at a time?
Two to three slides per request is a practical batch size. It's small enough to review carefully and revise without losing the parts that already worked, and large enough to move faster than drafting one slide at a time.
Can AI actually design the visual layout of a slide?
Not the finished graphic design, but it can suggest what a visual should show — a labeled diagram instead of a stock photo, for instance — which is useful guidance a teacher can act on while assembling the final deck.
Is it worth outlining a short, 5-slide presentation, or just quick decks?
Yes. Even a short deck risks one slide silently covering two ideas at once without a plan, and fixing that at the outline stage takes a sentence; fixing it after the slide is drafted takes a full rewrite.
Does a student-facing review deck need the same workflow as a lecture deck?
The same five stages apply, but the content-slide prompt changes — a review deck asks for short questions students answer at their own pace, rather than the fuller explanatory bullets a lecture deck needs, and speaker notes are usually unnecessary since no one presents it live.
References
- Richard Mayer — cognitive-load and multimedia-learning research on how audiences process slide content.
- ISTE — guidance on effective use of AI-generated instructional materials in the classroom.