How I Present Logo Concepts Without Getting Destroyed in Feedback

The Presentation Is Part of the Design

I used to think that good work would defend itself in a presentation. Just show the logo, and if it's strong, the client will see it. I was wrong repeatedly before I figured out what was actually happening.

Clients don't evaluate logos in a vacuum. They evaluate them in the context of everything said before, during, and around the presentation. If that context is wrong — if the presentation creates the wrong expectations, asks the wrong questions, or invites the wrong kind of response — even strong work can get a weak reception.

Presentation is a design problem. Treat it like one.

Strategy Before Visual

The single most effective change I made to my presentation process: I explain the strategy before I show the visual. Not as a disclaimer. Not as a preamble. As a genuine framing of the problem and the approach.

I describe what the brand needs to communicate, who the audience is, what the competitive context looks like, and what the design direction is trying to achieve. I take three to five minutes doing this, with slides if the project warrants it.

Then I show the logo.

This sequence does something important: it replaces "do I like this?" with "does this solve the problem?" The client has a framework for evaluation that's more useful than personal taste.

Showing Context, Not Just the Mark

I never show a logo in isolation on a white slide as the primary presentation. I show it in context first.

A business card. A sign. A tote bag. A website header. A social media avatar. The client sees how the mark performs in the world, not how it looks as a design artifact.

Context creates connection. A logo on a white slide is abstract. A logo on a business card being handed to a client's dream customer is real. I want the client to see the real version.

How Many Concepts to Show

I show two or three concepts, never more. More than three signals that I'm not sure what's right and I'm outsourcing the decision to the client. That's not what they hired me for.

Each concept is a complete thought — a direction with a rationale, not just a logo option. I explain why each direction exists and what brand problem it's trying to solve. I don't hide which direction I prefer. I tell them, with my reasoning.

Clients almost always go with the designer's preferred direction when the designer has a clear, well-reasoned preference. That preference communicates confidence. Confidence is persuasive.

Handling the "Can We See More Options?" Request

When a client asks for more options, I don't immediately produce more options. I ask questions first.

What specifically isn't working about the directions shown? Is it the concept, the execution, or the overall aesthetic? Is there a specific need that none of the concepts address?

Usually these questions reveal that the real issue is something addressable in the existing concepts — a refinement, a development of a direction, a different application context. Producing more distinct concepts rarely solves the problem. Developing the right concept usually does.

Documenting the Approved Direction

When a direction is approved, I document exactly what was approved: which version, which color, which application contexts. I get written confirmation.

This is not bureaucratic self-protection. It's professional clarity. Scope discussions and direction reversals are more common than they should be, and clear documentation prevents them.

The presentation ends when the next step is clear and agreed upon. That's the goal.