By Mehdi HassanHow should you give feedback on logo concepts?
Give feedback on logo concepts by checking each one against the brief you agreed, in the contexts where it will live, and by describing what isn't working and why. A designer can fix a clearly stated problem in many ways. A request for a specific fix, like "make the icon blue", gives them one way, and it's often not the best one.
Logo feedback goes wrong more often than logo design does. Concepts that could have become strong marks get sanded down into safe ones through rounds of vague, conflicting or taste-driven notes. This guide gives you a script you can follow in your next review. For the bigger picture of how a startup logo comes together, start with our logo design guide for startups.
Why does "make it pop" make logos worse?
"Make it pop" makes logos worse because it describes a feeling without naming the cause, so the designer has to guess. The usual guesses are brighter colors, gradients, shadows or extra detail. Those make a logo louder on a big screen and weaker everywhere else: in a browser tab, in one color, on a dark background.
Vague notes like this usually hide a real issue. "It doesn't pop" might mean it's hard to see at small sizes, it looks like a competitor, it feels too quiet for a consumer brand, or the wordmark is too light next to the symbol. Each of those has a different fix. Your job in feedback is to find the real issue and name it.
Instead of saying | Try saying |
|---|---|
Make it pop | It disappears next to competitor logos in the line-up |
It feels off | The symbol and the name feel like two different companies |
Can you make it more modern? | It looks like logos from ten years ago because of the beveled edges |
Make the icon bigger | The icon gets lost in the nav at small sizes |
I don't like the font | The name is hard to read quickly, especially the "g" |
Can we try it in green? | The blue reads as generic fintech, which is the look we wanted to avoid |
My co-founder hates it | It doesn't feel premium enough for enterprise buyers, which the brief asked for |
Why does committee voting ruin logos?
Committee voting ruins logos because a vote rewards whatever nobody objects to, and the logo nobody objects to is usually the least distinctive one. Bold concepts split opinion by nature. When five people each veto the thing they personally dislike, the survivor is the average, and average logos blend into their category.
That doesn't mean ignoring your team. Co-founders, early employees and trusted customers can spot real problems: a shape that reads as something unfortunate, a name that's hard to read, a symbol that looks like a competitor's. Collect those observations, but don't count votes. One person, usually the CEO, weighs the input against the brief and makes the call.
What is a good logo feedback script?
A good logo feedback script slows your first reaction down and makes you test before you judge. Follow these steps for every review round. It takes longer than a quick glance, and it's how you avoid spending a revision round on the wrong problem.
Reread the brief
Before opening the concepts, reread what the logo has to communicate, who it's for and what it should not look like. This resets your judgment from "do I like it" to "does it do the job".
Note your gut reaction, privately
Write down your first impression of each concept in one line. Don't send it. First reactions matter, but they're a starting point, not the verdict.
See each concept in context
Look at every concept as a favicon, in a website nav, as a social avatar, in one color and beside five competitors. Many concepts that seemed weak get stronger here, and some that seemed strong fall apart. Our 10 tests for a good logo make this quick.
Sort into keep, refine and drop
Choose one or two concepts to take forward and drop the rest clearly. Asking a designer to merge the best parts of three concepts usually produces a logo with no idea at all.
Write problems, not fixes
For each concept you keep, list what isn't working and why it matters, using the brief's language. If you have a fix in mind, offer it as an example, not an instruction.
Say what's working
Tell the designer what to protect. Without that, revisions can accidentally remove the part you liked most.
Send one consolidated note
Combine everyone's input into one document from the decision-maker. Resolve disagreements before sending, not in the designer's inbox.
For example, suppose a founder reviews three concepts
Hypothetical example: a health-tech founder receives three logo concepts. Her gut says concept B. After the context check, B's thin line symbol vanishes as a favicon, while concept A, which felt plain at first, holds up at every size and looks nothing like the competitors.
Her note: "Taking A forward and dropping B and C. A does what the brief asked: calm and clinical without looking like a hospital. Please keep the symbol's shape and the weight of the wordmark. The one problem is that the teal reads as generic healthcare next to competitors. We'd like a color that still feels calm but is more ownable. Open to your suggestions."
How many rounds of logo revisions should you expect?
Most logo projects include a fixed, small number of revision rounds, but the number in the contract matters less than how each round is used. One round of clear, consolidated notes does more than four rounds of scattered comments. Check your agreement before the first review so you know what's included and what costs extra.
Rounds also shape the schedule. Every round needs time for the designer to work and for you to review, so slow approvals push the finish date more than design does. Our guides to the logo design process and how long logo design takes show where revisions fit.
When should you kill a logo concept instead of revising it?
Kill a logo concept when the problem is the idea, not the execution. If a concept looks like a competitor, signals the wrong category or doesn't fit your positioning, no amount of color or spacing changes will fix it. Revising it just spends rounds on a dead end.
- Revise when the concept is right but the details are off: weight, spacing, color, small-size behavior.
- Kill when the concept reads as the wrong kind of company or looks like someone else.
- Kill when you'd need to explain the idea for people to get it.
- Ask for a new direction when none of the concepts fit the brief, and check whether the brief was clear.
If every concept misses, the problem is often upstream. A brief that says "modern and clean" can't guide anyone, so revisit the positioning before asking for more concepts. Our explainer on what branding is covers why that thinking comes first.
How is logo feedback different from website design feedback?
Logo feedback is about one small, permanent decision, while website feedback is about many changeable ones. A logo will be used for years in places you can't predict, so you're judging durability and distinctiveness. A website can be adjusted after launch, so feedback there focuses more on clarity, flow and conversion.
The principles carry over, though: describe problems, give one consolidated voice and judge against goals. Our guide to giving website design feedback applies the same approach to pages. If you're still choosing between a designer and a tool, the comparison in AI logo generator vs hiring a designer explains why AI tools offer no feedback loop at all, just more options.
