5 Things Your Graphic Designer Wants You to Know (But Might Not Tell You)

A lot of bad design doesn’t start with a bad designer. It starts with a bad working relationship.

The owner has an idea. The designer has an opinion. Three employees have feedback. Someone’s spouse hates the font. By round six, everybody has had a say and nobody can explain what problem the design is supposed to solve.

That’s the part clients don’t always see. Graphic design is subjective at the surface, but good design isn’t just a pile of preferences. There are goals, users, constraints, hierarchy, legibility, consistency, and a reason behind the decisions.

If you’re paying a designer to help your business, these are five things I want you to understand before the first round of feedback.

1. More Design Doesn’t Mean Better Design

One of the fastest ways to weaken a layout is to keep adding things because empty space feels unfinished.

Make the logo bigger. Add another badge. Fill that corner. Put a pattern behind it. Add one more line of copy.

Eventually everything is trying to be important, which means nothing is.

White space isn’t wasted space. It gives the design room to breathe, helps separate information, and makes it easier to understand what you’re supposed to look at first.

The same goes for your logo. Branding is bigger than how many times the logo appears. If the colors, type, photography, layout, voice, and overall system are doing their job, you don’t need to stamp the logo into every available corner.

Sometimes the best design decision is leaving something alone.

2. The Design Is Not Supposed to Be About You

You’re allowed to like the design. I want you to like it. But “I don’t like blue” is different from “blue is wrong for our brand or the people we’re trying to reach.”

Your business knowledge matters because a designer who doesn’t understand your business is guessing. But once the goals, audience, and limitations are clear, the work has to be judged against those things, not only your personal taste.

My job isn’t to win a taste contest with you. It’s to take what you know about the business and turn it into something that works for the people you’re trying to reach.

You might personally hate something that is still the right decision for the brand.

That distinction matters.

3. A Designer Should Not Love Their Work

I say this all the time: a designer can like their work, but they should never love it.

The second you love something you created, you introduce bias.

Now you’re emotionally attached to the idea. You want it to work because you made it. You start defending the design instead of evaluating whether it’s actually the right solution.

That’s a problem.

Design requires you to be able to look at your own work objectively. Sometimes the concept you spent hours on isn’t the best one. Sometimes the client brings up a legitimate problem. Sometimes another designer has a better idea.

If you’re in love with your work, it becomes a lot harder to admit any of that.

I can like a design. I can be proud of the work. But I still need to be able to look at it and say, “This doesn’t work,” and throw it away.

That ability to separate yourself from the work is part of being a good designer.

4. Not All Feedback Is Equal

Your designer already knows the work is going to get shown around. Business partner. Employees. Spouse. Friend who “has a good eye.”

Get feedback. Just don’t confuse the amount of feedback with the quality of it.

Your sister can hate the logo and still be wrong for the audience. A customer can love a color and still give you bad design advice. Even a target customer is not automatically a designer.

Feedback is information. It still needs interpretation.

Before asking for a revision, I would run the comment through four questions:

• Who is this feedback coming from?
• What actual problem is the change supposed to solve?
• Is this about clarity, function, brand fit, or just personal taste?
• Would we still make this change if one person hadn’t specifically asked for it?

If nobody can answer those questions, the revision probably doesn’t need to happen.

Trying to make everyone happy is how good design gets sanded down into something nobody hates and nobody remembers.

5. If You Hired an Expert, Expect Them to Push Back

You’re probably not a design expert. That’s okay. You shouldn’t have to be. You hired one.

But here’s the other half: your designer is not automatically the expert on your business.

You know the product, customers, operations, limitations, internal politics, and goals in a way an outside designer doesn’t on the first day. The designer understands typography, color, hierarchy, layout, file formats, scalability, and how the design needs to hold up across different applications.

The best relationship is not “the client shuts up and the designer does whatever they want.” That’s bullshit.

It’s also not “the designer becomes a mouse operator and executes every idea without question.”

Your job is to give the designer the information they need. Their job is to turn that information into design, explain why decisions were made, and push back when a request makes the work worse.

You still get the final say. But if you consistently hire experts and then ignore the expertise you hired them for, you’re paying for execution while throwing away a large part of the value.

Good Design Needs Good Judgment on Both Sides

Most bad feedback loops aren’t really about design. They’re about unclear goals, too many opinions, and nobody knowing which standard actually decides whether the work is good.

So before you ask to make the logo bigger, add more to the empty space, or change a concept because three people “weren’t feeling it,” ask one question:

What problem are we solving with this change?

If there’s a real answer, change it.

If there isn’t, leave it alone.

If you want a design team that will take your business seriously, explain the reasoning behind the work, and tell you when something doesn’t make sense, schedule a call with me and my team at Desque.