When Copilot arrives in an organization, in-house designers often hear one question underneath all the others: does this replace us?
It is the wrong question, but it deserves a straight answer. Copilot takes over a category of work that designers have long carried and rarely enjoyed: the routine internal deck. It does not take over the work that needs judgment, and it creates a new category of work that only designers are equipped to do well. The teams that do best are the ones that redraw the line on purpose, rather than waiting for it to move on its own.
Three kinds of presentation work
It helps to stop thinking about “presentations” as one kind of work. In most organizations, there are three.
Routine decks. Weekly updates, project status, team meetings, internal briefings, first drafts. High volume, moderate stakes, repetitive structure. Historically these either consumed designer time or were built badly by the people who needed them.
Decks that matter. Board presentations, investor materials, keynotes, major pitches, executive announcements. Lower volume, high stakes, specific audiences. Their difficulty is the argument and the emphasis, not the formatting.
The system. The template, its example slides, the Brand Kit, and the written rules that decide what everyone else produces. Historically this was a periodic project — a rebrand, a template refresh. With Copilot it becomes an ongoing responsibility.
Who should do each
| Work | Who drafts | Who decides | Designer’s role |
|---|---|---|---|
| Routine decks | Employees with Copilot | Employee | Designs the system they draw on |
| Decks that matter | A designer, often starting from a Copilot draft | Presenter and designer together | Structure, emphasis, craft |
| The system | Designers | Brand manager | Owns it |
The shift is in the first row. Routine decks move from “designer builds it” or “employee struggles with it” to “employee generates it from a system designers built.” The designer’s influence doesn’t disappear. It moves upstream, into the template and rules that shape thousands of decks instead of dozens.
Why the system is design work
There is a temptation to treat Copilot setup as an IT task. The settings are. Designating brand managers, uploading a template, switching on strict brand adherence — an administrator can do those in an afternoon.
But what Copilot learns from is not the settings. Microsoft’s guidance is that Copilot learns primarily from a template’s sample slides, uses placeholder type, position and size to place content, and draws colors and fonts from the theme. It recommends example slides across the slide types an organization actually uses — agendas, data, timelines, processes, quotes, summaries — at light, medium and heavy densities, showing how the brand uses color, typography and imagery.
That is a body of design work. Deciding which slide types the organization actually needs, designing examples that demonstrate good hierarchy and emphasis, sizing placeholders for real content, choosing when a full-bleed image is right and when an inset works better — these are the judgments designers make every day. The difference is that each example now teaches a model, and the model applies the lesson at scale.
What designers get back
When routine decks move to Copilot, the most immediate change is time. The weekly request for “just tidy up these slides” becomes less frequent, because the slides come out of Copilot already in a usable structure and the brand’s visual language.
That time is worth redirecting deliberately, toward:
- The decks that matter, which rarely got enough attention when the queue was full of routine work.
- The system, which now determines the quality of everything else.
- Review, especially early on: looking at what employees actually generate, spotting patterns in what goes wrong, and fixing the template or rules rather than fixing slides one at a time.
That last one is a real change in how designers work. Fixing a slide helps one deck. Fixing the example slide that taught Copilot the mistake helps every future deck.
What to say to your design team
If you lead a creative team, a few messages are worth being explicit about:
- The routine queue will shrink, and that is the point. Nobody’s value was in reformatting status updates.
- You own the system. The template, the examples and the rules are design assets, and the brand manager relies on you to make them good.
- Your approval matters more, not less. Every example slide in the template is a pattern Copilot will repeat. Designers should approve them.
- The decks that matter still need you. Generated first drafts can make those projects faster to start; the decisions still need a designer.
We would avoid framing any of this as “doing more with fewer designers.” That framing tends to produce a team that resists the system. Framed as “stop producing routine decks and get the strategic work back,” the same change is usually something designers ask for.
A practical first step
Take last month’s design requests and sort them into the three categories: routine, decks that matter, system. You may find the routine pile is larger than you expected. That pile is the opportunity — and the template Copilot learns from is how you capture it.
Common questions
Will Copilot reduce the need for in-house designers?
It changes what designers spend time on more than whether they are needed. Routine decks move toward employees working from a well-built system; the template, its example slides, the written rules and the decks that matter all still need design judgment. Microsoft describes sample slides as Copilot’s primary learning source, and designing those is skilled work.
Should designers edit generated decks or fix the template?
Both, but in different proportions than before. For a high-stakes deck, editing the deck is right. For a problem that keeps recurring across many generated decks, fixing the example slide, layout or rule that caused it is far better value, because the fix applies to every future deck.
Who should approve example slides?
Designers should create them and whoever owns the brand should approve them. Every example is a pattern Copilot may repeat at scale, so approval deserves the same care as approving a campaign asset.
Key takeaways
- There are three kinds of presentation work: routine decks, decks that matter, and the system.
- Copilot takes over routine decks; designers move upstream to design the system everyone draws on.
- What Copilot learns from — example slides, placeholders, theme — is design work, not an IT setting.
- Fix patterns in the template, not slides one at a time.
- Keep designers on the decks that matter, and on approving the examples Copilot will repeat.
Want your designers’ judgment built into what Copilot learns from? Have your template scored.**
Related reading
- What Copilot in PowerPoint still can’t do
- From prompt to deck: what happens when Copilot creates a presentation
- The brand manager role in Microsoft 365, and why someone must own it
Sources
- Microsoft Support, Keep your presentation on-brand with Copilot (July 2026)
- Microsoft Support, Manage template settings in your Brand Kit for Copilot in PowerPoint (August 2026)