How to Give Design Feedback That Makes the Work Better

The difference between a project that lands in three rounds and one that drags through eight is almost always the quality of the feedback, not the design. Here's how to give comments a designer can actually use.

Giving design feedback is a learned skill, not a personality trait, and most business owners have never been formally taught how to do it. The first round of logos lands in your inbox, you stare at three options for ten minutes, and you type “I’m not loving option two — can we try something more modern?” That comment, sent in good faith, will cost you a week and produce a revision you like even less than the original.

The difference between a brand or website project that lands in three rounds and one that drags through eight is almost always the quality of the feedback, not the quality of the design. Designers are usually good at design. The variable is what they’re given to work with.

Why “I’ll know it when I see it” wastes everyone’s money

Vague feedback like “make it pop,” “it doesn’t feel right,” or “something’s off” gives a designer almost nothing to work with. They can guess at what you mean, but a guess is just another concept. You haven’t moved the project forward — you’ve started a new one.

A small-business rebrand or website project usually budgets two to three rounds of revision. Each round you burn on imprecise feedback is a round you don’t have for the real refinements at the end. Projects that overrun their timelines almost never overrun because the designer was slow. They overrun because the feedback loop never tightened.

Describe the problem, not the prescription

The single most useful habit you can build is to describe what isn’t working and let the designer solve it. You hired a designer because you wanted their judgment. If you write the prescription yourself, you’ve also taken on the responsibility for whether it works.

Compare these two comments on a homepage hero:

  • Prescription: “Make the headline bigger and move the button to the right.”
  • Problem: “I’m worried a first-time visitor won’t immediately understand what we sell. The headline isn’t carrying that weight for me.”

The first comment locks the designer into one solution — your solution — and may produce a worse hero. The second describes the underlying issue and lets the designer answer it three different ways: rewrite the headline, restructure the section, add a subhead, change the image. Their answer will almost always be better than yours, because diagnosing visual problems is the actual job they trained for.

Tie every comment back to a goal, not your taste

Your taste matters, but it isn’t the standard the work is being judged against. The work is being judged against the goals you set at the start of the project — what the brand needs to communicate, who it needs to reach, what it needs to make happen.

Before you send a comment, ask yourself: which project goal is this serving? If you can’t connect the comment to a goal, it might be a personal preference, and personal preferences are the slowest, most expensive form of feedback. They’re also the kind that stakeholders argue about endlessly because there’s nothing external to check the argument against.

Good feedback sounds like: “Our audience is parents of school-age kids in Albuquerque, and this color palette feels closer to a tech startup than a community business.” That’s specific, tied to the audience, and gives the designer a real target. Bad feedback sounds like: “I just don’t like green.”

Consolidate before you send

One of the most common ways feedback rounds get derailed is the trickle. The owner sends three comments Monday, two more Tuesday, then a follow-up Wednesday after their partner saw the proof. Every fresh email forces the designer to context-switch and redo work they already started revising. The total amount of design that gets done shrinks.

Sit with the work for a few hours, not a few days. Gather every comment from every stakeholder into one document. Reconcile contradictions before they reach the designer — if your business partner wants the logo bigger and your spouse wants it smaller, that fight should be settled internally, not refereed by your designer at $150 an hour.

One round, one voice

Designate a single decision-maker per project — usually the founder or the marketing lead. Other stakeholders can contribute, but their comments get filtered through that person before reaching the designer. Without a single voice, a designer ends up trying to please three people whose feedback contradicts itself, and the result tends to please no one.

This is one of the quietest reasons large committees produce mediocre brand work. It’s not that the committee has bad taste; it’s that the designer never gets a clean signal.

How do you give design feedback without sounding mean?

Most clients worry about being harsh, and the worry is misplaced. Designers want specific, even pointed, feedback — what they don’t want is vague feedback that forces them to guess. Critique the work, not the person. “This logo feels generic for our category” is fair game. “This is a bad logo” is a judgment of the designer’s competence and rarely useful.

It also helps to lead with what’s working before what isn’t. Not as a softening trick, but because telling a designer which direction to keep pursuing is genuinely useful information. “The wordmark feels confident — I want to keep that energy. The icon underneath isn’t carrying its weight” is a clearer instruction than just listing what to change.

A simple template you can use today

If you want a structure to follow, three questions cover most of what a designer needs:

  1. What’s working? Name the specific elements you want preserved in the next round.
  2. What concerns you, and why? Describe the problem you see, tied to a project goal — not your fix for it.
  3. What decision do you need from the designer? If you’re stuck between two directions, say so explicitly so they know what choice to bring back.

Spend ten minutes filling that out before any feedback call and the call will be shorter, the next round will be sharper, and the project will land closer to your timeline. Designers can tell when feedback has been thought through. They respond to it differently — not with more deference, but with more precision, because they finally have something to aim at.

Feedback is a collaboration, not a performance

The best client-designer relationships look more like a working partnership than a transaction. After a brand engagement with Brainstorms, Inc., creative director Candace Walsh noted that Patrick Iverson “took constructive feedback very graciously” — the kind of remark clients use when a designer treats revisions as a shared problem-solving exercise rather than personal critique. That posture goes both ways: a designer who welcomes feedback is responding to a client who has learned to give it well.

If you’re about to start a brand or website project in Santa Fe, Albuquerque, or anywhere else in New Mexico — or remotely from elsewhere in the country — and you want a partner who’ll engage with your feedback rather than just absorb it, that’s how Patrick Iverson works on every brand strategy and identity engagement. Send a few notes about your project. The first conversation is free, and the goal of it is to figure out whether you’re a fit, not to sell you something.

Patrick's design sense opened up new possibilities for our website. His keen sense of matching client needs and skills to the available tools produced a site that we love working with. And his relaxed and responsive personal style made the whole project a pleasant experience.

Cecile LaBore, Recovery Systems Institute