Gemini for Presentations: Plan, Build, and Review Slides
Start with a clear audience and source material, then use Gemini to plan and build a presentation. Check the claims and the actual slides before handing the deck to anyone else.
Updated 5 min read
Use Gemini for presentations by defining the audience and decision first, building an outline from approved sources, and reviewing the generated slides for accuracy and layout. In supported Google Slides workflows, Gemini can generate an editable presentation or help revise individual slides.
The deck also needs a durable record of its purpose, evidence, and remaining checks. fenbs can keep that context and the review handoff outside the presentation conversation, so the next editor knows which claims are approved and which slides still need work.
How do you turn a presentation idea into a useful first draft?
- Name the audience and the action you want them to take. A decision meeting needs a different story from a training session.
- Collect the approved sources and mark material that is background only. Include the latest figures, definitions, and any required wording.
- Ask for an outline with one main point per slide. Review the sequence and remove anything that does not help the audience act.
- Build the presentation using the supported Gemini features available in your account. Keep the source material attached to the request where appropriate.
- Inspect the actual slides, verify the claims, and rehearse the talk before sharing the final deck.
For example, a small design studio might need a client to choose between two layout directions. Its deck should explain the choice, compare the options fairly, and end with the requested decision. A long company introduction could make the presentation worse even if every slide looks polished.
Which Gemini presentation workflow should you use?
You can plan the story in a Gemini conversation, then work on the deck in Slides. Google documents generating a presentation in Google Slides (opens in a new tab): provide a prompt and optional references, review the proposed plan, and approve generation. The result is editable. Check that page for current availability rather than assuming every account has the same controls.
For an existing deck, Google’s Gemini in Slides guide (opens in a new tab) covers generating new slides, summarizing a presentation, and rewriting content. Use that smaller workflow when only a few slides need attention. Rebuilding an approved deck can create extra review work without improving the message.
| Stage | Useful request | Your review |
|---|---|---|
| Before building | Propose a slide sequence from the audience, objective, and sources. | Does every slide help the audience understand or decide? |
| First visual draft | Generate the presentation from the approved outline and references. | Are the claims supported and the visual structure readable? |
| Revision | Rewrite or add the specific slide that needs work. | Does the change fit the surrounding argument and design? |
| Before delivery | List questions the audience may ask about the deck. | Can the presenter answer from evidence rather than guesses? |
If most of your effort is organizing research before you have a story, the Gemini Notebook guide covers that separate starting point. Keep the presentation workflow focused on explaining the evidence to a particular audience.
What should your presentation prompt include?
Include the audience, desired outcome, speaking time, source list, and constraints. Say whether the deck will support a live speaker or be read on its own. A slide that works while someone explains it may be confusing as an emailed document.
Plan a presentation for a client choosing a website layout. Audience: the owner and marketing lead. Speaking time: 10 minutes. Goal: choose option A or option B, or identify one blocking question. Use only the attached approved design summary and comparison notes. For each slide, give a main point, supporting evidence, and a visual idea. Mark missing evidence as a question. Do not invent client feedback. End with the exact decision we need, not a generic thank-you slide.
Review the outline before the visuals. Look for repeated points, an unsupported leap, or a conclusion that appears before the evidence. If the requested action is unclear in plain text, changing the theme or adding images will not resolve it.
How do you verify claims without slowing every revision?
Build a small claim list: the slide reference, factual claim, original source, and review status. Verify numbers, quotations, customer statements, and assertions about other products. Open the underlying page or document and check the exact passage instead of accepting a familiar-looking citation.
Check that each chart uses the same reporting period and definitions as its label. A figure copied correctly from a source can still be misleading if it is compared with a different measure. Keep hypothetical examples clearly labeled and separate from real results.
Record approved claims and human choices with their source references in fenbs project context. When a source changes, a review task can say which slide and conclusion need another check. The deck remains the presentation; the project record explains the work behind it.
What should you inspect on the finished slides?
Review the rendered presentation slide by slide, at the size the audience will see. Text can be factually correct and still be unreadable. Look for clipped labels, crowded charts, weak contrast, inconsistent terminology, and images that imply something the evidence does not support.
- Read every title alone. Together they should tell the story in order.
- Check the smallest chart labels and source notes from a realistic viewing distance.
- Check whether color is the only way to distinguish options or chart series.
- Confirm that screenshots, logos, and photographs are appropriate for the intended audience and use.
- Run through the presentation aloud and cut material that exceeds the available time.
After editing, inspect the format you will actually share. If you export a PDF, open that PDF. If another person will present, send them the approved deck location and the speaking context, including any question that still lacks an answer.
Keep the presentation ready for its next editor
Save the audience, goal, evidence references, and approved choices in a fenbs project. Make outstanding slide checks into tasks and leave a clear Where we left off entry. A connected assistant can read that record before helping with the next revision.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account and add a project for the deck, with its audience, purpose, and current presentation link.
- Record the choices a person approved, such as the proposed recommendation and required terminology, in Decisions and rules.
- Add tasks for missing evidence, chart checks, and layout review. Name the affected slide or section in each task.
- Connect a supported assistant through Integrations. Ask it to read the context before work and save progress before stopping, including which deck version was checked and what remains.
fenbs does not generate or edit your Google Slides deck. It helps when context and review work must survive a handoff; a one-off personal presentation may need only your source notes and a checked deck. The Gemini project management guide and AI at work hub cover related ways to keep ongoing work organized.