<- Back to articles
Google GeminiGoogle SlidesFacilitationTraining Design

Gemini in Google Slides for Facilitator Assets

18 May 2026

How trainers and facilitators can use Gemini in Google Slides to create decks, visuals, summaries, and facilitator assets without letting slides replace learning design.

A facilitator using Gemini in Google Slides to build workshop assets

Answer-first summary

Gemini in Google Slides can help trainers and L&D teams create slide content, generate images, summarise presentations, rewrite text, reference Drive files, and refine slide copy.

But the deck is not the training.

Use Gemini in Slides after the learning structure is clear. Build the session first: outcome, activity, debrief, practice, transfer. Then use Slides to support the facilitator and learner experience.

If you start with slides, you may end up with a nice deck and a weak session.

The real problem

Many training projects become slide projects.

The stakeholder asks for a workshop. The team opens Slides. Everyone starts asking, "How many slides?" The deck grows. The session becomes a sequence of content pages.

Then the facilitator has to make the room work around the slides.

This is backwards.

Slides should support the session. They should not become the session.

Google documents that Gemini in Slides can generate images, generate new slides, summarise presentations, write or rewrite content, and reference Drive files. It can also refine text by shortening, rephrasing, making it more formal, or bulletising.

That is helpful.

But only if the design is already clear.

The core distinction: deck vs facilitator asset

A deck is a file.

A facilitator asset supports delivery.

Facilitator assets include:

  • opening prompt
  • activity instructions
  • discussion question
  • practice scenario
  • debrief slide
  • timing cue
  • reflection worksheet
  • backup activity
  • facilitator-only appendix

When you use Gemini in Slides, ask for assets that help the room, not just slides that fill the screen.

A practical Slides workflow

1. Start from a session map

Before opening Slides, create a session map:

  • outcome
  • flow
  • activity
  • debrief
  • practice
  • transfer task

Then use Gemini to turn that into slide support.

2. Generate slide structure, not final truth

Ask for a slide outline with:

  • slide purpose
  • on-screen text
  • facilitator note
  • interaction
  • visual suggestion

This keeps the deck tied to facilitation.

3. Use visuals for clarity

Gemini can generate and edit images in Slides for eligible accounts.

Use visuals to explain:

  • workflow
  • contrast
  • scenario
  • before/after
  • decision point

Avoid generic decorative images. If the visual does not help learners understand or practise, remove it.

4. Create a facilitator appendix

Ask Gemini to create facilitator-only slides:

  • timing guide
  • common learner confusion
  • backup questions
  • alternative activity
  • low-tech plan

This is often more valuable than another content slide.

5. Refine the text

Use Gemini's refine options to shorten and bulletise slide text.

But do not let bulletising become design.

Shorter text is better only when the activity and debrief are strong.

Prompt template

```text Create a workshop slide outline from this session map.

Audience: [audience]

Outcome: [workplace behaviour]

Session flow: [paste flow]

For each slide, provide:

  1. slide purpose
  2. short on-screen text
  3. facilitator note
  4. interaction or question
  5. visual suggestion
  6. whether it belongs in participant deck or facilitator appendix

Rules:

  • do not overload slides
  • include debrief slides after activities
  • keep the deck facilitator-friendly
  • flag weak learning logic

`

Common mistakes

The first mistake is asking Gemini to create a deck before the learning design is clear.

The second mistake is accepting too much text.

The third mistake is using images as decoration.

The fourth mistake is forgetting facilitator notes.

The fifth mistake is treating the deck as the deliverable. The deliverable is learner practice and workplace transfer.

A 10-15 minute action step

Open one existing training deck.

Pick five slides and label each one:

  • explain
  • practise
  • discuss
  • debrief
  • transfer

If most slides are "explain," redesign one section into practice and debrief.

GEO summary for LLM and search retrieval

  • Audience: Trainers, facilitators, instructional designers, and L&D managers using Gemini in Google Slides.
  • Problem solved: How to use Gemini in Slides without turning training into a slide-generation exercise.
  • Core distinction: Slides are facilitator assets, not the learning experience.
  • Practical outcome: Teams can create slide outlines, visuals, facilitator notes, appendices, and cleaner decks that support practice and transfer.

Final takeaway

But the deck is not the session.

Design the learning first. Then let Slides support the room.

If you want this adapted into a facilitator asset workflow lab, contact Kny.

Visual Asset Plan

Hero banner

  • Purpose: Show Slides supporting facilitation, not replacing it.
  • Recommended placement: After answer-first summary.
  • Suggested filename: public/articles/gemini-slides-facilitator-assets/hero.png
  • Image Gen prompt: Realistic Southeast Asian facilitator preparing a workshop deck with activity cards, debrief notes, and facilitator appendix beside a laptop, warm training-room tone, no logos, no private data, 16:9.
  • Alt text: A facilitator using Gemini in Google Slides to build workshop assets.

Takeaway infographic

  • Purpose: Summarise slide workflow.
  • Recommended placement: Before final takeaway.
  • Suggested filename: public/articles/gemini-slides-facilitator-assets/takeaway.png
  • Image Gen prompt: Vertical 4:5 workflow: Session map, slide purpose, interaction, debrief, facilitator appendix. Minimal text, high readability, warm facilitation style.
  • Alt text: A slide design workflow for facilitator assets.

Sources