Constructive Feedback Examples: The Vague Line and the One That Works

Here is a sentence that gets said in a lot of one on ones, and it changes nothing.

"I would love to see you be a bit more proactive."

The person nods. There is nothing to disagree with. Then they go to their desk and try to work out what proactive means, which is a question about your preferences and not about their work. A month later you say it again, and now they think you have a problem with them. The constructive feedback examples below come in pairs: the sentence that gets said, and the one that changes something.

That sentence fails for one reason, and the reason is not tone. It carries no evidence. No date, no meeting, nothing anyone could have watched happen. It names a category, and nobody can fix a category.

What follows is a reference of constructive feedback examples organized by the situation you are in. Each appears twice: the version most managers reach for, and the version that gives the other person something to work with.

The phrase is not the part that works

None of these lines are scripts. Advice on how to give constructive feedback stops at the wording, and the wording is not what does the work. What makes any of them land is the thing attached: a date, a meeting, a document, a behavior a third person could have watched and described in your words.

Take that out and the sharpest sentence here becomes a nicer way of saying nothing. Put it into a clumsy sentence and the clumsy one works, because the person knows what you mean and can agree, argue, or fix it.

So every example below has two parts: the sentence, filled with a detail from a company that is not yours, and a bracket naming what you supply from your own week. Feedback examples for employees travel between companies. The bracket does not.

One test before you open your mouth. Could the person write down what to do differently, in one line, without a follow-up question? If not, you have a feeling rather than feedback. Everything else about how to open one of these is secondary to that.

When a deadline slipped

Deadlines are the easiest case: the evidence is already written down somewhere. Vagueness here is a choice.

Vague. "You have been missing deadlines lately."
Specific. "The pricing copy was due Tuesday and reached me Friday. Two designers waited a day on it." [the item, promised date, actual date]

Vague. "This is becoming a pattern."
Specific. "The audit slipped a week in September, the migration four days in October, and Monday's deck was late." [each instance, in order, with dates]

Vague. "You should have told me sooner."
Specific. "You knew Wednesday that Friday would not happen. I found out Friday at five. Late work costs a day. Late warning costs the chance to fix it." [when they knew, when you did]

Vague. "Try to be more realistic with your estimates."
Specific. "You estimated four days and it took nine. Walk me through the four, because I need to know if the estimate was wrong or the week was." [estimate, actual, the open question]

End to end, with nothing softened, it sounds like this.

The last move is the one people skip. Four sentences, every one checkable, then silence. What they say next tells you which problem you are solving.

When the work is below the bar

Quality feedback goes wrong when you describe your reaction to the work instead of the work. Point at the page.

Vague. "This is not quite there yet."
Specific. "Section three says churn is flat and the conclusion says churn is the reason to fund this. The analysis is solid. The recommendation is not." [what works, what fails, where they clash]

Vague. "The quality has slipped."
Specific. "The last two releases shipped the same bug, null handling in the import path. QA caught the first. A customer caught the second." [what it was, how often, who caught it]

Vague. "You need to be more detail-oriented."
Specific. "Four broken links and two wrong prices went to the client in that deck. I want the check before it leaves your hands." [the count, the artifact, who saw it]

Vague. "This needs more work."
Specific. "Here is the bar. A partner reads it once and knows what we recommend and why. Right now the recommendation is on page nine." [the bar in one sentence, the one change]

If the gap has been open for months rather than weeks, this is no longer feedback on a document. It is a conversation about performance, which needs a different opening and a written record.

When the problem is how they talk in meetings

This is where managers reach hardest for abstraction, because the specifics feel personal. Say them anyway. Describe what happened in the room and what followed.

Vague. "You can come across as a bit blunt."
Specific. "In Tuesday's review you cut Priya off twice while she was presenting. She did not speak again for the rest of the hour." [the meeting, the date, the count, what followed]

Vague. "Work on your executive presence."
Specific. "You gave four minutes of background in the steering meeting before the recommendation, and were asked twice what you needed. Start with the ask." [the meeting, what you saw, the change]

Vague. "People find you intimidating."
Specific. "Twice this month someone brought me a question they did not want to ask you. That is not a claim about your intent. It is what people do." [how often, what they did, intent left out]

Vague. "You need to speak up more."
Specific. "You had the answer to the pricing question and told me after the meeting. I want it said in the room, even half formed." [the moment, what they knew, where you want it]

When the person doing this is also your strongest performer, the arithmetic changes and the conversation gets harder to open. That case has its own way of going wrong.

