Negative feedback examples are short, specific statements a manager uses to name a behavior that missed the standard, explain its impact, and agree on the next step. Below are 95 examples by situation, role, and industry.
Managers need negative feedback examples because the hardest part of correcting someone is finding words that are specific, fair, and calm in the moment. A tested script takes out labels and guesswork, keeps feedback consistent from one manager to the next, and lets the employee focus on the fix instead of the tone.
Most of the scripts here are corrective feedback, while developmental feedback works on a skill over months. The table shows how each type of negative feedback sounds.
| Type | Purpose | Example line |
|---|---|---|
| Corrective | Fix a specific gap | The invoice totals were off. Please add a totals check before you send. |
| Developmental | Build a skill over time | Your analysis is strong. Next quarter, let's work on presenting it to leadership. |
| Evaluative | Rate work against a standard | This report meets the format standard and misses the accuracy standard. |
| Directive | Say exactly what to change next | Send the weekly update by Monday at noon. |
| Coaching | Help the person find the fix | What caused the delay, and what would you try next time? |
| Expert | Share specialist knowledge | Legal needs 48 hours for review, so build that into the deal timeline. |
Negative feedback describes a gap between the expected and actual behavior. Constructive feedback is negative feedback delivered with specifics and a path forward. Destructive feedback attacks the person, uses labels, or offers no fix. A manager can turn most negative feedback into constructive feedback by adding a concrete example, its impact, and one agreed next step.
| Aspect | Negative | Constructive | Destructive |
|---|---|---|---|
| Focus | The gap between expected and actual | The behavior and the fix | The person |
| Language | Names what fell short | Specific, neutral, about the future | Labels, absolutes, sarcasm |
| Timing | Any time | Soon after the event, in private | Often in public or in anger |
| Outcome | Awareness of the gap | An agreed next step | Defensiveness and lower trust |
| Example | "The report was late." | "The report was late, so the call moved. Can you flag risks earlier?" | "You're always late. Typical." |
These constructive negative feedback examples show the same message rewritten so it lands as a fix.
| Destructive version | Constructive version |
|---|---|
| "The inventory count was due Friday and isn't done. What's blocking it, and can you finish by Tuesday?" | |
| "Two figures in Monday's forecast were swapped. Please add a second check before you send it." | |
| "In yesterday's meeting, you interrupted Ana three times. Please let people finish before you respond." | |
| "The demo crashed because the test data wasn't loaded. Let's add data setup to the demo checklist." | |
| "Three tickets waited over a day for a first reply. Please reply within four hours, even if only to acknowledge." | |
| "When the plan changed, you said 'whatever' and left the call. If you disagree, tell me directly so we can talk it through." |
Managers should give negative feedback because most employees ask for it and perform better after it. In a Zenger Folkman study published in Harvard Business Review, 57% of employees preferred corrective feedback over praise. When managers avoid it, small problems repeat, peers absorb the extra work, and the employee loses the chance to fix the issue early.
of employees said their performance would improve if their managers gave corrective feedback.
of people told a research assistant about a visible smudge on the assistant's face. People underestimated how much others wanted constructive feedback.
Source: Abi-Esber, Abel, Schroeder and Gino, Journal of Personality and Social Psychology
Avoiding negative feedback has costs that build over time:

