By Andreas Pettersson, Founder, Leaders ADAPT
The 1:1 ran forty minutes. You asked good questions, they did most of the talking, and they left the room feeling heard. Ten days later the same draft comes back with the same hole in it.
Nothing changed because nothing was asked to change. That's what most constructive feedback examples online miss.
Constructive feedback is a correction of one observed behavior that states what should happen next time. In SBED, the model inside the 1:1 Protocol, that last part is the D, Demands, and it has to land within 24 hours. Leave it out and you vented. Soften it into a maybe and they never heard feedback at all.
Below are 24 scripts for 12 situations, each beside the weak version most managers actually say.
Quick answer: Constructive feedback examples name one behavior, its effect, and the change expected next time. Example: "In Tuesday's forecast review, the numbers arrived without the assumptions behind them, so the team couldn't check them and we lost twenty minutes. Next forecast, put the three biggest assumptions on page one." Weak feedback describes the person or hints. Strong feedback ends with a specific request.
What is an example of constructive feedback?
The forecast line above is one. Here's why it works, letter by letter, in the SBED order I teach:
- Situation. Tuesday's forecast review. One meeting, not "lately" or "you always."
- Behavior. The numbers arrived without assumptions. A fact a camera could record, not "you were sloppy."
- Experience. Nobody could check them, and twenty minutes went to questions. The effect on the team or the work.
- Demands. The three biggest assumptions on page one, next forecast. Specific, forward, checkable.
That's how to give constructive feedback in four parts. For the step by step comparison, read the SBI feedback model and how SBED adds the demand. This page is the phrasebook. The complete guide to giving feedback to employees is the system around it.
One more rule shapes every example below. The first miss and the third miss are different conversations. One miss is an occasion: say it in thirty seconds and move on. Three is a pattern, and a pattern gets the full four letters, in private, with a commitment asked for.
What is the difference between constructive and negative feedback?
Negative feedback is a statement that something went wrong, with no instruction about what should happen instead. Constructive feedback carries the same facts and adds the forward demand. Destructive feedback aims at the person instead of the behavior.
| Type | What it targets | Typical line | What the listener does next |
|---|---|---|---|
| Constructive | One behavior and its effect | "The summary skipped the budget risk. Next time, lead with it." | Knows the change and can make it |
| Negative | The outcome only | "That summary wasn't good." | Guesses what "good" means |
| Destructive | The person's character or intent | "You clearly don't care about detail." | Defends identity, changes nothing |
| Softened | Nothing specific | "Maybe think about the summary a bit?" | Hears optional, ignores it |
Most negative feedback examples online are constructive feedback with the last sentence cut off. So the answer to how to give negative feedback is short: add the demand back, and the same words start working.
24 constructive feedback examples, sorted by situation
Each row gives the weak version, a first time line of micro-feedback length, and a pattern line for the third occurrence. Swap in your own details.
Delivery: deadlines, handoffs and promises
| Situation | Weak version | Strong, first time | Strong, when it's a pattern |
|---|---|---|---|
| Missed deadline | "No worries, just try to hit it next time." | "The vendor summary was due Monday and came Wednesday. Next time a date slips, tell me the day you know." | "Three dates this quarter moved after they passed, and each cost the team downstream two days. From now on, flag a slipping date 48 hours before it's due. Can you commit to that?" |
| Work back 85 percent done | "Great, I'll just tidy it up." | "The draft covers everything except pricing, the part buyers ask about first. Check it against the brief before sending." | "Three of the last four drafts needed my final pass. Next draft, you own the last 15 percent: send it only when you'd sign it yourself." |
| Late handoffs | "Could you maybe send things over earlier?" | "The deck reached design at 4 p.m. for a 9 a.m. meeting. Next time, send it by noon the day before, rough is fine." | "Handoffs to design landed after 3 p.m. on four deadline days this month, and they worked nights to cover it. Starting this week, next morning work reaches them by noon." |
| Over promising | "You're taking on a lot, be careful." | "You promised the sales lead Friday; engineering says three weeks. Check dates with the people doing the work first." | "That's the third promise to another team we had to walk back. Going forward, no date leaves this team until the work's owner confirms it." |
Quality and thinking
| Situation | Weak version | Strong, first time | Strong, when it's a pattern |
|---|---|---|---|
| Report missing the point | "Interesting report, lots of data." | "This explains what happened to churn, not why. Next version, open with your top reason and its evidence." | "The last two reports left the conclusion to me, so I did the analysis twice. From the next one, paragraph one is your recommendation. Data goes underneath." |
| Quality slipping | "Things seem a bit off lately, all good?" | "Two invoices yesterday used the old rates. Check today's batch against the new sheet before it goes." | "Invoice errors went from zero to five in three weeks and customers are calling finance. Every batch gets checked against the rate sheet, starting today. What do you need from me to make that stick?" |
| Came unprepared | "Let's just go through it now." | "We spent fifteen minutes catching you up on the pre-read. Read it the night before Thursday's meeting." | "Third decision meeting without the pre-read, and each one pushed the decision a week. Next time it isn't read, we decide without your input." |
| Problems without proposals | "Thanks for flagging." | "You raised the hiring backlog. What would you do about it? Bring one option with the next problem." | "Six problems this month, zero proposals, so every decision lands on me. From now on, each problem comes with one option you'd recommend." |
Meetings, 1:1s and people
| Situation | Weak version | Strong, first time | Strong, when it's a pattern |
|---|---|---|---|
| 1:1 became a status update | "Great update, thanks." | "That was this week's task list, which I can read on the board. Next 1:1, bring the one thing that's harder than it should be." | "Our last four 1:1s were status reports, so I find out about problems late. Starting next week, status goes in writing the day before. The 1:1 is for what's stuck." |
| Interrupting in meetings | "Let's give others a chance, okay?" | "You cut in twice during the analyst's forecast. Next time, write your point down and bring it in once they're done." | "In three team meetings you've talked over the same two people, and both have stopped offering ideas. From Monday, nobody gets cut off by you. Hold it, then add it." |
| Decision routed back to you | "Sure, I'll decide." | "You asked me which supplier to pick. What would you pick if I weren't here? Decide it and tell me after." | "Four decisions inside your authority came to me this month and each waited two days. Anything under your spending limit, you decide. Bring me only what's above it." |
| Peer conflict | "You two need to sort it out." | "In stand-up you told the ops lead her plan won't work without saying why. Next time, give the reason and a better option." | "Three disagreements with the ops lead reached me this month and work stalled each time. Next one, meet first and bring me one recommendation or two options with the tradeoff." |
Read the weak column again. Every line is polite, and every line leaves the person guessing. The decision row is the one I see most in founder-led teams, and it has its own fix in reverse delegation.
Micro-feedback: the thirty second version
Micro-feedback is a single observation and a single instruction, said within minutes of the behavior, with no meeting attached. The first time column above is micro-feedback. The three lines I wrote for The 5-Minute Leader show the length:
| Moment | The whole feedback |
|---|---|
| In the meeting | "You're speeding up. Slow down so they can follow." |
| After a call | "Strong close. Next time, get a commitment before hanging up." |
| Over chat | "Report was solid. Add an executive summary next time." |
The second and third open with praise, then a demand, and both halves are true. That isn't a sandwich, because nothing is hidden and there's no second slice of bread.
Run micro-feedback weekly and the pattern column rarely gets used.
Boomerang check: does your work stay delegated, or does it come back?
Three questions, scored to the protocol that fixes the leak. The 5-Minute Leader is the four protocols, Delegation, 1:1, Accountability and Rhythm, written down so a manager can run them in about five minutes a day, so tasks stop boomeranging back half done.
Get the 5-Minute Leader or see what is inside the 5-Minute Leader.
How do you give constructive feedback without demotivating someone?
You make the warmth about the person and keep the words about the work. The structure is Warm but Firm, from the Accountability Protocol:
Warm opening: "I'm invested in your success, and that's why I'm being direct about this." Firm middle: the SBED, with no maybe, no perhaps, no softening. Warm close: "What do you need from me to make this change?"
Here's the part I learned the hard way. My Nordic default is directness without much visible emotion. In the American companies I ran, including the years as one of Canon's youngest CEOs, that read as too much of a poker face.
When the only time someone hears from you is when something is wrong, every correction sounds like a verdict. I had to learn to say the wins out loud, so the direct sentence had something to sit on.
Our own numbers point the same way. In the Leadership Readiness Index Q3 2026 skills chapter (n = 66 of 480 completions, 0 to 20 scale), leaders self assessed Relational Intelligence at 11.1 and Clarity and Directness at 7.6 (leadership skills statistics).
Self assessed, not measured. But it says most leaders believe the relationship is stronger than their ability to say the direct thing. So the relationship can carry more directness than you think.
What should you avoid saying?
Five habits turn good constructive criticism examples into noise:
- "You always" or "you never." One absolute starts a debate about the exceptions.
- Reading intent. "You were rude" or "you don't care" is a verdict. Describe what they said or did.
- Maybe, perhaps, just, a bit. Each one tells the listener the demand is optional.
- The sandwich. Fake praise before and after hides the demand in the middle. The feedback sandwich and what to use instead has its own page.
- The prequel. Discrediting yourself before you start.
The fifth is the one I correct most, usually in a coaching session where a leader rehearses the conversation and opens with "I'm not saying this from a place of perfect, I have gaps too." My answer is always the same:
"Never ever do stuff like that. You're discrediting yourself. You're discrediting the value of the word. If you don't make it about you, it's about them."
And if they turn it back on you ("well, you haven't followed up either"), decline the trade calmly. This conversation is about them. Yours can happen another day.
Constructive criticism examples: six that keep the change attached
Searches for constructive criticism examples usually want the same thing as the 24 scripts above, with one difference in emphasis. Criticism names what was wrong. Constructive criticism names what was wrong and what replaces it, and the second half is the part people leave out.
| Criticism alone | Constructive criticism |
|---|---|
| "The report was sloppy" | "The report had three figures that didn't match the source sheet. Before the next one goes out, reconcile the table against the sheet and tell me you've done it" |
| "You dominate meetings" | "In Tuesday's planning call you spoke for about half the time and two people didn't get in. Next meeting, make your point once and then ask who disagrees" |
| "Your code reviews are harsh" | "Your review on Friday had eleven comments and none said what was done well. Open the next one with the one thing that's right, then the changes" |
| "You're not proactive enough" | "The vendor contract expired two weeks before anyone flagged it. From now on, anything with a date goes on the team calendar the day you learn about it" |
| "The deck was too long" | "Forty slides for a 20 minute slot. Next board deck, nine slides, and the detail goes in the appendix" |
| "You keep missing deadlines" | "Three of the last four deliverables arrived after the date with no message before. If a date will slip, I hear it before the date, not after" |
Every line in the right column has a situation, a behavior and a demand. The word criticism is optional. The demand is not.
When the person pushes back
Most pushback falls into three types. Each has a response that steers back to the demand.
| Type | What they say | Response |
|---|---|---|
| The Defender | "That's not what happened." | "I might have seen it differently. Walk me through your perspective." Then: "Regardless, here's what I need going forward." |
| The Deflector | "Everyone does this." | "We're talking about you right now. Can you commit to what I'm asking?" |
| The Ghost | "Okay. Sure. Got it." | "Tell me what you're taking away from this conversation." |
The rule over all three: "Don't argue about perceptions. Redirect to commitment." You won't win a debate about what happened on Tuesday. You don't need to. You need a yes to next Tuesday.
If the same person pushes back on the same pattern twice, it isn't a feedback problem anymore. Check whether the standard was ever set with clear expectations, then move to holding the employee accountable. For scripts on the harder talks, see these difficult conversation examples.
How often should managers give constructive feedback?
As often as the behavior happens, and inside a day. That's the 24/48 Rule: see it, say it within 24 hours with "Quick feedback from yesterday. Got 2 minutes?" After 48 hours, don't deliver it late. Wait for the next occurrence, because it will come, and address that one fresh.
And don't hold it for a 1:1 that's five days away.
The research backs frequency over formality:
- Employees who get daily feedback from their manager are 3.6 times more likely to strongly agree they're motivated to do outstanding work than those who get it annually (Gallup, 2022, Gallup Panel of 13,490 full time US employees, fielded March 2021).
- 80 percent of employees who received meaningful feedback in the past week are fully engaged (Gallup, same study).
- Just 20 percent of individuals constantly seek and offer feedback (Culture Partners, Workplace Accountability Study, 40,000 respondents, 2011 to 2014, vendor funded).
The 1:1 meeting is where you check the feedback stuck, not where you save it up.
Constructive feedback examples FAQ
What are good constructive feedback examples for a coworker?
Peer constructive feedback examples follow the same structure without the authority. Name the moment, the behavior, the effect on shared work, then make a request rather than a demand: "In yesterday's planning call, the timeline changed after I'd committed it to the client team. Next time a date moves, can you message me before the call ends?" A peer can ask for a change but cannot require it, so the last line is phrased as a request with a reason.
How do you give negative feedback to an employee?
To give negative feedback to an employee, turn it into constructive feedback by adding what should happen next. State one specific situation, the observed behavior, and its effect on the team or the work, then say what you need going forward. Deliver it privately within 24 hours. Avoid words that describe the person's character or intent, and end by asking for a commitment rather than agreement with your view of events.
Is constructive criticism the same as constructive feedback?
In workplace use the terms are close to interchangeable: both mean a correction aimed at improving future behavior. Constructive feedback is the broader term and also covers reinforcing feedback on work done well. Constructive criticism refers only to the corrective side. Some managers avoid the word criticism because listeners hear it as a judgment of the person, but the content and structure are the same.
What are some constructive criticism examples for work?
Pair what went wrong with what replaces it. "The report had three figures that didn't match the source sheet. Reconcile the table before the next one goes out." "Forty slides for a 20 minute slot. Next time, nine, with the detail in the appendix." "Three of the last four deliverables were late with no message. If a date slips, I hear it before the date." Each names a moment, a behavior and a change.
Should constructive feedback be given in writing?
Small corrections work in writing: a two sentence chat message naming the behavior and the change is fast and clear. Pattern level feedback belongs in a spoken conversation, ideally private and in person or on camera, because tone carries the warmth that plain text drops. A short written follow up afterward recording what was agreed prevents later disagreement about what was said.
How long should a constructive feedback conversation take?
A first time correction takes about thirty seconds: one observation and one instruction. A full conversation about a repeated pattern usually takes five to ten minutes: the four parts of the feedback, the person's response, and an explicit commitment. Conversations that run much longer tend to drift into debating what happened, which moves attention away from what changes next.
What is the best structure for constructive feedback?
A widely used structure is SBED: Situation, Behavior, Experience, Demands. The situation fixes one time and place, the behavior describes observable actions, the experience states the effect, and the demand specifies the change expected. SBI (Situation, Behavior, Impact) covers the first three parts. The final element matters most because feedback without a stated change leaves the listener without a clear next step.
The weak column costs more every week you keep using it
The weak version protects your comfort today. The strong version protects the person's next month. Keep the weak one and the pattern repeats, you end up fixing the work yourself, and the talk you avoided gets harder each time.
So don't start with all 24 constructive feedback examples. Pick the one situation that happened on your team this week. Write the first time line. Say it before lunch tomorrow.
Feedback only sticks when the rest of the system is running
At Arcules I went from a handful of people to more than 150, and feedback was never the thing that failed alone. It failed when the work was handed off unclear, or when there was no regular meeting to check it stuck. That's why The 5-Minute Leader runs four protocols in order:
- The Delegation Protocol keeps the work handed off, so the standard leaves the room with the task.
- The 1:1 Protocol surfaces problems early. SBED, micro-feedback and the 24/48 Rule all live here.
- The Accountability Protocol makes the standard visible, so nobody has to chase and Warm but Firm has something to point at.
- The Rhythm Protocol puts all of it on a weekly cadence the team keeps even when you're traveling.
Part 2 adds a two minute record you fill in after every 1:1. One of its eight fields tells you, four weeks later, whether your feedback actually changed anything.
Tomorrow morning, before your first meeting, open the constructive feedback examples table above and find the row you've been avoiding. Write the pattern line with your real details. Say it today, then add that person's name to your next 1:1 agenda to check it held. For the whole system, start with The 5-Minute Leader.