When nothing finishes unless you chase it

Here the words are the problem. Ownership, initiative and proactive are placeholders. Define them by pointing at the moment they went missing.

Vague. "I need you to take more ownership."
Specific. "The export job failed Saturday. You flagged it in the channel and stopped. Whoever finds it fixes it or names who will, before closing the laptop." [what happened, where it stopped, what should follow]

Vague. "You are not following through."
Specific. "You agreed to send the client the revised scope by Thursday. It is Tuesday, it has not gone, and you have not mentioned it." [what was agreed, by when, current state]

Vague. "Be more proactive."
Specific. "You saw in June that the reporting query would break at scale. You mentioned it once and moved on. I want the problem, a proposal, and a date." [what they saw, what they did, what you meant]

Vague. "You need to close the loop."
Specific. "Casey asked for the numbers on the 9th and again on the 14th, and I heard it from him. A reply saying Friday would have ended it." [who asked, when, how often, what would close it]

When another team stops wanting to work with them

Cross-team feedback is second hand by definition, which is why it needs more precision, not less. Say who told you, and whether you agree.

Vague. "You need to work better with sales."
Specific. "Morgan's team stopped bringing you into deal reviews and started routing questions through me. That began after the pricing thread in August." [which team, what changed, roughly when]

Vague. "There is a bit of friction there."
Specific. "Two people there told me your review comments read as a flat no. I went back and read them. I can see why." [who said it, what they said, whether you agree]

Vague. "Try to be more collaborative."
Specific. "You made the schema change Thursday and told the data team Monday. They rebuilt two dashboards." [what was done, who paid, the right order]

Vague. "They say you are hard to reach."
Specific. "Three support requests have sat over a week and two were escalations. Answer or decline within a day." [the count, the age, the standard you want]

When the feedback itself is the problem

Some people argue with every example, and any constructive criticism becomes a trial about whether that instance was fair. Name the pattern out loud, or you relitigate single events forever.

Vague. "You get defensive when I give you feedback."
Specific. "The last three times I raised something, your first sentence was why it was not your call. Try a different shape: hear it, take a day, come back." [how often, what the first response was]

Vague. "You do not take criticism well."
Specific. "When I mentioned the deck on Tuesday, you said the brief was late. The brief was late. Both are true and the deck still needs to be right." [the exchange, the true part, what remains]

Vague. "Just be open to feedback."
Specific. "Every time I give an example we spend the meeting on whether the example counts. I want to talk about the pattern, not try the instance." [what happens, in what order, your next move]

Vague. "That is not what I said."
Specific. "I think you heard that as a verdict on your work overall. It is not. It is one document and one deadline." [what they heard, what you meant, the size]

Have this ready when the objection arrives mid sentence.

Most defensiveness is a request for time, delivered badly. Grant the time explicitly and there is nothing left to fight about in the room.

When someone has visibly checked out

The temptation is to open with a diagnosis shaped as a question. Are you okay? Is something going on at home? Describe the change and leave the explaining to them.

Vague. "Is everything okay? You seem off."
Specific. "Your camera has been off for three weeks and you have brought nothing to the last two one on ones. I have no theory. I am asking." [the observable change, the window, no diagnosis]

Vague. "You do not seem engaged anymore."
Specific. "Six months ago you argued in roadmap reviews. In the last four you have said nothing. That is a change and I want to understand it." [what they did before, what they do now]

Vague. "Are you looking for another job?"
Specific. "I would rather ask than tiptoe. Are you thinking about leaving? If you are, I still want to know, and it will not change how I treat you." [the direct question, plus the guarantee]

Vague. "Let me know if you need anything."
Specific. "Two things I can change this month are the on-call rotation and who runs the Thursday sync. Is either of them the problem?" [what is genuinely in your gift, named]

This does not work if you and the other person would describe the event differently. Every pair here assumes the facts are agreed and only the wording is in play. When they are not, this is not feedback, it is two accounts of the same week, and both have to be on the table before any sentence below lands.

The part that reading does not give you

Every line here is easy to read and hard to say. The difficulty is not vocabulary. It is that the moment you say the copy was due Tuesday and reached you Friday, their face changes and your next sentence stops being available.

That is where the softening happens. You add that it is not a big deal, that they have had a lot on. Both are true, and both delete what you just said. You leave believing you had the conversation. Nothing changes.

The fix is not more phrases. It is having said one out loud, to somebody who pushes back, enough times that the silence afterward stops feeling like something you must fill.