Communication
Constructive Feedback Examples for Work
Give constructive feedback people can act on: describe the behaviour, explain the impact, suggest a change. Examples for missed deadlines, meetings, quality and teamwork.
Constructive feedback describes a specific behaviour, explains its impact and suggests a change the person can actually make. It is not a compliment sandwich, and it is not a softened criticism the recipient has to decode. Done well, it is useful information delivered early, in private, with the genuine intention of helping someone succeed.
The examples below are fictional wording to adapt, covering the situations professionals ask about most: missed deadlines, meeting behaviour, work quality and teamwork. Every example follows the same structure—behaviour, impact, request—because that structure is what makes feedback constructive rather than personal.
What makes feedback constructive
Three things separate constructive feedback from criticism. First, it is about behaviour, not character: ‘the report went out with two figures unchecked’ rather than ‘you are careless.’ Second, it names a real impact, so the person understands why it matters. Third, it ends with something the person can do differently—feedback without a path forward is just a complaint.
Timing and setting matter as much as wording. Raise things within days, not months; do it in private; and choose a moment when neither of you is mid-crisis. Feedback saved up for a performance review arrives too late to be useful and feels like a verdict rather than help.
Check your intention before you speak. If the honest answer to ‘why am I giving this feedback?’ is ‘because I am annoyed’, wait a day. Constructive feedback is for the recipient's benefit, and they can tell the difference.
Example: missed deadlines
Weak version: ‘You need to be more reliable.’ This names a character trait, gives no evidence and offers no path. The recipient can only agree or defend themselves.
Constructive version: ‘The last two handovers arrived a day after we agreed, and each time the testing team had to replan their week. I want to understand what is getting in the way. Would it help to agree the date together, or to flag risks a few days earlier?’
Notice what this does: it cites specific instances, names the impact on another team, and opens with curiosity rather than blame. The question at the end is genuine—sometimes the deadline was unrealistic, and that is worth discovering.
Example: meeting behaviour
Weak version: ‘You dominate every meeting.’ Broad, absolute and easy to dispute.
Constructive version: ‘In yesterday's planning meeting, you responded to each of Priya's points before she had finished, and she stopped contributing halfway through. The team loses out when that happens—she knows the client history better than anyone. Could you let people finish and note your response before jumping in?’
Meeting feedback works best close to the event, privately, and tied to an observable moment. ‘You interrupted twice in yesterday's meeting’ is discussable; ‘you always interrupt’ starts an argument about the word ‘always.’
Example: work quality
Weak version: ‘This isn't good enough.’ The recipient learns nothing except that you are displeased.
Constructive version: ‘The analysis section compares this quarter with last quarter, but the client asked for a comparison with their competitors. I should have made that clearer in the brief. Could you rework that section against the competitor data by Thursday? Happy to talk through the structure first.’
Quality feedback should separate two questions: was the brief clear, and was the execution careful? Owning your part of a quality miss—an unclear brief, a moving target—makes the rest of the feedback easier to hear.
Example: teamwork and collaboration
Weak version: ‘You're not a team player.’ A label, not a behaviour.
Constructive version: ‘When the support team asked for help with the migration weekend, the request sat unanswered for three days and they assumed we had declined. Even a quick “I can't this week” would have let them plan. Could you reply to cross-team requests within a day, even if the answer is no?’
Collaboration feedback often lands better when you name the positive version you have seen: ‘When you flagged the API risk early last month, it saved the release. That same early flag is what support needed here.’ This is not softening the message—it is showing the person the behaviour is already in their repertoire.
The other half: receiving feedback
Constructive feedback is a skill in both directions. When you receive it, listen to the end before responding, ask for a specific example if the feedback is vague, and say what you will do with it—even if the answer is ‘I need to think about it.’
You do not have to accept every piece of feedback as accurate. You do have to treat it as information about how you are experienced. If three people independently tell you your updates are hard to follow, the useful question is not ‘are they right?’ but ‘what are they seeing?’
ERA Skills is built around that question. The free self-assessment covers five interpersonal skills, and you can invite colleagues to give pooled, anonymous feedback—results require at least three completed raters, and no individual answer is ever shown. It turns ‘how am I experienced?’ from a guess into something you can see.