How do you give feedback without just telling someone what to do?

Name the problem you see, not the solution. Point to the evidence where you saw it. Say "The palette is all warm tones, and it reads louder than the calm this brand promised." That is a note. Now the person can try different ways to solve it. They will find something better than you imagined because they know their craft better.

What if you give feedback and the person goes in a completely different direction with it?

That is working. They own the work. The feedback said: here is what I saw. They decide what to do about it. You might see it and think: that is not the solution I would have picked. But it solves the problem you named, so it works. You gave them information. They used their judgment. That is the whole point of feedback.

Should you ever tell someone exactly what to do with feedback?

Yes, in specific moments: when the problem is a rule or a constraint they did not know about, when they are very early and need direction, or when speed matters more than learning. Most of the time, no. Tell them what is wrong. Let them get better at solving it. That is how you build a team that does not need you to check every decision.

Feedback That Actually Changes the Work by Tyler Garner

Why does so much creative feedback go nowhere?

Most creative feedback goes nowhere because it is a reaction, not a note. "Make it feel more premium." "The energy is off." These describe your feeling, not the work's problem. A person who hears this leaves the room without knowing what to fix. They guess. Feedback that goes nowhere does that over and over: reaction, guess, repeat.

When you get a note like that, you have nowhere to go. You cannot push against it because it is not an argument, just a feeling. So you go back to your desk and change things at random, hoping one lands. As an editor, I got notes like that all the time and spent hours trying to read between the lines, asking myself what the person actually meant. That guessing game teaches you to stop trusting your own judgment.

What is the difference between a reaction and a note?

A reaction is what you felt looking at the work. "I like it" or "It does not land." A note is what you saw. "The contrast makes text hard to read" or "The copy is too formal for this audience." One is about you. One is about the work. Usable notes name a specific problem and point to evidence.

An editor hears "The energy is off," and they have no path forward. A dozen changes might move the energy. Which ones? All of them? An editor hears "The pace of the cuts is slowing down in the middle act," and they know exactly what to look at and where to experiment. That is a note. The first one is a reaction dressed up as feedback.

How do you write a note someone can use?

A usable note has three parts. Name the problem. Point at the evidence. Leave the solution to whoever is doing the work. "The copy reads corporate, but we said this brand sounds like a person." That is a note. Corporate is the problem. The copy is the evidence. Now they can close the gap.

The three parts work like this:

The problem: what you saw that is not working. Be specific. Corporate, not off. "The gray text on white is too light," not "the design feels weak."
The evidence: where you saw it. The homepage copy. The button at the bottom. The email confirmation. Point at the place.
The solution: do not build the fix. Do not say "Make it sound casual" or "Try sans serif." You saw the problem. You named it. That is enough.

Not every note needs that much structure. Short notes work too. "This headline wraps to two lines and buries the verb." "The hold time on that frame is too long." The principle stays the same: what did you see, where did you see it, and stop there. When you build the fix inside the note, you become the taste in the room. When you name what is wrong, they get to be.

I learned this from editing first, before I led anyone. Every cut is feedback to the viewer about where attention goes next. You can make that choice by accident, reacting to what feels right. Or you can make it deliberately, naming why it belongs there. The editors who taught me were always the second kind. They could say why. A note is the why, said out loud.

What happens when feedback lands?

When feedback lands, the work moves forward without stalling. People use it, they do not ask for clarification, and they come back stronger. Good feedback respects that the person doing the work has judgment too. That judgment might even be better than yours because they have been living in the problem all day.

People stop defending themselves. They stop performing compliance. They start listening because they know a note means information they can use. They know you are not a taste competitor in the room. You are someone who saw something and told them the truth.

The best version of my team was not the one with the most critical eye at the top. It was the one where criticism landed as information, not verdict. Where a note meant something specific enough to learn from. Where feedback moved work forward instead of backward, where people got faster at using it over time because they understood the principle underneath. A note is only good if the person can use it without asking you what you meant.