Selling Design: How to Present Work Effectively

Design presentation is a skill distinct from design itself. I know designers who produce exceptional work and consistently watch it get revised into mediocrity because they don't know how to present it. I also know designers whose work is competent but who are consistently trusted with significant projects because they present with authority and clarity.

Both skills matter. The presentation shapes how the work is perceived — and whether the work gets to succeed.

The Setup Before the Show

Before I show anything, I establish the criteria. I briefly recap the brief: what was the challenge, what were the constraints, who is the audience. This reminds the client of the context they gave me and frames what they're about to see.

Then I preview what I'm going to show: "I'm going to show you three directions that each take a different strategic approach to positioning this brand." This sets expectations and prevents the client from being surprised by the number of options or the approach.

Narrate the Intent, Then Show the Work

When I show a concept, I describe what I was trying to achieve before I show the visual. "This first direction prioritizes authority and permanence — I wanted something that would feel appropriate on a bronze nameplate as much as a website." Then I reveal the work.

This sequence matters. When clients see design without context, they react to the first thing they notice, which is often not the most important thing. Giving them the intent first frames what to look for.

Speak to Strategy, Then Craft

I present in two layers: first the strategic argument (why this direction is right for the brief), then the craft argument (how the specific formal decisions support that strategy). The client cares about the strategic fit; they may not have the vocabulary for the craft, but the craft argument demonstrates rigor.

This structure also anticipates the most common feedback problem: purely aesthetic reactions that have nothing to do with whether the design is solving the right problem.

The Recommendation

I give a clear recommendation. Not "here are three options" but "here are three options, and I recommend the first because reasons." The recommendation signals confidence and gives the client something to react to.

A client who has to make a choice from three apparently equal options will often choose based on personal preference, which may not be the best strategic choice. A designer who has a recommendation based on strategic reasoning is more useful.

What to Do With Feedback

When feedback comes in, I listen completely before responding. Then I ask clarifying questions: "Can you say more about what's not working?" Understanding the concern behind the feedback is more useful than responding to the surface complaint.

Some feedback is about strategy (the brief has changed, the positioning needs to shift). Some feedback is about taste (the client or their boss doesn't like it). These require different responses. Strategic feedback requires design changes. Taste feedback requires explanation and, sometimes, negotiation.