"So leaders can role model, reinforce, recognize and celebrate behaviors that are all aligned with the expectations of the company. And they can also coach and give constructive feedback when they see behaviors that are out of alignment."Watch episode
To give negative feedback, prepare one specific example, describe the situation and the observable behavior, explain the impact, ask for the employee's view, and agree on a next step with a follow-up date. This sequence follows the Situation, Behavior, Impact (SBI) model from the Center for Creative Leadership, with an added action step.
Situation: "In Thursday's product demo for the regional sales team,"
Behavior: "you skipped the pricing slide and moved straight to questions."
Impact: "Three reps emailed me afterward asking how to quote the new tier. What happened on that slide?"
Next step: "Can you send the pricing walkthrough to the team by Tuesday? Let's review it together on Wednesday at 10."
Negative feedback is one of the most common difficult conversations a manager has. For preparation tips beyond the script, see this guide to difficult conversations at work.
These 50 negative feedback examples cover ten common situations managers handle, from missed deadlines to feedback that gets ignored. Each example uses the SBI structure: it names when it happened, what the person did, and why it mattered, then closes with a request. Adapt the details to your own case before using any script.
5 SBI scripts, each with the situation it fits and why it works.
Say this:The client report was due Tuesday and went out Wednesday afternoon. The account lead had to delay the client call. What got in the way, and what do you need to hit Friday's deadline?
Say this:The API task moved from sprint 14 to sprint 15 and then to sprint 16, and I found out at the review each time. The release date moved with it. Can you flag risk to me as soon as a task looks likely to slip?
Say this:On Monday you agreed to finish the vendor comparison by Thursday, and on Thursday it was half done. Procurement had already booked the decision meeting. Next time, check your workload before you commit, and tell me if the date needs to move.
Say this:The onboarding deck was due to HR yesterday at noon, and I heard it was missing from HR before I heard it from you. That put me on the back foot with their director. When a deadline is at risk, message me before it passes.
Say this:Your budget figures reached Sam two days after the agreed date, so Sam had one day left to build the board summary, and it went out with errors. What would help you get inputs to Sam on time next month?
5 SBI scripts, each with the situation it fits and why it works.
Say this:In last week's sales report, the regional totals did not add up to the national figure, and the VP spotted it in the meeting. Before you send the next report, run the totals check and ask a peer to review the summary page.
Say this:The checkout fix merged on Wednesday without unit tests, and it broke discount codes for four hours while support handled the tickets. Every merge to the main branch needs passing tests. What support do you need to make that routine?
Say this:The renewal email that went to 3,000 customers had the wrong product name in the subject line, and two customers asked if it was spam. Please send every external email to the editor for a second read before you schedule it.
Say this:The design brief asks for mobile and desktop views of each mockup, and the three you shared today only have desktop. The client review is Thursday. Can you add the mobile views by Wednesday noon so we can check them together?
Say this:This is the third payroll file this quarter with the overtime column formatted as text, and each time payroll fixed it by hand. I'd like to understand what causes it. Can we walk through your process together tomorrow morning?
5 SBI scripts, each with the situation it fits and why it works.
Say this:The project sponsor emailed me twice this week asking for status, because the last update went out ten days ago. It makes the project look out of control. Please send a short status note every Monday, even when nothing has changed.
Say this:Your proposal email to the leadership team ran to two screens, and the request was in the last paragraph. Two directors replied asking what decision you needed. Next time, put the decision you need in the first line, then add the detail.
Say this:In the team channel yesterday, you replied 'already answered, read the thread' to a new hire's question. They told me afterward they felt embarrassed to ask again. Can you point people to the answer with a link and a friendlier line?
Say this:You knew on Tuesday that the supplier would miss the shipment, and the team found out on Friday. We lost three days we could have used to plan around it. When you learn something that affects the schedule, share it in the team channel that day.
Say this:In today's design review, you cut in while Ana and Wei were explaining their options, three times by my count, and neither finished their point. In the next review, let each person finish before you respond. I'll help keep time.
5 SBI scripts, each with the situation it fits and why it works.
Say this:During quarter-end close, you declined the two extra reconciliations the team asked you to take, and two colleagues worked late all week to cover them. At the next close, can you take on at least two extra accounts?
Say this:In the client presentation, the analysis slide was introduced as your work, and Jordan built most of it. Jordan noticed. When you present shared work, credit the people who built each part. Could you mention Jordan's part in the follow-up email?
Say this:The new onboarding flow launched without input from support, and support learned about it the day it went live, with no scripts ready for customer questions. Before the next launch, share the plan with support at least one week ahead.
Say this:In the last three planning meetings, you argued against the agreed approach after we had decided, and the team spent another half hour each time. Raise concerns before we decide. Once we decide, I need you to back the plan.
Say this:Your Tuesday shift ended without handoff notes on two open orders, so the next shift phoned a customer who had already been called twice that day. Please complete the handoff log before you clock out, every shift.
5 SBI scripts, each with the situation it fits and why it works.
Say this:In this morning's client call, you were on your phone for most of the pricing discussion, and the client had to ask you a question twice. On client calls, please put the phone away and take notes for the team.
Say this:When Lee shared the referral idea in the team meeting, you said 'that will never work' and moved on, and nobody else offered an idea after that. If you have concerns about an idea, ask a question about it first.
Say this:You came to the quarterly review without the numbers we agreed you would bring, so we had to move the budget item to next week. Please send your figures to me the day before each review so we can check them together.
Say this:In the stand-up, when the release slipped, you said 'great planning as usual.' The project lead took it personally and the stand-up ended early. Please raise frustrations with me or the project lead directly, in private.
Say this:On Thursday's call, you spoke over the client twice while they were describing the integration problem, and they repeated themselves at the end. On the next call, let the client finish, then summarize what you heard before you answer.
5 SBI scripts, each with the situation it fits and why it works.
Say this:You clocked in 15 to 20 minutes late on four of your last six shifts, and the opening checklist fell to one person. I need you here at the start of each shift. Is something making the start time hard to hit?
Say this:You joined the weekly planning call ten minutes late for the last three weeks, so we recapped the first agenda item for you each time. Please join on time, or message me before the call if you will be late.
Say this:On Monday you did not come in and did not call, and we found out at 10 a.m. The line ran short for two hours. Our policy is to call the shift lead before your start time. Can you commit to that from now on?
Say this:Your lunch breaks this week ran 20 to 30 minutes past the hour, and one person covered the front desk at the busiest time. Please keep breaks to the scheduled hour, and tell me if your schedule needs to change.
Say this:Twice this week you left at three without letting the team know, and a customer call to your line went unanswered. If you need to leave early, put it in the team calendar and arrange cover first.
5 SBI scripts, each with the situation it fits and why it works.
Say this:In the review, you said the target was missed because marketing sent weak leads. Some of that may be true, and your follow-up rate was 40 out of 100 leads against a goal of 70. Let's look at the part you control and agree on a plan for this month.
Say this:When the shipment went to the wrong address, you told the customer the system made the error, and the label was entered by hand. I need you to own errors with customers and then fix them. Let's call the customer back together today.
Say this:The supplier follow-up was assigned to you in last Monday's meeting, and nobody has contacted the supplier since. The quote expires tomorrow. Can you call them today, and track assigned items on the task board from now on?
Say this:When the dashboard broke on Tuesday, you waited for me to assign the fix, and it stayed down until Wednesday. You have the access and the skills to fix it. Next time, start on it and keep me posted.
Say this:We have discussed late expense reports three times, and each time there was a different reason. Finance has now flagged your account. What would make this one task reliable for you, starting with this month's report?
5 SBI scripts, each with the situation it fits and why it works.
Say this:Your reply to the customer yesterday was one line: 'This is in the FAQ.' The customer rated the chat one star. Please answer the question directly first, then share the FAQ link for more detail.
Say this:You told the client we would deliver the custom report by Monday, and the data team needs two weeks to build it. The client now expects something we cannot do. Before promising a date, check with the team that owns the work.
Say this:Your average first response this week was six hours, against our four-hour standard, and three customers followed up to ask if anyone had seen their request. What is slowing your queue, and what would help you get back under four hours?
Say this:When the guest complained about the room, you explained why the complaint was wrong before you apologized, and the guest asked for a manager. Next time, acknowledge the problem first, then explain what you can do.
Say this:You told the customer on Monday you would call back with an update by Wednesday, and they called us on Friday instead. Please log every callback promise in the CRM with a reminder, so none get missed.
5 SBI scripts, each with the situation it fits and why it works.
Say this:This week you spent two days refining the internal style guide, and the client proposal due Friday is still a draft. The proposal comes first. Can you finish the draft by Thursday and pick up the style guide next week?
Say this:You took on three new projects this month, and the migration, your main goal, has stalled. Before you say yes to new work, check with me so we can decide together what moves.
Say this:In our last two check-ins, you had five tasks started and none finished, and the QA team is waiting on two of them. Finish the two blocked items first, then pick up the next one.
Say this:Legal asks for contracts 48 hours before signing, and the last two arrived the morning of the signing, so legal reviewed them in a rush. Please build the send date into your timeline for each deal.
Say this:Your calendar shows 28 hours of meetings this week, and the analysis you own slipped again. Which of these meetings could you skip or hand to someone else, so you get two clear mornings a week?
5 SBI scripts, each with the situation it fits and why it works.
Say this:In our last two one-on-ones, we agreed you would add test cases to your pull requests, and the last four still have none. I want to understand what is blocking this. What would make it happen on the next one?
Say this:When I raised the report errors last week, you said the template was the problem and ended the conversation. I want to solve this with you. Can we look at one report together and find where the errors start?
Say this:We agreed in March that all quotes go through the pricing tool, and the last three you sent were built in a spreadsheet, two with old rates. From today, use the tool for every quote, and tell me if something in it does not work for you.
Say this:Your peers raised the same point about missed handoffs in the team retro, and you said they were overreacting. When several people see the same issue, it is worth a closer look. What do you think is causing the handoff gaps?
Say this:After our talk in June, your reports arrived on time for six weeks, and the last three were late again. The change worked when it was a priority. What changed, and how do we make it stick this time?
Negative feedback changes with the relationship. A manager speaking to a direct report can set expectations, a peer can only describe impact and make a request, and a senior leader giving feedback to a manager should focus on team outcomes. These 20 examples cover five common giver and receiver pairs.
For feedback you give upward, see feedback for your manager.
4 SBI scripts, each with the situation it fits and why it works.
Say this:You have canceled three of our last four one-on-ones, and I haven't been able to help with the migration blockers you mentioned. These meetings are for you. Can we keep Thursday at 2 p.m. fixed for the next month?
Say this:In your review, we agreed you would close 12 deals this quarter, and you are at five with three weeks left. I want to help you get closer. Which of your open deals can we work on together this week?
Say this:Since we moved to the new ticket system on the first, you have logged your work in the old spreadsheet, so the team dashboard shows no tickets for you. Please log everything in the new system starting today.
Say this:In Monday's board update, the slides had no summary, and the board asked three times what the main point was. For the next update, open with one slide that states the result and the request.
4 SBI scripts, each with the situation it fits and why it works.
Say this:Your numbers this quarter are the best on the team, and four of your contracts went out without legal review. That exposes the company to risk. Strong results don't change the rule, and every contract needs legal review from now on.
Say this:Your code is the strongest on the team, and your review comments last sprint made two junior engineers stop asking you questions. I want them learning from you. In reviews, explain the reason behind each change you ask for.
Say this:You rewrote both of Lina's drafts this week instead of giving notes, so Lina isn't learning the format. As a team lead, growing others is part of your job now. Give written notes on the next draft and let Lina revise it.
Say this:You pitched the pricing change to the VP before discussing it with the product team, and product heard about it from the VP. They felt bypassed. Good ideas still need the right path. Share the next one with the owners first.
4 SBI scripts, each with the situation it fits and why it works.
Say this:In your first month, three of your tickets went out with the wrong setup because our internal guide is out of date. Nobody expects you to know our quirks yet. Please ask in the team channel whenever something looks unclear.
Say this:You have been joining stand-up with your camera off, and on this team we keep cameras on for stand-up so we can read the room. It's a small thing, and nobody would have told you. Can you turn it on from tomorrow?
Say this:Last week you changed the shared report template without checking with the team, and two dashboards broke. I like that you spotted the problem. For shared tools, propose the change in the team channel first.
Say this:At 60 days, you are handling about half the case volume we planned for this stage, and your quality scores are strong. Let's find where the time goes. Can you shadow Ravi for two afternoons this week?
4 SBI scripts, each with the situation it fits and why it works.
Say this:The last two times we co-owned a launch, your section came in after our agreed date, and I had to explain the delay to marketing. Next time, can we set an internal date two days earlier so we both have a buffer?
Say this:In the last two team meetings, I couldn't finish my updates before you came in with a related point. I want to hear your input. Could you let me finish first, and then jump in?
Say this:The last three files you handed to me were missing the client contact details, and I spent about an hour each time tracking them down. Could we add contacts to the handoff template we both use?
Say this:In yesterday's client meeting, you corrected my figure in front of the client before checking with me. You were right about the number, and I'd have preferred a quick message. Can we agree to flag those to each other privately?
For more scripts between colleagues, see these peer feedback examples.
4 SBI scripts, each with the situation it fits and why it works.
Say this:Your team's latest pulse survey has the lowest score in the department on 'my manager gives me useful feedback,' and several comments mention canceled one-on-ones. What gets in the way of holding them, and what support would help?
Say this:Two of your team members raised a colleague's missed deadlines with HR, and they said nobody had discussed it with that colleague. Waiting has let the problem spread. Let's plan that conversation together this week.
Say this:Three people on your team told us you corrected their work during the Monday team call, and they felt singled out. Please move individual corrections to one-on-ones and keep the team call for shared updates.
Say this:The reviews you submitted rated four people below expectations, and none included examples or earlier conversations. HR cannot support those ratings without documentation. Please add one dated example per rating before calibration.


