How to write feedback that improves the work, not the mood

Good feedback points at the exact place the work falls short and says what better looks like there. Anything vaguer is mood, and nobody can revise a mood.

This is about the written kind: notes typed into a comment box on a draft, a design, a plan, or a pull request, where your face is not around to soften anything and the words have to do all the carrying.

Open with the verdict

The first line of written feedback should say what happens next for the work, before any of the notes. Everything below that line is detail.

People read feedback out of order. The first thing they hunt for is the overall damage, and until they find it, every small comment looks like part of something bigger. It is the same reflex that makes people bury bad news, running in the other direction.

A verdict is one plain sentence. A few that work:

• "Ready once the two comments below are fixed."
• "The structure holds. The middle section does not, and most of my notes live there."
• "I do not think this approach survives review. Want to talk before you revise?"

Skip the verdict and the notes fill the vacuum. Eleven comments with no verdict reads as start over, even when you meant nearly there.

The verdict also sets the depth of everything under it. If the draft needs a rethink, stop at the fundamentals. Polishing commas on something you are about to ask someone to rebuild is its own small cruelty.

While you are at it, say which notes gate shipping and which are optional. I tag mine with "must fix" or "take it or leave it". It costs a few words and saves a whole round of guessing.

Anchor every note to a line

A note the person cannot locate is a note they cannot fix. Tie every comment to a place they can click, quote, or scroll to.

• In a document, quote the sentence you mean.
• In a design, name the screen and the state it is in.
• In code, comment on the line, not the file.
• In a recording, give the timestamp.

"This feels off" is a real signal, and I do not want anyone swallowing it. It just is not usable until it comes with coordinates. "The second paragraph promises three reasons and delivers two" gets fixed before lunch. "Something about the intro is not working" starts an investigation.

Feelings are fine evidence and bad instructions.

Sketch what better looks like

A note that names the problem without pointing at a direction is half a note. You do not owe anyone the finished fix, but you owe them a next move.

"Too long" just repeats the verdict. "Cut the history section, nobody reading this needs it" is a move. The second one risks being wrong, which is exactly what makes it useful: the writer finally has something concrete to disagree with.

The opposite failure exists too, and it dresses up as generosity: rewriting the whole thing your way in the comments. At that point it has stopped being feedback and turned into ghostwriting with extra steps. Sketch the direction, then let them build it.

I get to practice this on myself. Unvent's three tones went through a lot of rounds of my own notes, and the ones that said a rewrite sounded off did nothing for me the next morning. The only notes I could act on named the sentence and said what it should have sounded like instead. Being your own reviewer teaches you quickly which notes are usable, because you are also the one stuck holding the useless ones.

Make the praise carry information

Praise earns its place in feedback when it is specific enough to repeat on purpose. "The opening example is doing a lot of work, keep it" tells someone what to protect in the next revision. "Great job overall" tells them you opened the document.

Praise that could be pasted under anyone's work is worth nothing.

Specific praise is also the cheapest way to steer the next ten drafts, because people repeat what got named. Half of improving someone's work is stopping them from sanding off the parts that were already good.

There is a selfish reason to get good at this. Someone who only ever hears what is broken starts defending drafts instead of sharing them, and then you see the work later, and worse. Specific praise keeps the drafts coming early, while the notes are still cheap.

So my rule is symmetry. If the criticism names a line, the praise names a line.

Write it blunt, check it warm

Criticism in writing lands about a notch harsher than you meant it, because your delivery does not travel with your words, and the version the reader imagines is rarely the friendly one.

The wrong response is padding every note with softeners until nobody can find the point. Keep the content blunt. Spend the warmth in two specific places instead: the verdict line and the closing line, because those are the sentences people reread.

One more situation worth naming: sometimes the notes are fair and specific and the writer still takes them personally. When an angry reply lands, wait an hour before typing anything you would have to apologize for later.

One last check before you send: could they act on every note without booking a meeting to decode it? If not, the note is not done. The mood, it turns out, mostly takes care of itself once the notes are usable.