A junior associate spends a weekend building a 40-slide deck packed with every chart the team produced. A partner spends three hours cutting it down to nine slides and one number per page. Ask which deck cost more to make, and most people guess wrong — they assume the 40-slide version, because it clearly took longer to fill. It didn't. The nine-slide version is the one that actually cost money, because someone senior enough to be expensive spent their time deciding what to throw away.

That's the part the usual "less is more" advice skips. It treats simplicity as a taste — a style someone with a good eye happens to prefer. In practice, a stripped-down deck is almost always the output of a more expensive production process than a busy one, not a cheaper one. Understanding why changes what you actually try to fix when your own decks feel bloated.

Cutting a slide is a decision someone has to be authorized to make

Adding a slide requires no permission. Anyone on a team can drop in another chart, another logo, another "just in case" bullet, and nobody has to sign off on it — it's additive, low-risk, and reversible. Removing a slide is a different act entirely. It means someone is willing to say, out loud, "the thing you spent two days building isn't going in," and stand behind that when the person who built it asks why.

That's precisely the decision most people building a deck aren't senior enough, or don't feel safe enough, to make on their own. Most of what quietly bloats a corporate deck survives for exactly this reason — not because anyone thought it improved the presentation, but because cutting it felt like a confrontation nobody wanted to have in a meeting. The slide that should have been deleted three drafts ago is still there because deletion has a social cost that addition doesn't.

An external design process buys that authority as a byproduct. A consultant or senior designer has no stake in whose chart survives — they can cut without it reading as a rejection of a colleague's work, which is precisely what makes the output look edited rather than accumulated.

In-house decks default to more, because more feels safer

I've watched the same pattern play out inside teams building their own decks without outside help: when nobody's sure exactly what the room will ask about, the instinct is to prepare for every possible question rather than commit to the three that actually matter. That produces a deck that's technically comprehensive and functionally unreadable — every slide is a hedge against being caught unprepared, not a step in an argument.

A deck built by someone paid specifically to make it work doesn't hedge that way, because hedging isn't their job — clarity is, and they're not the one who has to answer follow-up questions live in the room. That's a structural difference in incentive, not a difference in design skill. The in-house version optimizes for "nothing gets left out that could be asked about." The paid version optimizes for "the argument lands in the time available," and everything that doesn't serve that gets cut regardless of how much work went into it.

The revision math nobody budgets for

A dense, first-draft deck typically goes through one or two passes before it ships — a spelling check and a template swap. A deck that ends up looking deliberately simple usually went through far more rounds than that, most of them invisible in the final file: an early version with twice the content, a middle version where someone argued for keeping a chart that eventually got cut, a final pass purely to see if any slide could be removed without losing the argument.

Each of those rounds costs time from someone whose time is expensive — which is the actual mechanism behind "simple looks expensive." It's not that white space signals money. It's that reaching a genuinely minimal version requires paying for iteration that a first-draft deck never gets. The visual cue people read as "premium" — one color decision instead of five competing ones — is downstream of that process, not a substitute for it. Strip the colors off a deck that never went through real editing and you get a plain-looking version of the same unfocused argument, not a polished one.

Complexity isn't the enemy — unpaid-for complexity is

None of this means dense decks are automatically wrong. A due-diligence data room, a technical spec review, a multi-region performance breakdown — these genuinely need more on the page, and the same logic that governs how many colors a chart needs applies to how much content a slide needs: the right amount is whatever the reader's job actually requires, not a fixed ceiling borrowed from a different kind of deck. A reference document someone will reopen to check a number has a different job than a pitch trying to move a room toward one decision in twenty minutes, and treating both as "should be minimal" is its own kind of category error.

There's research behind the general direction, even if it doesn't map onto presentations one-to-one. Work on visual complexity and perceived trust in online interfaces, presented at an HCI International conference, found that heavier image-based visual complexity tended to lower how credible a page was judged to be — while complexity in the actual text content had the opposite effect, reading as more trustworthy rather than less. The distinction matters more than the headline finding: it's decorative complexity that erodes credibility, not informational density. A slide with five genuinely necessary numbers isn't the problem. A slide with five numbers and a stock photo probably is.

What this actually means for a deck you can't outsource

You don't need a five-figure design retainer to buy the thing that actually produces a simple deck — you need to budget the editing pass, not just the building pass, and give someone explicit permission to cut slides without it being a fight. In practice that means finishing a first full draft earlier than feels comfortable, so there's real time left over for a second person to go through it asking "does this slide need to exist" rather than "does this slide look right." Starting from a structure that's already doing some of that work — a template built around one argument per slide rather than a blank deck that invites accumulation — buys back some of the time that editing pass needs, which is often the actual constraint, not design taste.

Go back to that partner cutting forty slides down to nine. The associate wasn't a worse presenter. They just never got the budget — in time, seniority, or permission — to do the part of the job that doesn't show up as new content: deciding what doesn't survive.