How to tell a coworker their work is not ready

The kind way to tell a coworker their work is not ready is to say it plainly, early, and about the work: name the specific gap, point at the shared standard, and give them a next step they can actually take.

Most people do the opposite. They write "looks good, just a few thoughts" and then bury the real problem in comment twelve, hoping the author will find it on their own.

That move feels gentle. It is not. The author walks away believing they are nearly done, plans their week around it, and finds out at the worst possible moment that they were never close. Vague approval is the cruel option dressed as the nice one.

Say it before the deadline says it for you

Tell them the moment you know, because every day you sit on the news makes it worse news.

Silence has a schedule of its own. If the work is not ready and nobody says so, the deadline says it instead, in front of more people, with less time to fix anything.

The early version of the message is also easier to write. "This needs another pass before it goes out" lands very differently on Tuesday than it does an hour before the review. Early, it is a note between colleagues. Late, it is a verdict.

I rewrote the Unvent store listing more times than I want to admit before submitting it. The drafts I threw away had one thing in common: I already knew they were not ready while I was polishing their commas. Somebody saying so on day one would have saved me the week I spent proving it to myself.

Name the gap, not the person

The message should describe the distance between the work and the bar, and say nothing about the person who wrote it.

There is a real difference between "this is not ready" and "you are not ready", and under deadline stress people blur it. Keep the work as the subject of every sentence. "The argument in section two does not survive the numbers in section four" is a sentence someone can act on. "You tend to rush things" is a sentence someone will defend against, and the work stays broken while they do.

Concretely, that means:

• Point at places, not patterns. Quote the paragraph, link the section, name the case that fails.
• Say what "ready" means for this piece of work, out loud, once.
• Skip the adjectives. "Sloppy" starts a fight; "missing the error case" starts a fix.
• Leave their past work out of it entirely.

If you cannot name the gap concretely, you are not ready to give the feedback. "Something feels off" is a note to yourself, not a message to them. Do the work of finding what is off first, or say honestly that you cannot tell yet and need a day.

The standard does the confronting for you

Comparing the work to a visible bar takes the sting out, because the bar is not a mood.

"This is not what I would have done" is taste, and taste is a losing argument with a colleague. "This does not yet do what the ticket says" is a fact both of you can stand next to and look at together.

So anchor the message to something outside your own head. The spec, the checklist, the acceptance criteria, the example everyone agreed was good. When no such thing exists, that is your finding: the work is not ready because nobody defined ready, and that gap belongs to the team, not to the author.

This is also the honest answer to the worry that saying "not ready" makes you the villain. It does not, if the standard was visible before the work started. It might, if you are quietly raising the bar after the fact. Check which one you are doing before you hit send.

End with a next step, not a verdict

A "not ready" message earns its keep in the last line: what would make it ready, and what happens next.

Feedback that stops at the diagnosis leaves the author alone with a pile of problems and a bruise. You do not have to fix it for them. You do have to leave the door open and the path lit.

The shape I use:

• One sentence on where the work stands against the bar.
• The two or three gaps that matter most, each pointing at a specific place.
• What I am explicitly not worried about, so they do not sand the wrong plank.
• The next step, with a time attached: another pass, a call, a narrower scope.

Notice what is missing: the compliment cushion. I do not open with two lines of praise I half mean. People learn your pattern within a month, and after that your praise reads as a warning siren. If something is genuinely good, say so where it is true, not as anesthetic before the needle. Written feedback survives being reread, and it will be reread, so every sentence has to hold up on the third reading.

When they push back

If they disagree, that is the conversation working, not failing.

You flagged the gap; maybe they know something you do not. Half the time "this is not ready" turns out to mean "I did not know about the constraint you were working around". Say what you see, hold it loosely, and let them disagree with the claim rather than with you.

What you should not do is soften the message until it can no longer be disagreed with. A note so gentle it says nothing cannot be pushed back on, because it never lands anywhere. Write the version with edges, in the plainest words you have, and trust your colleague to be an adult about a true sentence.

They usually are. And the ones who thank you a month later are never thanking you for the time you said "looks good" and let them walk into the wall.