Most people pick a presentation template by scrolling until something looks good. That works until the deck is half-built and the layout starts fighting the content — a slide that only holds three bullets when you need six, a chart placeholder sized for two series when you have five, a cover that assumes a short company name.
Choosing by use case avoids most of that, because the constraints come from the room rather than the aesthetic. A board read-out and a classroom lesson can share a colour palette and still need completely different layouts: the board deck wants density and a recommendation up front, the lesson wants one idea per slide and space to breathe.
Three questions worth answering first
Who is in the room, and what do they need to do? An audience that has to decide something needs your conclusion early. An audience that has to learn something needs it last, after the reasoning. That single difference reorders the whole deck.
How will it actually be viewed? A deck read alone on a laptop can carry far more text than one projected in a bright room or shared over a video call. If it will be forwarded rather than presented, the slides have to make sense without you narrating them.
What has to survive editing? Templates that depend on licensed fonts fall back to a default the moment the file opens on another machine, which breaks every layout built around them. If the deck will pass between PowerPoint, Keynote, and Google Slides, favour web-safe families and effects that all three render the same way.
Where to start
Each page below covers one context: what the audience expects, which layouts earn their place, and the mistakes that show up most often. The guidance applies whether you use one of our templates or build from scratch.