How to tell someone their work isn't good enough

Almost everyone softens this conversation so much that the message never lands. The person walks out feeling vaguely uneasy, not clear, and three weeks later you are having the same talk again with a sharper edge.

The instinct to cushion is good. The execution usually is not. Here is how to be honest about work that is falling short without either crushing the person or letting them off the hook.

Separate the work from the worth

The thing you are evaluating is the deliverable, not the human. That sounds obvious and it changes everything in how you talk. “This report missed the mark” is a statement about a report. “You’re sloppy” is a verdict on a person. The first invites a fix. The second invites defense.

So name the work, every time. The deck did not make the argument. The analysis skipped a step. The code shipped without the edge cases handled. You are not being cold by staying on the work. You are giving the person something they can actually change.

Lead with the gap, not the feelings

Managers love a warm-up. “How are you feeling about the project? Is everything okay at home?” Sometimes that is genuine care. Often it is delay, and the person can smell it. They spend the whole preamble bracing, which means they hear none of it.

Get to the gap in the first minute. Try something like: “I want to talk about the client deck. It didn’t land the way we needed it to, and I want to be specific about why.” Then be specific. The kindness is in the clarity, not the cushion.

Be concrete or be ignored

Vague feedback is the cruelest kind because the person cannot act on it. “This needs to be stronger” tells them nothing. Stronger how? Compared to what?

Bring examples. This slide had three competing messages instead of one. This section made a claim without evidence. The intro promised an answer the body never delivered. Concrete feedback respects the person enough to assume they can fix a real problem once they can see it.

If you cannot point to a specific thing you would do differently, you are not ready to give the feedback yet.

Say what good looks like

This is the step almost everyone skips. You name the problem, the person nods, and then they go off to guess at the target. Half the time they guess wrong, and now you are both frustrated.

Close the gap out loud. “Here’s what a strong version looks like: one clear recommendation up top, three reasons, the data behind each one.” You are not micromanaging. You are removing the guesswork so the next attempt has a fair shot.

Make it a conversation, then a plan

After you have been clear, stop talking. Ask what they make of it. Sometimes you will learn there was a constraint you did not know about. Sometimes you will hear a defense that tells you exactly where the real gap is. Either way, the person needs to process out loud, not just absorb.

Then leave with something concrete: what changes, by when, and how you will both know it worked. End the conversation on the plan, not the problem.

The hardest part of this is not the words. It is your own discomfort with someone being briefly disappointed in front of you. Sit in that discomfort. It is the price of giving people feedback they can actually use, and it is a far smaller cost than letting them keep missing while you quietly lose faith.