"With CultureMonkey, managers are using the data that comes back in ways to help them engage with their staff, re-engage with their staff, look forward to different opportunities to bring the staff together, and recognise them as well."Read the Air General case study
Industry changes what negative feedback sounds like because the impact lands on different people: patients in healthcare, customers in retail, guests in hospitality, and safety in manufacturing. These 25 examples cover five industries, each with the situation it fits and why the wording works.
5 SBI scripts, each with the situation it fits and why it works.
Say this:During this morning's shift change, the medication timing for bed 12 was left out of the handoff, and the next dose was given an hour late. Please use the full handoff checklist for every patient, every shift.
Say this:Your charting from Tuesday's shift was completed on Thursday, and the day team made decisions without your notes. Please finish charting before the end of each shift, and tell me if your patient load makes that impossible.
Say this:When the family asked about discharge timing yesterday, you said 'I already told you' and left the room, and they complained at the unit desk. When families ask again, answer again and offer to write it down for them.
Say this:In this week's audit, you were observed entering two patient rooms without hand hygiene, which is our highest-risk gap. Please follow the protocol on every entry, and tell me if the dispensers on your corridor are empty.
Say this:You arrived after the safety huddle twice this week, so you missed the fall-risk update for your patients. The huddle starts at 7 sharp. Can you plan to be on the unit by 6:55?
5 SBI scripts, each with the situation it fits and why it works.
Say this:During Saturday's rush, you were restocking shelves while four customers waited at the fitting rooms, and two left without buying. When there is a queue, serve the customers first, and restock once the queue clears.
Say this:Your drawer has been short three times this month, by small amounts each time. I'm not assuming anything, and we need to find the cause. Let's count your drawer together at close tonight and see where the gap comes from.
Say this:The front table display did not match this week's planogram, and the regional manager flagged it during the visit. Please check the planogram photo before you finish each display, and ask me if a product is missing.
Say this:A customer was refused a return yesterday without the policy being explained, and they posted about it online. Every time a return is refused, explain the policy and offer the exchange option.
Say this:On Tuesday afternoon, you and the other associate took breaks at the same time, and the floor was empty for 15 minutes. Please check the break schedule with the shift lead before you leave the floor.
5 SBI scripts, each with the situation it fits and why it works.
Say this:Room 418 asked for extra towels at 8 p.m., and they arrived after 10 when the guest called again. The guest mentioned it in the review. Please log every request in the system so the next person can see it.
Say this:Two guests this week wrote that check-in felt rushed, and both checked in at your desk. Neither heard about breakfast hours or parking. Please walk every guest through the welcome card, even when the line is long.
Say this:You started the dinner shift without your name badge twice this week, and a guest who wanted to thank you couldn't find your name. Please wear the badge every shift. Do you need a replacement?
Say this:On Friday, tickets from your station averaged 22 minutes against our 15-minute target, and two tables sent food back cold. Let's look at your prep list together before Saturday service.
Say this:When the guest complained about noise last night, you offered a discount without telling the duty manager. The guest still left angry, and we had no record. Please call the duty manager for any complaint that involves compensation.
5 SBI scripts, each with the situation it fits and why it works.
Say this:This morning you cleared the jam on line 3 without locking out the machine. That step prevents serious injuries, and it applies every time. Walk me through the lockout steps now, and use them on every jam.
Say this:The last hour of your Thursday shift had four times the defect rate of the rest of the shift, and QA pulled two pallets. Keep the same check pace through the end of the shift, even if output drops.
Say this:You were near the press without safety glasses twice this week. The rule protects your eyes, and I need it followed every time. Is there a problem with the glasses you were issued?
Say this:The downtime section of your shift report has been blank for three nights, so maintenance could not see why line 2 stopped. Please record every stop over five minutes with its cause.
Say this:You noticed the material shortage on Monday and told the planner on Wednesday, after the line had stopped. Please raise any shortage with the planner during the shift you spot it.
5 SBI scripts, each with the situation it fits and why it works.
Say this:The payment alert fired at 2:10 a.m. on Sunday during your on-call shift, and the backup picked it up at 3:30. Customers could not check out for over an hour. What happened, and what would make sure you hear the next alert?
Say this:Your last pull request changed about 2,000 lines across 40 files, and it sat for a week because nobody could review it properly. Please split work into pull requests of a few hundred lines that each do one thing.
Say this:The new billing service shipped without a README or runbook, and support couldn't answer customer questions during the first outage. Please add both before we close the ticket.
Say this:Your last four estimates were two days each, and every task took more than a week. The roadmap we shared with sales was built on those numbers. Let's break your next estimate into steps together before you share it.
Say this:Support reported the login bug on Monday, and you closed it as 'cannot reproduce' without contacting them. By Wednesday it affected 200 users. Before you close a support ticket, talk to the person who filed it.
To give negative feedback in a positive way, focus on the future, describe the behavior without labels, show you believe the person can improve, and invite their ideas for the fix. Positive framing changes the tone, and the message itself stays clear. Each example below keeps the problem explicit and frames the next step as shared work.
of respondents agreed that negative feedback, delivered appropriately, is effective at improving performance.
Old wording"Your reports are always wrong."
Positive framing"I want your reports to be the ones leadership trusts first. Last week's had two totals off. What check could we add so the next one is clean?"
Old wording"You need to stop missing deadlines."
Positive framing"You do strong work when you have the time. The last two deadlines slipped. What would help you plan the next one so it lands on the date?"
Old wording"You're too quiet in meetings."
Positive framing"Your analysis of the pricing issue was the best I saw, and the team never heard it. Could you share one point in Thursday's meeting?"
Old wording"Customers find you rude."
Positive framing"Customers rate your fixes highly, and two said your replies felt short. One friendly line in each reply would match the quality of the fix."
Old wording"Your presentation was a mess."
Positive framing"The data in your deck was solid, and the story was hard to follow. Let's outline the next one together before you build the slides."
Positive framing works best when praise also happens on its own. These positive feedback examples help managers give it in separate, specific moments.
The feedback sandwich, praise then criticism then praise, often weakens the message because employees learn to wait for the criticism hidden between compliments. Researchers at Ivey Business School reported that the method creates confusion and that people end up ignoring the positive and resenting the negative. A direct SBI conversation, with genuine praise given separately, keeps the feedback clear.
| Aspect | Feedback sandwich | SBI plus next step | Direct with separate praise |
|---|---|---|---|
| Structure | Praise, criticism, praise | Situation, behavior, impact, agreed action | Clear critique now, specific praise at other times |
| Clarity of the message | Low: the criticism gets lost between compliments | High: one behavior and its effect | High: the critique stands on its own |
| Effect on trust | Compliments start to feel like a buffer | Feels fair because it is specific and checkable | Praise stays credible because it is never a buffer |
| Best used for | Rarely; praise lands better on its own | Most corrective conversations | Teams with regular one-on-ones |
Give negative feedback privately, as close to the event as possible, and in a format that matches the work setting. Use a live conversation for anything serious, video with cameras on for remote employees, a short follow-up note for written records, and a private moment at shift change for frontline teams. Avoid email as the first channel.
| Aspect | In person | Video call | Written note | Shift huddle or private moment |
|---|---|---|---|---|
| Best for | Serious or repeated issues | Remote and hybrid employees | The recap after a live talk | Frontline and shift teams |
| Timing | Within 48 hours, in a private room | Within 48 hours, cameras on | The same day as the conversation | At shift change, away from customers |
| Watch out for | Open-plan spaces where others can hear | Multitasking and muted cameras | Using it as the first delivery | Correcting someone in front of the crew |
| Follow-up | A written recap | A written recap and a check-in date | The employee confirms the next step | A note in the shift log and a check-in next shift |
Remote negative feedback needs a scheduled video call with cameras on, so both people can read tone. Book it as a one-on-one and name the topic in the invite, so the employee is not caught off guard. Keep chat for the follow-up. Share your screen if the issue involves a document, and point to the exact line. End by agreeing on the next step out loud, then send the recap the same day.
Frontline employees rarely have a desk or a calendar, so find a private moment at shift change, away from customers and the rest of the crew. Keep it short: one behavior, one impact, one ask. Record it in the shift log. To hear from deskless teams in return, use frontline employee surveys and multilingual and omni-channel surveys they can answer by SMS, WhatsApp, or QR code.
Written negative feedback works best as the recap after a live conversation. Restate the situation, the behavior, the impact, and the agreed step with its date in four or five plain sentences. Leave out adjectives and opinions. Ask the employee to reply to confirm the next step, and keep the note where HR policy says records belong.
Communication driver score on a 0 to 10 scale, by company size, Q3 2026 edition.
| Company size | Communication (0 to 10) |
|---|---|
| Under 100 employees | 7.42 |
| SMB (100 to 500) | 7.91 |
| Mid-market (500 to 2,000) | 8.00 |
| Enterprise (2,000+ employees) | 8.19 |
CultureMonkey's benchmark data shows the lowest Communication scores in companies under 100 employees. See how CultureMonkey builds its benchmarks.
Source: CultureMonkey People Science, Employee Engagement Benchmarks by Company Size 2026, Q3 2026 edition, about 11 million employee survey responses.
The most common mistakes are being vague, using absolutes like always or never, labeling personality, delivering it in public, stacking months of issues into one meeting, and skipping the follow-up. Each mistake shifts attention from the behavior to the relationship. The table below pairs each mistake with phrasing to use instead.
| Mistake | What it sounds like | Say this instead |
|---|---|---|
| Being vague | "You need to step it up." | "Two of your last three reports missed the Friday deadline." |
| Using absolutes | "You never listen." | "In today's meeting, you replied before Kai finished the question." |
| Labeling personality | "You're careless." | "The order form had the wrong address for two customers." |
| Correcting in public | A correction in the team meeting | A one-to-one conversation later that day |
| Stacking issues | Six months of issues saved for the review | Each issue raised within days of the event |
| Skipping the follow-up | "Okay, so just do better." | "Let's check in Friday to see how the new checklist is working." |
| Hedging until the point is lost | "It's probably nothing, but maybe..." | "I want to talk about one thing: the missed client call on Tuesday." |
| Comparing to coworkers | "Why can't you be more like Sam?" | "The standard for this role is a reply within four hours." |
Every one of these mistakes makes it harder for employees to speak up later. Protecting psychological safety means correcting the work while keeping the person safe to disagree.
Negative feedback becomes a performance improvement plan when the same issue continues after documented conversations with clear expectations and support. A practical threshold is two or three documented feedback conversations with no lasting change. At that point, HR joins, goals become formal, and the timeline and consequences are written down.
| Rung | Trigger | Who owns it | Record and next check-in |
|---|---|---|---|
| 1In-the-moment feedback | First time the issue is seen | Under 100 employees: Manager100 to 1,000: ManagerEnterprise: Manager | What gets written down: A short note in the manager's own logNext check-in: At the next one-on-one |
| 2Documented one-on-one | The issue repeats after in-the-moment feedback | Under 100 employees: Manager100 to 1,000: ManagerEnterprise: Manager, with the HR business partner informed | What gets written down: A dated note: situation, behavior, impact, agreed stepNext check-in: The agreed follow-up date |
| 3Written expectations with HR aware | The issue continues after two or three documented conversations | Under 100 employees: Founder or people lead100 to 1,000: Manager with HREnterprise: Manager with the HR business partner | What gets written down: Written expectations shared with the employeeNext check-in: Weekly check-ins |
| 4Performance improvement plan | Written expectations are not met | Under 100 employees: Founder, with outside HR advice100 to 1,000: HR and the managerEnterprise: HR business partner, manager, and employee relations | What gets written down: A formal plan with goals, support, timeline, and consequencesNext check-in: Scheduled plan reviews |
When a case reaches rung four, follow your company's performance improvement plan process. The ladder reflects CultureMonkey people science guidance on fair, documented escalation.


