Signing in

You will be sent to MillerKnoll sign-in.

AI

Why PowerPoint Beats Chat for Decks

Asking Copilot Chat or Agent Builder for a deck often makes things worse: you get a text outline or generic design that ignores MillerKnoll layouts, then spend the saved time fixing fonts by hand.

Lesson 1

The file is the constraint.

Copilot inside PowerPoint reads the file you have open — slide masters, named layouts, theme colors, fonts. When you start from the MK template, Copilot picks from layouts that already exist.

Use Chat upstream for brainstorming slide order or speaker notes from a Word brief if you want — but build the slides here, in PowerPoint, on the template file.

Core principles

  1. Template file is the source of truth — never start from a blank deck or generic Copilot theme.
  2. Layouts, not designs — tell Copilot to use only slide layouts already in the file.
  3. Brief before bullets — missing inputs become [Needs input] on the slide, not invented copy.
  4. Verify before you share — pricing, timelines, specs, and case references come from your brief or attached files.
  5. Treat every slide as a first draft you verify, not a client-ready deliverable.

Prerequisite: Copilot Basics — daily apps

Check yourself

Why does this lesson recommend building slides in PowerPoint rather than Copilot Chat?

Do this in Copilot

Name one client deck you rebuild often. Note whether you usually start from the MK template or a blank file.

Paste this into Copilot Chat and work through it before moving on.

Compare approaches

I need to update a client presentation for [MEETING TYPE]. List three risks of drafting the deck in Copilot Chat instead of Copilot in PowerPoint on the MillerKnoll template. Then one sentence on when Chat is still useful upstream.
Open Copilot →
  • Goal and context

Did you run this in Copilot? Mark complete when you have tried it.

Next lesson: Three Slides in Fifteen Minutes →