Logo Review Guide
How to Give Useful Feedback on a Logo
Learn how to give useful logo feedback that is specific, evidence-based, and actionable for designers, founders, and brand teams.
A practical guide for founders, clients, designers, and brand teams


Start with the brief, not your personal taste
Before reviewing a logo, write down who it is for, what it should communicate, and where it must work. A mark for a software product may need to remain clear in a small navigation bar, while a retail identity may need to work on packaging and signage. Without this context, feedback tends to become a debate about whether the design feels modern, premium, or friendly.
Ask the designer to show the intended audience and primary applications. The same logo can be successful in one setting and weak in another, so make the job measurable before discussing changes.
Describe what you see before explaining what you feel
Begin with a neutral observation: “The symbol and wordmark have similar visual weight,” “the counter closes at small size,” or “the first letter sits very close to the icon.” This gives the team something concrete to inspect. “It feels off” may be a useful signal, but it is not yet an actionable diagnosis.
Separate observation from interpretation. You might see a dense silhouette, then infer that the logo may be difficult to recognise in a favicon. State both parts so the designer can test the inference rather than guessing which change you want.
Give feedback in order of impact
Prioritise issues that affect recognition, legibility, distinctiveness, or real-world use. A crowded silhouette matters more than a minor curve preference. Weak contrast in the primary application matters more than whether a corner could be slightly rounder.
A practical order is: first-read clarity, audience fit, distinctiveness, typography and spacing, scalability, contrast, then polish. This keeps a review from producing a long list of low-value edits that obscure the main decision.
Use specific language for typography and spacing
Replace “make it cleaner” with a visible relationship. Say that the wordmark feels cramped because the gap between two letters closes at the intended header size, or that the symbol appears too dominant beside the name. Mention the size, background, and application where you notice the problem.
Review letter spacing, weight, alignment, cap height, symbol-to-wordmark proportion, and optical balance. Mathematical alignment is not always visual alignment, so compare the lockup at normal viewing distance as well as close up.
Test the logo in real conditions
Ask to see the logo at 16px, 32px, 64px, and a larger display size. Test light and dark backgrounds, one-colour use, a busy image if relevant, and the actual interface or packaging where customers will encounter it.
A useful feedback note connects the result to the job: “The icon remains recognisable at 32px, but the wordmark disappears in the mobile header.” This is more useful than asking for a logo that is simply “more readable.” For a broader checklist, see the logo evaluation criteria.
Compare before calling something generic
Place the logo beside five to ten direct or adjacent competitors at the same size. Look for repeated category conventions, confusing similarities, and one feature that customers could remember. Distinctiveness is not the same as unusualness; a strange mark that cannot be read is not automatically stronger.
Keep competitor comparisons focused. Do not ask for a completely different concept unless the review shows a strategic problem. Often the best next step is to protect one ownable shape, proportion, or letterform while simplifying the surrounding system.
End with a decision, not a mood board of opinions
Sort the discussion into Keep, Refine, and Reconsider. Keep names the strengths that should survive. Refine covers production or system fixes such as spacing, contrast, variants, and exports. Reconsider is reserved for strategic problems such as audience mismatch or confusing similarity to a competitor.
Finish with one or two testable next steps and the condition for approving them. The Logo Review Tool can provide a structured first pass across clarity, contrast, colour, scalability, typography, uniqueness, versatility, and application before the team reviews the work together.
Frequently Asked Questions
What makes logo feedback useful?
Useful feedback describes an observable issue, explains why it matters in context, and suggests a direction that the designer can test. It is specific rather than a broad preference.
Should I say what I like before giving criticism?
Yes, when the positive observation is genuine and relevant. Identify the strengths that should survive refinement, then focus on the highest-impact issue instead of listing every personal reaction.
How do I avoid subjective logo feedback?
Agree on the audience, brand job, and real applications first. Then test the logo at useful sizes, on relevant backgrounds, beside competitors, and in monochrome before making a recommendation.
Does negative feedback mean the logo needs a redesign?
No. Spacing, contrast, export quality, missing variants, and small-size detail are often fixable system or production issues. A redesign is more appropriate when the mark repeatedly misfits the audience or category.