"Switching to CultureMonkey and connecting to our real HR data has just been a game changer for us. Now I can see engagement information down to the manager level, which is just a completely different world."
HR teams improve negative feedback by training managers on one shared model such as SBI, building a feedback item into every one-on-one, giving managers a short escalation guide, and measuring whether employees feel coached. Pulse surveys and manager feedback surveys show where feedback is missing or landing badly, team by team, before it shows up as attrition.
To compare platforms that collect this data, see this roundup of employee feedback tools.
of managers said they are uncomfortable giving direct feedback about performance if they think the employee might respond negatively.
Source: Interact and The Harris Poll, reported by Lou Solomon in Harvard Business Review
Manager Support driver score on a 0 to 10 scale, by company size, Q3 2026 edition.
| Company size | Manager Support (0 to 10) |
|---|---|
| SMB (100 to 500) | 8.25 |
| Mid-market (500 to 2,000) | 8.30 |
| Enterprise (2,000+ employees) | 8.43 |
In CultureMonkey's own benchmark data, enterprise companies score highest on Manager Support, and companies with 100 to 500 employees score lowest of the sizes reported.
Under 100 employees: not reported for Manager Support in the Q3 2026 edition.
Source: CultureMonkey People Science, Employee Engagement Benchmarks by Company Size 2026, Q3 2026 edition, about 11 million employee survey responses.
Negative feedback examples are short, specific scripts that name one behavior, explain its impact, and agree on one next step. They work because they follow the SBI shape: the employee hears what happened and why it mattered, without labels, and leaves with a clear action and a date. Specific wording turns a hard conversation into a fixable problem.
This guide covered 95 negative feedback examples by situation, role, and industry. It also covered the SBI steps, positive framing, the feedback sandwich, delivery channels for remote, frontline, and written feedback, common mistakes, the escalation ladder to a performance improvement plan, and how HR teams can help managers.
CultureMonkey helps HR teams see where feedback is missing. Its employee feedback software runs pulse surveys and lifecycle surveys with anonymity thresholds, applies AI comment analysis to sort open comments by sentiment and topic, gives managers dashboards with engagement and eNPS over time, and tracks action plans with owners, all in one employee experience platform.
The four types most HR teams use are corrective feedback, which fixes a specific gap; developmental feedback, which builds a skill over time; evaluative feedback, which rates work against a standard; and directive feedback, which says exactly what to change next. Most workplace negative feedback is corrective.
Negativity bias is the tendency to give negative events more weight than positive ones. In feedback, one critical comment can outweigh several compliments. Managers offset it by keeping negative feedback specific and private, and by giving genuine praise in separate, equally specific moments.
No single fixed ratio fits every team. Popular ratios are not a reliable rule for workplace feedback. A better habit is to give specific praise often and separately, so negative feedback never arrives as the only signal an employee hears from their manager.
Use email for the written recap, not the first delivery. Give negative feedback live, by video or in person, then send a short note that restates the behavior, the impact, and the agreed next step with a date. Email first removes tone and the chance to hear the employee's side.
Pause and ask for the employee's view before repeating the point. Restate the specific behavior, not a judgment, and acknowledge any context they share. If emotions run high, agree to continue within 48 hours, and keep the expectation and the follow-up date unchanged.
Write a short, dated note after each conversation: the situation, the behavior, the impact, what the employee said, and the agreed next step with a date. Store it where HR policy requires, share the recap with the employee, and keep opinions and labels out of the record.
Address a shared behavior only when most of the team is involved. Name the pattern, show its impact, and ask the group for the fix. Handle individual issues one to one. Share engagement survey results the same way, and run a short pulse survey later to see if the change held.
Feedback from a manager to a direct report should be named, so the employee can ask questions and act. Peer and upward feedback can stay anonymous through an anonymous employee feedback tool. Well-written employee survey questions keep anonymous input specific and useful.
No. Negative feedback should arrive within days of the event, not months later. A performance review or an annual employee engagement survey should summarize conversations the employee has already had. Nothing in a formal review should be a surprise.
Ask employees directly. Add two or three items about coaching and fair feedback, then compare results by manager. Most employee engagement survey tools and pulse survey tools break results down by team, which shows where feedback is missing or landing badly.
Base every point on observed behavior and results, hold everyone in the role to the same standard, and avoid personality words. Review whose work gets criticized most often. Teams running diversity, equity, and inclusion programs often audit feedback language for patterns.
Look for manager-level reporting with anonymity thresholds, open-comment analysis, and action plans with owners. Check the vendor's survey methodology. Lists of top employee engagement survey vendors and a comparison of employee engagement survey software help narrow the shortlist.
Listen fully, ask for one specific example, thank the person, and agree on one next step. Separate the message from the tone before deciding what to change. For scripts and reply samples, see how to respond to negative feedback.