The Logo Design Revision Process: How to Handle Feedback Well

Feedback Is Information

The first thing I remind myself when receiving logo feedback is that all of it is information, even the feedback I disagree with. Negative feedback tells me something about how the concept reads, what expectations it does or doesn't meet, and what the client values. I try to process feedback analytically before responding emotionally.

This is harder than it sounds after you've spent days on a direction. But it's essential to handling the revision process well.

Distinguish Feedback Types

Not all feedback calls for the same response. Some feedback identifies a genuine design problem — "this mark looks too similar to a competitor" is a design issue that needs to be solved. Some feedback expresses a preference that doesn't have a right or wrong answer — "I'd like it to feel warmer" is direction I can work with. Some feedback is really a symptom of a deeper concern — "can we make it bolder" might actually mean "this doesn't feel confident enough for our positioning."

I try to identify which type of feedback I'm receiving before deciding how to respond. The first type should be fixed. The second should be explored. The third requires uncovering the underlying concern.

The Clarifying Question

When feedback is ambiguous, I ask clarifying questions. "When you say warmer, what are you comparing it to?" or "What specifically feels like it's missing?" These questions aren't pushback — they're the fastest way to understand what's actually needed.

Iterating on feedback I haven't fully understood wastes both parties' time and produces work that misses the mark.

When to Push Back

Sometimes client feedback points in a direction I believe is wrong. I push back — once, clearly, with my reasoning. If a client wants to add complexity to a mark I believe is working well, I'll explain why I think the simplicity is an asset and what specifically I think would be lost.

Then I execute what they've asked for. My job is to give my best professional judgment and then serve the client's final decision. Not to fight for my preference indefinitely.

Keeping Scope in Mind

Revision rounds should be scoped in the project agreement. Unlimited revisions aren't sustainable, and they also produce worse outcomes — the work cycles endlessly without converging. Clear revision scope creates a deadline that helps both parties make decisions.

When a project approaches the revision limit, I flag it explicitly and have a conversation about scope extension if needed. Surprise scope overages are avoidable.

The Version Archive

I save every version of every mark developed over the course of a project. Clients sometimes return to directions they previously rejected. References from earlier explorations are often useful in later stages. A well-organized archive makes the whole process more efficient.

Never delete early explorations. The design history is part of the project.