Feedback is a skill

Nobody teaches clients how to give feedback. We hand people a design, a cut, a draft, and expect them to instinctively know how to respond to creative work, a skill that takes creative professionals years to build. Then we act wounded when the notes come back sideways.

So consider this the missing manual. Not because bad notes offend us. Because bad notes cost you money, and good ones are learnable in about ten minutes.

The one rule that carries most of the weight

Describe the problem. Don’t prescribe the fix.

A problem description sounds like: “I didn’t notice the signup button until you pointed it out.” A prescription sounds like: “Make the button red.” The first one hands us the actual issue, and now the whole toolkit is available: size, position, contrast, the competing elements around it, the copy on the button itself. The second one hands us a solution that might not solve anything, because maybe the button was invisible for reasons that have nothing to do with color, and now it’s red and still invisible.

You hired people who solve visual problems for a living. Give them the problem. It’s the more valuable half, and it’s the half only you have.

A short translation guide

Some notes we’ve received many times, and what it costs when they arrive untranslated.

“Make it pop.”

The most famous note in the industry, and the most expensive. “Pop” could mean contrast, color, scale, motion, whitespace, hierarchy, or simply “I’m underwhelmed and can’t say why.” A designer receiving this note starts guessing, and each guess is a revision round you’re paying for. Roulette, at an hourly rate. The translated version is usually something like “this feels quieter than our brand is” or “my eye doesn’t know where to go first,” and either of those we can act on immediately.

“I’ll know it when I see it.”

Translation: I haven’t decided what I want, and I’d like to rent your team while I figure it out. Fair enough, honestly, but say that, and we’ll structure the exploration on purpose instead of burning revisions pretending each round is the last one.

“Can we see it in a few other directions?”

Sometimes legitimate. Often a soft way of saying “I don’t like this and can’t articulate why.” The articulation is the valuable part. Even “this feels wrong and I’m not sure why” is a better note than a request for more options, because it starts a diagnosis instead of a lottery.

Four habits of people whose projects go well

1. They react in first person. “I got lost on this screen” is data. “Users will get lost” is a hypothesis wearing a costume. We can test the hypothesis; we’ll take the data straight.
2. What’s working gets said out loud. Not for our egos. If you don’t flag what’s right, we might fix it, and now you’ve paid to break the best part.
3. Notes arrive ranked. Ten notes of equal weight is a fog. Two must-fixes, five worth-discussing, three take-or-leave: that’s a plan.
4. Feedback shows up as one voice. When it arrives from five stakeholders, the notes disagree, and we end up refereeing your org chart at our hourly rate. Fight it out internally, then send the treaty.

Our end of the deal

This cuts both ways, and we know it. It’s on us to present work with the reasoning attached, so you’re reacting to decisions instead of guessing at intentions. Asking the follow-up question instead of resenting a vague note is on us too. When someone says “make it pop,” the lazy response is an eye roll. The professional response is “tell me where your eye goes first,” which turns the worst note in the industry into a usable one inside a minute.

Vague feedback is an invitation to a conversation. We try to accept the invitation instead of grading it.

The best notes we’ve ever gotten were all some version of the same six words: “This looks like everyone else’s.” That kind of note stings. It contains no instructions whatsoever. And when it’s true, the next round gets better in ways no prescription could have reached.

That’s the whole skill. Tell us what’s true. We’ll handle the rest.