A CEO I worked with years ago used to open every Monday meeting the same way: "Skip the deck. Just tell me what's true." His team hated it for about three months. Then something shifted — the meetings got shorter, the arguments got sharper, and the follow-up emails asking "wait, what did we actually decide?" mostly stopped. Nothing about the business changed. What changed was the format standing between the information and the decision.

This isn't really a story about slides being bad. It's a story about what slides are quietly optimized for, and why that thing — persuasion, polish, narrative control — is often the opposite of what a recurring internal meeting needs.

The Deck Was Never Built for This Room

Slides were designed to persuade an audience that hasn't seen the material before: investors, prospects, a board meeting once a quarter. A weekly team sync is a different animal. The people in the room already share context. What they're missing isn't a narrative arc — it's the three numbers that moved since last week and a decision on what to do about them.

I've sat through enough of these meetings to notice the pattern: someone spends fifteen minutes building a deck to explain something that would take four sentences in a written update. The deck isn't adding clarity. It's adding a presentation layer to information that didn't need one — and the person building it usually knows this halfway through, but builds it anyway because "that's how we do updates here."

What Actually Replaces the Slides

The teams that drop decks from weekly meetings don't replace them with nothing — they replace them with a short written document, read silently at the start of the meeting, followed by discussion. Amazon's well-documented shift to six-page narrative memos instead of PowerPoint for internal reviews is the most cited version of this, but the underlying mechanic shows up in smaller companies too: a one-page status note, a shared doc with three sections, a Slack thread with the week's numbers pinned at the top.

The mechanism is the same regardless of format: writing a sentence forces a decision that a bullet point lets you avoid. "Revenue is down" fits on a slide. "Revenue is down 6% and I don't yet know if it's seasonal or a churn problem" does not fit comfortably into three words next to a bullet — so the person writing it has to actually think it through before the meeting starts, not during it.

What the Data Actually Says About Where CEO Time Goes

It's tempting to assume this is a minor scheduling preference. It isn't, once you look at how much of a leader's week meetings actually consume. A Harvard Business School study tracking 27 CEOs across roughly 60,000 logged hours found that these executives spent an average of 72% of their working time in meetings, attending around 37 meetings a week — and the majority were small, with 42% one-on-one and another 21% involving two to five people.

That last detail matters more than the headline number. Most of a CEO's meeting time isn't spent in large, formal, deck-worthy settings — it's spent in small rooms making fast calls. A slide deck built for a room of twenty doesn't fit a conversation between two or three people who already know the context. Building one anyway is a format mismatch dressed up as diligence.

Where This Breaks — and It Does Break

Here's the part most "kill your slides" advice skips over: a no-deck policy works cleanly when the update is narrative and the room is small. It works far less cleanly the moment a meeting's real content is comparative numbers — a funnel across five regions, a project timeline with dependencies, a quarter-over-quarter cost breakdown. Reading "conversion dropped in three of five markets" out loud is not the same as seeing which three, by how much, and since when.

This is the trade-off nobody wants to admit when they're evangelizing the no-slide approach: written narrative is excellent at forcing clarity of thought, and genuinely bad at showing relationships between numbers or timing across many moving parts. A board update on a construction project's twelve-month phasing, or a leadership review of pipeline health across a dozen accounts, loses real information when it's flattened into prose. In those specific cases, a tight chart or a single timeline slide — not a full deck, one visual — communicates in five seconds what a paragraph would take five minutes to describe, and describe worse.

The distinction that actually matters isn't "slides versus no slides." It's whether the update is a decision that needs a sentence, or a pattern that needs a shape. Teams that get this right tend to keep a small, reusable set of status timelines or dashboard charts on hand for the recurring numbers that genuinely need a visual, and drop the deck-building habit for everything else — rather than treating "no slides" as a blanket rule that quietly starts costing them clarity on the one meeting a month where a picture really was worth the paragraph.

Running It Without Losing the Room

Switching a recurring meeting away from slides isn't free of friction, and pretending otherwise sets the change up to fail. The first few sessions tend to run long, because people who are used to a deck's built-in pacing don't yet know how to structure a written update on their own. One thing people overlook here: give the written format a strict length limit from day one — a half-page cap works better than "keep it short," because vague guidance just gets replaced by a different kind of bloat.

I wouldn't recommend making this switch for a meeting that already runs well. The value shows up specifically in meetings that have become deck-building rituals — where more time goes into formatting the update than making the decision it's meant to support. If your Monday meeting still ends with people knowing exactly what changed and what to do next, the slides in the middle of it were never really the problem.

For teams that do need the occasional chart to make a number legible, a small library of ready-made visuals — pulled in only when the content actually calls for one, like these free chart templates — keeps the discipline of "no deck by default" from turning into "no visual, ever," which is its own kind of avoidable confusion.

So the next time someone on your team opens PowerPoint before a weekly sync, it's worth asking what they're actually trying to solve — clarity, or the appearance of having prepared. Those two things look identical from the outside. They rarely are.