# Negative Performance Feedback Examples: What the Good Ones Sound Like Canonical URL: https://headwayskills.com/knowledge/working-with-your-manager/negative-performance-feedback-examples/ Markdown URL: https://headwayskills.com/knowledge/working-with-your-manager/negative-performance-feedback-examples.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving working with your manager at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Negative performance feedback examples for deadlines, work quality and communication, plus how to tell if feedback is fair and what to say in the room. ## Key facts - Title: Negative Performance Feedback Examples: What the Good Ones Sound Like - Category: Working with Your Manager - Primary skill: Working with Your Manager - Related skills: Building Self-Awareness, Communication - Primary keyword: negative performance feedback examples - Source page: https://headwayskills.com/knowledge/working-with-your-manager/negative-performance-feedback-examples/ ## What this page covers - Negative performance feedback examples for deadlines, work quality and communication, plus how to tell if feedback is fair and what to say in the room. - Practical guidance for negative performance feedback examples - How this topic connects to Working with Your Manager ## Detailed explanation Nobody enjoys the sentence that starts, "There's something I want to raise with you." Negative performance feedback examples worth learning from all share one shape: they name a specific, observable behavior, describe its impact, state the expectation that was missed, and point to what should happen next. "You submitted three reports after their agreed deadline this quarter" is feedback. "You are unreliable" is a verdict. Only the first one can be acted on. That same shape is also the fastest way to read feedback that has just landed on you — and to work out how worried you actually need to be. ## What makes a negative feedback example usable instead of just harsh? The sample-phrase libraries that dominate this topic — PerformYard, Deel, Business Management Daily — converge on the same four parts. Name the observable action or pattern rather than a personality trait. Describe the impact on the work, the team, or the project. State the standard that was expected. Then point to what happens going forward. Strip any of the four out and the feedback stops being usable. "Your work isn't good enough" contains none of them, which is why it lands as an insult rather than an instruction. "In the last project, the report you submitted had several formatting errors, and it was missing key data on customer engagement" contains the first two — and you can get the rest out of your manager with a single question. ## Is negative feedback the same as constructive criticism? Not quite. "Negative" describes the direction: something isn't working. "Constructive" describes whether it was built to be acted on. Plenty of feedback is negative and constructive. Some is negative and useless. Most of the phrase banks lean hard on softening. Instead of "You don't meet deadlines consistently," they suggest something closer to "It would be beneficial for the team if you could enhance your time management skills." Instead of "Your reports have had several errors," they offer "Paying closer attention to detail could help improve the accuracy of your reports." CultureMonkey recommends the same move with "I" statements — "I noticed that you arrived 15 minutes late this week" rather than "You're always late." Softening genuinely helps people hear the message. It also has a cost worth knowing about: the gentler the wording, the easier it is to nod along and completely miss that you were just told something serious. ## Negative performance feedback examples for deadlines and time management Missed deadlines are the most common category across every phrase library, and the good examples all count something: - "You submitted three reports after their agreed deadline this quarter, which pushed the client summary out by a day. I need drafts by Thursday so there's time to review them." - "The last two sprints both closed with items rolled over. Let's look at how you're estimating the work at the start of the week." Notice what does the work in each: a number, a date, a consequence, and a specific ask. If you are on the receiving end of one of these, the number is a gift — it tells you exactly what "fixed" would look like, and roughly how long you have to get there. ## Examples for work quality and accuracy - "In the last project, the report you submitted had several formatting errors, and it was missing key data on customer engagement." - "Paying closer attention to detail could help improve the accuracy of your reports." Those two say roughly the same thing at very different volumes. The first is checkable — you can go and look at the report. The second isn't, and it is the version you are far more likely to hear, because it is much easier to say. When you get the second one, the useful response is a request for the first: which reports, and which errors? ## Examples for communication and working with others The phrase banks sort this territory into communication struggles, poor prioritization, and weak collaboration. Worked examples look like: - "In the last two project meetings, you cut in while Sam was walking through the numbers, and the budget question never got answered. In the next one, hold your points until she's finished." - "You've been taking questions from three teams at once and answering whoever asked most recently. Route them through the ticket queue so we can see what's actually pending." Same anatomy each time: named occasion, named effect, named next action. Feedback about how you work with people feels more personal than feedback about a deadline, which is precisely why the specific version matters more here rather than less — vagueness in this category reads as a comment on your character. ## How do I know if the feedback I got is fair? Run it against the four parts. Can you name the occasion it refers to? The effect it had? The standard you were meant to meet? If you can't, you weren't given an assessment; you were given an impression, and the right response is a question rather than a defense. The harder case is feedback that is specific, checkable, and about something you genuinely could not see from where you sit. That isn't unfairness — it's [a blind spot](/knowledge/self-awareness/how-to-improve-self-awareness/), and blind spots surface in reviews precisely because nobody mentioned them earlier. Rather than relitigating one comment, it's worth [finding out which gaps are real](https://assessment.headwayskills.com/): the free work skills test gives you an outside read instead of a guess, and anything it surfaces is something you can work on. ## What should I say in the room? Almost every source on the receiving side opens with the same instruction: don't defend yourself in the moment. Fortune poses it as a choice between defending yourself and smiling and nodding, and the practical answer is neither. [Going on the defensive](/knowledge/self-awareness/handle-criticism/), as The Muse describes it, mostly makes you look uncooperative and resolves nothing. What works instead is visible openness. Ask a Manager suggests something close to "I really appreciate you telling me this — I didn't realize it was a problem," on the reasoning that the more open you appear, the more useful detail your manager will volunteer. Then ask for examples: which occasions, which projects, what "better" would actually look like. And you are allowed to say you'd like some time to think it over. ## What if I think the feedback is wrong? Say so — afterward, calmly, with specifics. The consistent advice is to [bring examples or data](/knowledge/working-with-your-manager/disagree-with-your-manager/) and keep the conversation on facts rather than on how the feedback felt. If it was delivered in front of other people, acknowledge it briefly and ask for a private follow-up rather than arguing it out publicly. It helps to separate two different disagreements. "That didn't happen" is a factual dispute and usually gets settled fast. "That happened, but here's the context you're missing" is an interpretation dispute, and it's the far more common one. That second conversation goes much better as a question about what your manager was expecting than as a correction of what they said. ## What happens after a negative performance review? Follow up in writing. The guidance here is unanimous: send a short summary of what you understood, with a small number of measurable goals and dates attached. It turns a conversation the two of you might remember differently in six months into a shared record. Then [ask for check-ins](/knowledge/working-with-your-manager/one-on-one-meetings/). Managers are routinely advised to schedule regular follow-ups — biweekly meetings to review progress against the goals — but plenty never get around to it, and there is nothing stopping you from proposing it yourself. It's also worth holding on to the reframe The Muse offers: a manager who invests the time to spell out what needs work usually believes you're capable of closing the gap. ## The skills that make these conversations easier to handle Read back across those answers and remarkably little of it was about wording. The examples were the easy part. What decided the outcome each time was how the conversation itself got handled. **Working with Your Manager** carries most of the load. The reviews that go badly are usually the ones where the relationship only got attention twice a year — where your results were never visible in between, so one weak quarter becomes the entire story. Treating it as a partnership means coming prepared, asking for specifics, keeping the conversation future-focused, and saying plainly what you want out of the next six months. Disagreeing with your manager is fine; it's the avoidance that costs you. **Building Self-Awareness** is what turns feedback into something usable. There's a sequence to receiving it: understand what is actually being said, add your own view of it, then reflect properly afterward when you're out of the room and your pulse has come down. It also means asking for feedback long before a review comes around — specific, forward-looking advice you requested is far easier to act on than a rating you were handed. **Communication** governs both ends of the exchange. Leading with the main point, staying direct without making it personal, and choosing a conversation for the difficult part and writing for the record are the same moves whether you're receiving feedback or giving it to a peer on a shared project. Handling disagreement without damaging the working relationship belongs here too. None of these are things you either have or don't — they're three of a wider set of **twelve work skills**, all of them learnable. And a review only ever reflects what your manager happened to notice this cycle, so it's worth seeing [the skills a review misses](https://assessment.headwayskills.com/) in the free test: the ones nobody mentioned are often the ones quietly holding you back. Some of this probably already sounds like how you operate — perhaps you're the one who asks for the concrete example instead of leaving the room with a vague sense of having been told off. Reading up on what good feedback looks like before your next review, rather than after one goes badly, is the step most people skip entirely. The parts that don't come naturally yet are learnable, and you can build them without becoming a different person at work. They also compound: the further into a career you get, the more of your progress runs through conversations exactly like this one — and the less anyone bothers to soften them for you. ## Find out where your own work skills stand You know what good feedback looks like now. The only thing left is knowing which of your own skills would change how the next conversation goes. The **free** Work Skills Test is a short self-assessment covering all twelve work skills — including the manager relationship, self-awareness, and communication habits these conversations run on — and it points you to the ones worth your attention first. **[Take the test](https://assessment.headwayskills.com/)** *Free to take, and most people finish in about 7 minutes.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Negative performance feedback examples for deadlines, work quality and communication, plus how to tell if feedback is fair and what to say in the room. ### Which Headway skill does this connect to? This guide connects primarily to Working with Your Manager. It also relates to Building Self-Awareness, Communication. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/self-awareness.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/working-with-your-manager/negative-performance-feedback-examples/ Preferred summary: "Negative performance feedback examples for deadlines, work quality and communication, plus how to tell if feedback is fair and what to say in the room." ## Change log - 2026-07-07: Content collection version published.