How to give useful feedback on a logo proposal
A practical framework for giving precise, prioritized and constructive feedback on a logo proposal without taking over the designer’s role.
Useful logo feedback is neither polite silence nor a personal preference turned into a design order. The best response explains the gap between a proposal, an approved brief and real applications. It helps the designer solve the right problem while protecting the identity as a system. This guide offers a practical method for reviewing a direction, consolidating stakeholders, prioritizing requests and running revisions without an endless loop.
Sources consulted: Interaction Design Foundation · Nielsen Norman Group.
Why logo feedback is difficult
A logo proposal triggers an immediate response: like, dislike, recognition or doubt. That intuition matters, but it does not tell a designer what to revise. Useful feedback connects the response to the project goal, the audience and a real touchpoint. Instead of saying that blue feels sad, explain that the current shade feels too institutional for a family leisure brand. The second statement identifies a gap while leaving room for professional solutions.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Return to the brief before commenting
Begin with the approved brief. Who must recognize the brand, what promise matters, where will the mark appear, and which competitors should it avoid resembling? Turn those answers into observable criteria: accessible without looking childish, readable at twenty-four pixels, distinctive in the local market, effective in one color and credible on a proposal document. Shared criteria prevent the loudest personal preference from becoming the strategy.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Describe before judging
Separate observation, interpretation and request. Observation: the name becomes difficult to read below three centimetres. Interpretation: this may weaken product labels. Request: could we test a less extreme contrast between strokes? This sequence gives evidence and opens discussion. Avoid psychological verdicts such as “the design has no soul.” Name visible properties: rigid rhythm, weak contrast, generic sector symbolism or an unbalanced small-size composition.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Be precise without designing for the designer
Precision does not mean taking over the design. “Make the circle twelve percent larger” may solve a symptom and damage the system. Say instead that the symbol dominates while name recognition is the launch priority. A helpful comment usually contains context, finding, expected consequence and priority. If you suggest a solution, frame it as a hypothesis. The designer can confirm it, challenge it or propose a better responsive variation.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Prioritize instead of multiplying comments
Do not send thirty comments with equal weight. Label items as blocking, important or optional. Blocking issues concern strategy, readability, essential production uses or clear legal risk. Group comments that may have one cause. A cold impression can arise through type, color and angles; changing all three separately may overcorrect. Limit each cycle to a few decisions so the team can see what improved and preserve what already works.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Consolidate feedback from several people
When founders, marketing and sales all comment separately, the designer is forced to solve an internal governance problem. Appoint one person to consolidate reactions, identify contradictions and send a single decision. Ask every reviewer to use the same criteria before the meeting. In a disagreement, return to audience and usage: which direction expresses the promise and survives priority constraints? A focused audience check may inform uncertainty, but design should not become a popularity contest.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Avoid language that blocks progress
Words such as modern, premium, dynamic or “more wow” are ambiguous. Define what they mean here: premium through restraint, typography, material, rarity or contrast? Modern in a digital, editorial, industrial or cultural sense? References to famous brands should identify a quality, never request copied symbols, colors and composition. If objectives conflict—more minimal yet with more elements—state the tension and choose a priority.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Organize an effective revision cycle
Use one feedback document with a short summary. Start with strengths that must remain, list issues by priority, and finish with open questions. Annotated screenshots should locate a problem, not replace its rationale. Agree on scope, deliverables and timing; a sound revision may require rebuilt lettering, proportion tests and production checks. On the next round, compare against the consolidated feedback rather than the memory of the first emotional reaction.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Test the logo without turning it into a poll
Useful tests answer specific questions: can people read the name quickly, does the symbol remain distinct at small size, and does the brand feel more approachable than relevant alternatives? Results reveal risks; they do not automatically design the answer. The Nielsen Norman Group’s usability heuristics concern interfaces rather than logos, yet their discipline around visibility, consistency and error prevention is valuable when checking real contexts.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
A message template you can adapt
A practical message can read: “Thank you for the proposal. We want to preserve the symbol’s clarity and the type personality. Two points are blocking: the name loses readability at small size, and the dark-background version lacks contrast. Product labels and mobile avatars are our priority uses. The overall tone also feels more institutional than the accessible direction in the brief. Could you explore a response while preserving the general construction?” Add factual constraints and ask where a secondary lockup is preferable.
Review the proposal in the actual application, not only in a polished presentation. Check the full signature, symbol alone, monochrome version, dark background, small scale and the production method that matters. A concern tied to a touchpoint is easier to verify and resolve than a general aesthetic command.
Keep the designer responsible for the visual answer. The client contributes business knowledge, customer context and operational constraints; the designer contributes hierarchy, form, typography and system thinking. This division creates constructive tension without reducing collaboration to taste or blind execution.
Checklist before sending
- Read the brief and extract five criteria
- Test priority uses and small sizes
- Separate facts, interpretations and ideas
- Consolidate stakeholders into one message
- Label blocking, important and optional items
- Explicitly preserve approved strengths
Prepare a clear logo brief with Wilogo
Want to start an identity project with better criteria from day one? Describe your business, audience, touchpoints and preferences in a structured brief.
Frequently asked questions
Should I say that I dislike a proposal?
Yes, but explain what causes the response and connect it to the brief. Emotion is useful input, not a complete instruction.
How many comments should one round contain?
A few prioritized decisions are better than a long list. Separate blocking, important and optional points.
Can I share reference logos?
Yes, to illustrate one quality—not to request a copy. Name the relevant quality such as restraint, contrast, rhythm or flexibility.
Who should consolidate stakeholder feedback?
One appointed person should combine contributions and resolve contradictions before sending them to the designer.
When is a revision finished?
When priority goals and essential uses are satisfied, the system remains coherent, and remaining disagreements are minor preferences.
