Open your company's shared drive and search "template." On most teams that search returns somewhere between twelve and forty files — old brand decks, a "final_v3" someone built for one pitch in 2022, a regional office's own version nobody signed off on, three separate "official" title slides. Ask five people which one is current and you'll get five different answers, usually all wrong.

The instinct when this gets noticed is to add more structure: a template governance doc, a naming convention, a Slack channel for "approved assets." I've watched that fix fail more often than it works, for a simple reason — it treats the problem as too little organization, when the actual problem is too many templates competing for the same slot. The fix isn't a better filing system. It's deletion.

The math nobody runs before adding another template

A design lead at a mid-sized agency once told me their shared drive held 34 PowerPoint templates. Thirty-four. When we counted how many were actually used in the last quarter, it was four. The other thirty weren't backups or specialized edge cases — they were forgotten forks of the same four, kept alive because deleting a file feels riskier than leaving it.

That instinct is exactly backwards. Every unused template sitting on a shared drive is a live option the next person under deadline pressure might grab instead of the current one — and they usually can't tell the difference by looking at the thumbnail. An industry-wide survey by empower, published in its Global PowerPoint Study, found that employees lose roughly 2.6 hours a week to PowerPoint time-wasters like searching for the right template version and reformatting inherited slides — and that close to half of all presentations produced inside a company don't actually follow that company's own design guidelines. Multiply that gap across a year and you get dozens of off-brand decks per employee, not because people are careless, but because there was never really one template to follow — there were several, and picking wrong was easy.

Why "just add more guidelines" makes the sprawl worse

The natural response to messy templates is a brand guidelines document explaining which template to use when. I wouldn't recommend this as a first move. A guidelines PDF competes for attention with the actual deadline someone is working against, and in that competition the deadline wins nearly every time — so the guideline gets skimmed once, ignored forever, and the old templates stay right where they were, still downloadable, still confusing.

What actually changes behavior is removing the wrong options rather than documenting which one is right. If there's only one template file anyone can find, there's nothing to guess about. This sounds almost too simple to be a real strategy — and it is simple, which is exactly why it works better than a policy document that assumes people will read it before a 4pm deadline.

What "90%" actually means in practice

The 90% figure isn't a precise measurement — it's a useful exaggeration pointing at a real pattern I keep seeing: most organizations have one, maybe two templates doing real work, and everything else is a variant, a duplicate, or a relic from a rebrand three years back that nobody archived properly. When a company actually audits its templates, the survivors usually fall into a short list:

  • The current master deck template, actively maintained
  • One lightweight variant for internal-only decks that don't need full brand polish
  • Maybe a client-facing proposal template, if that's structurally different enough to earn its own file

Everything past that third item is usually a candidate for deletion, not preservation. That includes the "just in case" templates — the ones someone insists on keeping because a specific project might need that exact layout again. In my experience, that project rarely comes back, and if it does, rebuilding one slide from scratch takes less time than the confusion caused by keeping ten dormant options around for a year.

The exception that actually complicates this

Here's where it gets less clean than "delete everything but one file." Multi-brand companies, agencies serving different client verticals, and organizations with genuinely separate audiences — investors versus internal ops versus regulators — often do need more than one template, and collapsing those into a single file creates a different problem: a template stretched thin enough that it fits none of its use cases well. A template built around what a specific audience expects to see isn't sprawl — it's doing a job a generic one can't.

The distinction that matters is whether a second template exists because the audience genuinely needs a different structure, or because nobody wanted to be the person who deleted someone else's file. Those look identical sitting in the same folder. They're not identical in what they cost you.

How to actually run the deletion, without breaking anything important

Don't start by deleting. Start by checking which templates were opened, edited, or exported in the last two to three months — most file storage and DAM tools log this. Anything untouched in that window is very unlikely to be load-bearing for someone's workflow, whatever the file name suggests.

From there, the sequence that's worked for me:

  • Archive, don't destroy, for the first round — move candidates to a clearly labeled "legacy" folder outside the main template path rather than deleting outright, in case something surfaces
  • Announce the single remaining template's location in whatever channel people actually use for urgent things, not just the wiki page nobody opens
  • Wait one full reporting cycle before permanently removing the archived versions — if nobody asks for them, that's your answer

This is slower than a mass delete, and that's the point. The goal isn't to look decisive, it's to make sure the one template left standing is actually the right one — which means it needs to hold up under real content, not just the sample slides it shipped with. A template that looks clean with placeholder text and falls apart the moment someone pastes in a dense quarterly table isn't ready to be the last one standing; it just means you've swapped a sprawl problem for a single-point-of-failure problem.

What replaces the deleted templates

Once the shelf is cleared, the remaining template needs to actually be good enough to survive being the only option — flexible layouts for text-heavy and chart-heavy content, placeholder guidance instead of blank boxes, and structure that holds up past slide five. That's usually the moment teams either commit real design time to their single surviving template or go looking for a professionally built starting point rather than patching an internal file that was never designed to carry the whole company. For a genuine multi-brand situation, a custom-built template system tends to hold up better than trying to force one generic file to serve three different audiences at once.

The next time someone proposes a new template for a specific use case, ask what's getting retired to make room for it. If the honest answer is "nothing," that's usually the moment the sprawl starts over.