Asking for a judgement, not a preference

Approval is a separate skill from the work

Good work gets rejected constantly, and usually not because the client has bad taste. It is rejected because it was presented in a way that invited a preference rather than a judgement, or because it arrived cold in an email at 6pm on a Friday, or because the client did not know what they were supposed to be assessing.

This is learnable and it is not manipulation. A presentation’s job is to put the viewer in a position to evaluate the work against the problem, rather than against whatever they happened to imagine.

The order that works

1. Restate the problem. Thirty seconds. Their words, from the kickoff. “You said the shutter needs to make people who have walked past for six years look at it again, and that it has to survive being repainted every monsoon.”

This does more than anything else in the presentation. It moves the client from do I like this to does this solve that, which are different questions with different answers.

2. State the criteria. “So I was judging every route on whether it reads at four metres, whether it survives a two-colour print, and whether it still looks like the same shop.” Now the client knows what they are being asked to assess.

3. Show the work. Large, in context, in silence for a few seconds before you speak. Let them look.

4. Explain the decision, not the process. One or two sentences about why this solves the stated problem. Not what software you used, not how many versions there were.

5. Ask a specific question. Not “what do you think?”, which produces a reflexive opinion, but “does this feel like your shop to you?” or “would your regular customers recognise it?”. A specific question produces usable feedback.

How many routes to show

Fewer than you want to. One, or at most two different directions.

Showing three routes seems generous and is usually a mistake. It communicates that you did not have a view, it invites the client to combine elements from each, which produces the compromise nobody would have chosen, and it triples the chance that they fall for the one you least want to make.

If you show more than one, show them as different answers to the problem and say which you recommend and why. Never include a weak option as a foil; it is transparent to anyone perceptive, and the alarming outcome is that it gets chosen.

Presenting live rather than sending

Whenever the project is large enough to matter, present the work with your voice attached: in person, or on a call with your screen shared. Then send the file afterwards.

The reason is specific. Work sent cold is evaluated by whoever opens it, in whatever mood they are in, without the problem restated and with no chance for you to answer the first objection. The first reaction to unfamiliar work is very often mild discomfort (that is what unfamiliarity feels like), and if nobody is there, that reaction becomes the written feedback.

When you cannot present live, record a three-minute screen video walking through it. Free tools do this well: OBS Studio records screen and voice on any platform. It is not as good as a conversation, and it is much better than an email with attachments.

The context problem

Show work at the size and in the situation it will exist in. A logo presented at 2000 pixels on a white screen is not the thing being bought; the thing being bought is 8mm on an invoice and 40 feet on a shutter.

The most common approval failure in identity work is that the client falls in love with the enormous version and is disappointed by reality. Show the small version in the same presentation. It also protects you: a client who approved the 8mm version cannot be surprised by it later.

Do not show what you cannot deliver

Anything in the presentation is a promise. A mockup with a foil finish the budget excludes, a photograph you do not have rights to, a typeface you have not licensed: every one of these will be expected in the final work, and explaining that it was illustrative is a conversation in which you look like you are withdrawing something.

When the room goes quiet

Silence after you present is normal and almost never negative. People are looking. The instinct is to fill it by talking, and talking at that moment is where presentations are lost: the freelancer starts qualifying, offers alternatives unprompted, and undermines the work before anybody has objected to it.

Count to ten in your head. Let them speak first.

If the first response is negative, resist defending immediately. Ask what specifically is not working, and whether it is the idea or the execution: those have completely different remedies, and clients frequently reject an execution while describing it as a problem with the idea.

Getting a decision

End every presentation with an explicit next step and a date. “Could you come back with consolidated feedback by Thursday? Then I will have the revisions to you by the following Wednesday.”

The word consolidated is doing real work. Feedback arriving in fragments from four people over ten days is the most common cause of revision overrun, and asking for one collected response, from one person, is a reasonable request that clients almost always accept when it is made at the right moment.

The limitation

Presentation cannot save work that does not answer the brief. A well-structured argument for a weak solution buys you one round, and the client’s dissatisfaction returns at the next stage with interest.

It also has less effect than people hope on a client who has already decided what they want and is looking for someone to produce it. A shop owner who came in wanting a blue logo with a swoosh may sit politely through a superb argument and then ask for the swoosh. Sometimes the honest outcome is to make the swoosh well, and the skill is knowing which of those situations you are in, which the restated problem, at the start, tends to reveal within the first minute.