Send the deck before the meeting.

Process · 5 min read

I used to present everything live. Walk through the research report in real time. Reveal the wireframes screen by screen. Show the brand options one at a time. It felt like the right thing to do. Build the narrative. Control the reveal. Guide the client through the thinking.

Then a client told me they would have preferred to see everything beforehand. "If I'd had this the night before, I could have read it, thought about it, written down my questions, and come to the meeting ready to make decisions instead of trying to absorb everything in the moment."

They were right. And it changed how I run every project since.

Why live presentations waste time

When you present something live, you're asking the other person to do two things at once: understand the work and evaluate it. Those are different cognitive tasks. Understanding requires reading, absorbing, and connecting new information to what they already know. Evaluating requires critical thinking, comparison, and decision-making. Doing both simultaneously means doing both poorly.

The result is meetings that run long because half the time is spent on consumption. The client is reading slides you could have emailed. They're asking clarifying questions that would have answered themselves if they'd had twenty minutes to read the document first. And when you do get to the decisions, they're tentative because the client hasn't had time to properly think.

"Can I think about it and get back to you?" is the most expensive sentence in the design process. It pushes decisions to email threads that drag on for days. It delays the next phase of work. And it usually means the client made a gut-level decision in the meeting but isn't confident enough to commit to it out loud. If they'd seen the work in advance, they'd be ready.

What pre-work actually changes

When I send the materials in advance now, the meeting starts differently. Instead of "let me walk you through this," it's "what questions did you have?" The client has already absorbed the information. They've already formed initial reactions. They've circled things they like and flagged things that bother them. We skip straight to the productive part.

Meetings get shorter. A session that used to take ninety minutes takes forty-five. Not because we're rushing. Because we're not wasting time on information transfer that could have happened asynchronously. The meeting becomes a decision-making session, not a presentation.

This is especially important for clients who process information differently. Some people think better when they read. Some need to see things visually and sit with them. Some want to show the work to a partner or advisor before forming an opinion. Pre-sending gives everyone the space to engage with the material in their own way.

How to do it well

Don't just dump a file and say "have a look." Give context. Tell them what they're looking at. Tell them what decisions you'll need from them in the meeting. If there are two options, say so. If there's a section you're less confident about, flag it. Guide their reading so they arrive prepared, not overwhelmed.

I usually send the document with two or three specific questions. "Do you prefer option A or B for the navigation?" "Does the user flow on screen four match how your users actually think?" "Is there anything in the feature list that should be reconsidered?" That gives the client a job to do, not just a thing to read.

Try it once. Send the deck twenty-four hours before the meeting. Watch how the conversation changes. You'll never go back to live presentations.

Sources
What It Takes to Run a Great Meeting (Harvard Business Review) - Pre-distributing materials improves meeting effectiveness.
How to Run Stakeholder Reviews (Nielsen Norman Group) - Separating consumption from evaluation leads to better design feedback.

Related blog posts:

How to prepare for your first app design project →

Don't forget to do your homework →

Your first usability test should embarrass you →