Presenting design work to a client has two jobs. The first is showing the work. The second is setting the terms on which feedback is given, and it happens before the work appears on screen. A presentation that does only the first job produces a room full of people improvising improvements out loud, because nobody told them what they were being asked to decide. A presentation that does both produces a decision. The difference is not charisma or slide quality. It is whether the frame was set while the work was still hidden.
Why the Room Starts Redesigning
A client who starts moving type around in their head is not being difficult. They are filling a vacuum. When work appears with no stated criteria attached, the only question available to a viewer is "do I like it," and the only way most people know how to answer that question is by suggesting changes. Liking something is not a decision anyone can act on, so they reach for the nearest actionable thing, which is an edit.
This gets worse the more senior the room. A marketing lead who has been asked for an opinion will produce one, at length, because producing opinions is part of their job. Nobody in that room is behaving badly. They are answering the question they were given, and the question they were given was the wrong one.
Working solo makes this sharper. On a team, an account lead absorbs the wandering conversation and quietly steers it back, then writes up what was actually agreed. Running the project alone, you are presenting and moderating at the same time, and moderating is the harder of the two. The way to make it manageable is to do most of it in advance, in the first ninety seconds, before there is anything on screen to react to.
The Sequence: Problem, Criteria, Work, Decision
Four beats, in that order.
Problem. Restate what the client hired you to solve, in their words where possible, drawn from the brief. This is not throat-clearing. It reestablishes the standard the work is about to be judged against, and it moves the room from taste to purpose.
Criteria. State how you will know the work succeeded. Two or three specifics from the brief. If the brief said the mark has to survive being embroidered at a small size, say so now. Criteria stated after the reveal sound like an excuse. Criteria stated before it sound like a standard.
Work. Show it. Let it sit in silence for a beat longer than feels comfortable, because the first person to speak sets the tone and you want that person to be you.
Decision. Ask for the specific decision you came to get.
| Beat | What it does | What happens if you skip it |
|---|---|---|
| Problem | Moves the room from taste to purpose | Feedback becomes personal preference |
| Criteria | Gives the room a standard to judge against | The only available question is "do I like it" |
| Work | Presents the actual deliverable | Nothing to decide on |
| Decision | Converts a conversation into an outcome | The call ends with no agreement and a full inbox |
Most solo presentations include the third beat and skip the other three. That is the whole failure.
Naming the Decision Before the Reveal
The single highest-leverage sentence in a design presentation is the one that says what you are asking for. It goes before the work, not after.
"I am going to show you two directions. What I need from you today is which one we develop, not a list of changes to either. The changes come next week once we have picked a lane."
That sentence does three things at once. It tells the room the scope of their authority in this meeting. It gives them permission to withhold detailed notes, which most clients are relieved to be given. And it makes a wandering conversation easy to redirect without anyone losing face, because you are not overruling anybody, you are pointing back at something you both already agreed to a minute earlier.
Compare it to the default opening, which is some version of "so here's what I came up with, let me know your thoughts." That sentence invites exactly the meeting the reader is trying to avoid.
When It Happens Anyway: Three Recovery Sentences
It still happens. A stakeholder starts specifying. You need a way back that does not read as defensive. Three moves, in escalating order.
Capture and park. "That's a good note, let me write it down for the revision round so we don't lose it." You have acknowledged the person, recorded the note, and moved the conversation off it. Most live redesigning stops here, because the underlying need was to be heard.
Return to the criterion. "Before we change the layout, can I check it against the thing we said mattered most, which was that this reads at a glance on a phone?" This is not a rebuttal. It is a request to test the suggestion against a standard the client set. Sometimes the suggestion passes, and you have learned something.
Reset the meeting's scope. "I want to make sure we leave today with a direction chosen, because that's what unblocks the next two weeks. Can we come back to the type once we know which of these we're building on?" Used once, this lands as competence. Used three times in one call, it reads as stonewalling, so it is the last resort rather than the first.
None of these require you to disagree with anyone. That is deliberate. A solo designer arguing with a client's suggestion in front of the client's colleagues is spending relationship capital to win a point that a written follow-up would have won for free.
Live Presentation Versus Sending It Over
These are two different jobs and they run on different rules. Presenting live lets you set the frame, control the order things are seen in, and read the room. Sending work over means the frame has to survive without you in the room, which means it has to be written down.
If the work is going over asynchronously, the four beats do not disappear. They become the message that accompanies the file: what the problem was, what the criteria are, what is attached, and what decision you need by when. A file sent with "let me know what you think" is the asynchronous version of the presentation that loses the room, and it fails more completely, because you are not there to recover it. Whether a given round needs a live call at all is a separate judgment, and it depends more on how contested the decision is than on how important the work is.
One thing worth deciding in advance either way: how many directions are going into the room, because that number changes the shape of the whole conversation. A room asked to choose between three things behaves very differently from a room shown one recommendation, and the reasoning behind how many design concepts to present is worth settling before the meeting is booked. So is the question of whether the work is being shown flat or in context, since presenting in context with mockups changes what the client believes they are approving.
What Has to Be in Writing When the Call Ends
The call is not the record. The recap is the record.
Within a few hours, send a short written summary: the decision that was made, the notes that were captured and parked, anything that was explicitly deferred, and what happens next with a date on it. This is the substitute for the project manager an agency would have, and it is the cheapest insurance in the whole process, as the wider solo design project process covers stage by stage.
The recap also solves a problem that shows up later. A client's memory of a meeting drifts, usually toward whatever they were thinking about on the drive home rather than what was agreed in the room. A written recap does not prevent that drift. It just makes correcting it a two-line email instead of a redone concept.
Once a direction is chosen, the next task is getting feedback that is specific enough to act on, which is a skill of its own and mostly a matter of how you ask clients for design feedback rather than how patient they are. And if the direction being presented came out of a reference-gathering stage, it is worth being clear with yourself about what a moodboard was actually for, because a client who approved a moodboard has not approved a concept.
FAQ
How do you present design work to a client?
In four beats: restate the problem, state the criteria the work should be judged against, show the work, and ask for the specific decision you need. The first two beats happen before anything appears on screen, and they are what stops the meeting turning into a live redesign.
What do you say at the start of a design presentation?
Restate the brief and name the decision you are asking for. Something like "I am going to show you two directions, and what I need today is which one we develop, not detailed changes to either." That single sentence sets the scope of the meeting.
How do you stop a client from redesigning your work in the meeting?
Capture the suggestion in writing and park it for the revision round, then return to a criterion the client themselves set. Most live redesigning is a request to be heard, and acknowledging the note in writing usually ends it without any disagreement.
Should you present design work live or send it over?
Both work, but they need different preparation. Live lets you set the frame and read the room. Sending it over means the frame has to be written into the message, including the decision you need and by when, because you are not there to steer the reaction.
What should you send after a design presentation?
A short written recap: the decision made, the notes parked for later, anything deferred, and the next step with a date. The meeting is not the record. The recap is.