40+ Constructive Feedback Examples for Effective Teams

Paul OsasNovember 4, 20265 min read
40+ Constructive Feedback Examples for Effective Teams

Most managers know they should give feedback. Far fewer know how to say it without sounding either robotic or brutal.

The gap between "good feedback" and "feedback that actually changes behavior" usually comes down to specific wording, and that's exactly what most advice skips.

We're so afraid of sounding like a jerk that we sand our words down until there's nothing left to act on. That isn't kindness. It's leaving someone to fail slowly, in private, while you watch.

The good news is that kind and direct aren't opposites. Good constructive feedback is both, and it's a skill, not a personality trait. You can borrow the words until they become yours.

That's what this guide is for. Below you'll find 40+ constructive feedback examples written for real work situations.

Key takeaways

- Constructive feedback is specific, about behaviour (not personality), and points to a next step.

- Use a simple formula: Situation, Behaviour, Impact, then Ask.

- Say it soon, say it privately, and say it more often than feels natural. Praise counts too.

- If people can't safely give you feedback, you won't hear most of it. Pair direct conversations with an anonymous channel.

What is constructive feedback?

Constructive feedback is specific, honest input about someone's work or behaviour that helps them improve. It describes what happened, explains why it matters, and points to a clear next step.

The word doing the heavy lifting is constructive. It builds something. Criticism describes a problem. Constructive feedback describes a problem and gives the person a way forward.

It also isn't only about what went wrong. Telling someone exactly what they did well, so they do it again, is constructive feedback too. Arguably it's the most underused kind.

Constructive vs destructive feedback

Constructive feedback

Destructive feedback

Focus

A specific behaviour or piece of work

The person's character ("you're careless")

Detail

Concrete moment and example

Vague or sweeping ("you always…")

Purpose

Help them improve

Vent frustration or assign blame

Timing

Soon after, in private

Weeks later, or in front of others

Ending

A next step or question

A verdict

How it feels

Uncomfortable but useful

Personal and deflating

Why it matters more than you think

Gallup found that 80% of employees who received meaningful feedback in the past week are fully engaged, whatever their office schedule. Yet in the same research, only 16% said their last conversation with their manager was extremely meaningful.

One detail from that study changed how I think about this. The topic employees found least meaningful was a conversation focused only on their weaknesses. The most meaningful conversations covered recognition, collaboration, goals, and strengths.

So the lesson isn't "stop giving critical feedback." It's that criticism lands when it's part of a bigger conversation about where someone is going, not the whole conversation.

A simple formula: Situation, Behaviour, Impact, Ask

Every example in this post follows the same four beats. It builds on the Situation-Behavior-Impact model from the Center for Creative Leadership, with one addition that turns a statement into a conversation: the Ask.

1. Situation: when and where. "In Tuesday's sprint review…"

2. Behaviour: what you actually saw or heard. Not what you think it means. "…you presented the dashboard before QA had signed off…"

3. Impact: what it caused, for you, the team, or customers. "…and two customers on the beta saw broken numbers."

4. Ask: a question or next step. "What got in the way of the QA check? How can we make sure it happens next time?"

The Ask matters most. It invites their side of the story (maybe QA was blocked for reasons you didn't know) and makes the next step something you agree on together, instead of a ruling handed down.

Before and after

What we usually say

What to say instead

Too vague

"Your specs could be a bit clearer."

"On the export feature spec, the acceptance criteria were missing, so engineering spent two days guessing at edge cases. Could we add a criteria checklist to the template and review the next one together?"

Too harsh

"You never think about the customer."

"In the pricing page review, the copy focused on our features, but the three customer calls last week were all about migration risk. What would it look like if we led with that?"

Too sugar-coated

"Love the energy! Maybe slightly fewer slides?"

"Your board-update deck had strong data, but at 40 slides the key decision got lost. Can you cut it to ten and put the ask on slide two?"

A quick test before you say anything: could the person act on it tomorrow morning? If not, it's not feedback yet. It's a mood.

Constructive feedback examples for product managers

Product work runs on clarity. When feedback is fuzzy here, it shows up as slipped dates and features nobody uses.

1. Missed sprint commitment

"We committed to the onboarding checklist this sprint and it rolled over for the second time. That pushed the activation experiment back a month. What's getting in the way? I'd rather we commit to less and land it."

2. A spec that was too thin

"The PRD for bulk invite didn't cover permissions or error states, and engineering spent the first two days asking questions in Slack. Can we walk through the next spec together before it goes out? I'll share the template I use."

3. Saying yes to every request (scope creep)

"In the last three planning meetings you've added a request from sales mid-sprint. Each one is reasonable on its own, but together they've cut our roadmap work by about a third. How do you want to handle the next one? I'm happy to be the one who says no."

4. Prioritising by loudest voice

"The dark mode ticket jumped the queue after one customer escalated, but our usage data says CSV import affects far more accounts. Walk me through how you decided? I want to understand, and make sure we're using the same yardstick."

5. Shipping without a success metric

"We launched the new dashboard last week, but I don't know what 'working' looks like. Before the next launch, can you write down one metric and the number that would make us call it a win?"

6. Not saying no to stakeholders

"When the CEO asked for the Q1 date, you agreed on the spot, even though the team had flagged risk the day before. I get the pressure. Next time, try: 'Let me check with the team and come back by Friday.' It protects them and you."

7. Skipping customer discovery

"We built the reporting module from internal assumptions, and adoption is at 4% after a month. For the next feature, can we talk to five customers before we write the spec? I'll help you line up the calls."

8. Unclear roadmap communication

"Two people on the CS team told me they found out about the pricing change from a customer. Can we add a short 'what's shipping' note to the Monday update, so the people talking to customers hear it from us first?"Positive Constructive Feedback Examples

Constructive feedback examples for engineers, designers, and cross-functional teams

These are the conversations where people most often stay silent, because the work is technical, the person is senior, or it's "not your team." Say it anyway. Kindly.

9. Code reviews that feel harsh

"Your review comments on Ana's PR were technically right, but phrases like 'this is wrong' landed hard. She's new and stopped asking questions in the channel. Could you try framing the next few as questions, like 'what happens if this is null?'"

10. Over-engineering

"The plugin system for notifications is impressive, but we have two notification types and no plans for more this year. It added a week. Next time, can we talk through the simplest version first and build out only when we need to?"

11. Missing estimates without warning

"The API work was due Wednesday and landed Friday, with no update in between. Support had nothing to tell the customers who were waiting. Slipping is normal. Can you flag it the moment you think a date is at risk, even if you're not sure?"

12. Designer skipping research

"The new settings layout looks clean, but we didn't test it, and three of the first ten users couldn't find billing. For the next redesign, could we run five quick usability sessions before we hand off?"

13. Design hand-off gaps

"The Figma file for checkout had the happy path, but no empty, loading, or error states. Engineering ended up inventing them. Could you add those to your hand-off checklist?"

14. Working in a silo

"You rebuilt the search index over the weekend, which was a huge effort. But the data team didn't know, and their reports broke Monday. Before changes like that, can you post a heads-up in #eng-changes?"

15. Dismissing other teams' input

"When marketing raised concerns about the launch name, you said 'that's not really an engineering problem' and moved on. They felt brushed off. Could you follow up with them? Their worry about SEO was actually fair."

16. Quality slipping under pressure

"We've shipped three hotfixes in two weeks, all from the same module. I know the deadlines have been brutal, and that's partly on me. What would you need to add tests there before the next release?"

Notice the last one. Sometimes the most constructive thing you can say is "this is partly my fault." It lowers defences faster than anything else.

Constructive feedback examples about communication, meetings, and ownership

These apply to anyone on the team, from a new hire to a VP. They're also the ones most often softened into nothing, because they feel "personal." They aren't. They're about habits.

17. Talking over others in meetings

"In this morning's planning, you finished Sam's sentence twice and moved us on before Priya made her point. You have great instincts, but the quieter people stopped contributing. Could you try waiting a beat before jumping in?"

18. Not speaking up in meetings

"You mentioned the migration risk to me after the meeting, and you were right. That point would have changed the decision if the room had heard it. What would make it easier to raise in the moment? I can also call on you directly if that helps."

19. Long, unfocused updates

"Your standup updates have been running five or six minutes, and the team is losing the thread. Could you try the format 'done, doing, blocked' and keep the detail for the thread afterwards?"

20. Missing follow-through on action items

"Three action items from last week's retro were assigned to you and none have moved. When things stall, the team stops trusting retros. Which of these is still realistic? Let's drop or reassign the rest today."

21. Negativity that drains the room

"When we discussed the new pricing, your first reaction was 'this will never work,' and the conversation stalled. Your concerns are often valid. Could you lead with the specific risk and one idea to reduce it? People will hear you better."

22. Defensiveness when receiving feedback

"When Leo raised the bug count in the review, you explained why each one happened before he finished. I could see him back off. Try 'thanks, tell me more' first. You can always explain after."

23. Blaming others when things go wrong

"In the incident retro, most of your points were about what the vendor did. Some of that's fair, but the team needs to hear what we can change. What's one thing on our side you'd do differently?"Constructive Interview Feedback Examples

Constructive feedback examples for managers and founders (upward feedback)

Giving feedback up the chain is where the formula matters most, because the risk is real. If you're a founder reading this, this section is for you too: these are the sentences your team is probably holding back.

24. The founder who rewrites everything

"When you rewrote the launch email the night before it went out, the marketing team felt their two weeks of work didn't count. Your edits were good. Could we agree you review drafts by Thursday, so changes happen before the final version?"

25. Changing priorities too often

"We've changed the top priority three times this month. Each change made sense, but the team is now hesitant to start anything big. Could we lock priorities for two weeks at a time, unless something is truly urgent?"

26. Being hard to reach

"I've had a decision on the enterprise contract waiting since Monday, and I couldn't find a time on your calendar. Could we set up a standing 15 minutes each week for decisions like this?"

27. Micromanaging

"You've asked for updates on the integration project three times a day this week. I understand it's high stakes. It's slowing me down, though. Would a short written update every evening give you what you need?"

28. Feedback only in public

"When you pointed out the error in my forecast during the all-hands, it was fair, but it was hard to hear in front of everyone. Next time, could you flag that kind of thing with me first?"

29. Decisions without context

"The team heard about the hiring freeze in a one-line Slack message, and rumours filled the gap. A few more sentences on the why would go a long way. Could you share the reasoning at Friday's all-hands?"

If the stakes feel too high to say these face to face, that's a signal about your culture, not about you. Our guides to upward feedback examples and giving anonymous feedback to your boss cover how to do it safely. And if you're the founder, ask yourself honestly why nobody has said these to you yet. Our post on why your open door policy isn't working might hold the answer.

Positive constructive feedback examples

"Great job!" is nice. It's also useless. The person has no idea what was great, so they can't do it again on purpose.

Positive feedback follows the same formula. Be as specific about what went right as you would be about what went wrong. And remember the Gallup finding from earlier: recognition and strengths are what make feedback conversations feel meaningful in the first place.

30. A clear, well-structured spec

"Your spec for SSO was the clearest one we've had. The edge-case table meant engineering asked zero clarifying questions. Would you be up for turning it into our team template?"

31. Calm incident handling

"During Tuesday's outage, your updates every 20 minutes in #status kept support and customers informed without anyone having to ask. That's exactly the standard I want for every incident."

32. Pushing back well

"When you challenged the Q2 date in planning, you brought data and a cheaper alternative, not just a no. It changed the decision. Please keep doing that, even with me."

33. Helping a teammate grow

"Over the past month you've paired with Maya on every on-call shift, and she handled last night's alert on her own. That's real leadership, and it doesn't show up in any ticket count. Thank you."

34. Customer empathy

"The way you summarised the churn interviews, using customers' own words, made the problem impossible to ignore. Two people from sales told me it changed how they pitch."

35. Admitting a mistake early

"When you flagged that the migration script had a bug before anyone else noticed, you saved us a messy weekend. Owning it that fast makes it safe for everyone else to do the same."

36. Saying no to protect focus

"You turned down the partner integration request with a clear reason and a later date, and the partner was fine with it. That protected the whole sprint. Good call."

Examples 32, 35, and 36 matter more than they look. When you praise someone for pushing back or admitting a mistake, you tell the whole team those behaviours are safe. That's how psychological safety actually gets built: one specific moment at a time.

Constructive feedback examples for Slack, async, and anonymous channels

On remote and hybrid SaaS teams, a lot of feedback happens in text. Text strips out tone, so a sentence that sounds fine out loud can read as cold. Two rules help: keep criticism out of public channels, and if it's more than two sentences, offer a call.

37. Slack DM about a missed handoff

"Hey, quick one. The design files for the billing page weren't in the ticket this morning, so Dev was blocked for a few hours. Not a big deal, just flagging so it doesn't repeat. Can you drop them in by 10 a.m. on hand-off days? Happy to hop on a call if anything's in the way."

38. Async comment on a doc

"The problem statement here is strong. In section 3, I think we're jumping to a solution before showing the data. Could you add the three support-ticket trends you mentioned in standup? That would make the case for me."

39. Moving a public pile-on to private

(In the thread) "Let's take this offline, I'll set up a quick call." (In the DM) "I could see that thread getting heated. Your point about the API limits was valid. Can we talk it through with Jo directly instead of in the channel?"

Anonymous feedback is still feedback, and the formula still works. If anything, it matters more, because the reader can't ask you what you meant. Here's what good anonymous constructive feedback looks like, from the employee's side:

40. Anonymous feedback about a manager

"In our team's last three 1:1 cycles, several of us have had our meetings cancelled with less than a day's notice. It makes it hard to raise blockers, and a few of us have stopped bringing them up. Could 1:1s be treated as fixed unless there's an emergency?"

41. Anonymous feedback about company process

"The new expense approval flow needs three sign-offs for anything over $50, so small purchases take a week. Could the threshold go up, or could managers approve alone under a set amount?"

42. Anonymous feedback about culture

"In all-hands Q&A, tough questions seem to get answered with 'we'll come back to that,' and we rarely hear back. It's making people stop asking. Could unanswered questions get a written follow-up the next week?"

Each one names a pattern, explains the impact, and suggests a fix, without naming or blaming a single person. That's what makes it something a leader can act on instead of something to get defensive about. You'll find dozens more in our collection of anonymous feedback examples for managers, plus tips for remote teams.

How to receive constructive feedback (the half nobody practises)

Here's an uncomfortable truth for founders and managers: your team learns how to give feedback by watching how you take it. React badly once, and you've trained everyone to stop.

When someone gives you constructive feedback, try this:

1. Breathe and say thank you. "Thanks for telling me. That can't have been easy." Mean it. They just took a risk.

2. Ask before you explain. "Can you give me an example?" or "What would you have liked to see instead?" Your explanation can wait.

3. Separate the message from the delivery. Even clumsy feedback usually contains something true. Look for that part.

4. Say what you'll do, and when. "I'll try that in next week's planning and check in with you after."

5. Close the loop. Go back and tell them what changed. This is the step that makes them willing to do it again. More on that in how to close the feedback loop.

And a few phrases worth retiring for good:

"That's not what I meant." (It might not be. It's still how it landed.)

"Well, the reason I did that is…" (Too soon.)

"Who else feels this way?" (This turns feedback into a hunt, and it guarantees silence next time.)

If you want feedback on how you lead, not just on tasks, these manager 360 feedback questions are a good place to start.

6 mistakes that turn constructive feedback destructive

1. The compliment sandwich. Praise, criticism, praise. People learn to brace when you open with a compliment, and the middle gets lost. Give praise and criticism separately, and mean both.

2. Saving it for the performance review. If the first time someone hears about a problem is in a formal review, that's a management failure, not theirs. Feedback goes stale fast, so aim to say it within a few days.

3. Using "always" and "never." "You always miss deadlines" invites an argument about the one time they didn't. Stick to the specific moment.

4. Guessing at motives. "You obviously didn't care about this" is a story you've invented. Describe what they did, then ask why.

5. Piling on. One issue per conversation. Five pieces of feedback at once feels like an ambush, and none of them sticks.

6. Only giving feedback down. If feedback only flows from managers to their reports, it isn't a culture. It's a hierarchy with comments. Make it safe to encourage honest feedback in every direction.

The kindest thing you can say is the true thing, said well

Somewhere in your head right now is a piece of feedback you've been avoiding. Maybe for a week. Maybe for a quarter.

You've been telling yourself you're protecting them. You're mostly protecting yourself from an awkward fifteen minutes. Meanwhile, they keep doing the thing, and they're the last to know it's a problem.

So here's my challenge. Before Friday, take that one piece of feedback and run it through the formula:

- Situation: When did it happen?

- Behaviour: What did you actually see?

- Impact: What did it cost?

- Ask: What question opens the conversation?

Write it down. Read it out loud once. Then go say it, kindly and directly. Most people are grateful. Almost nobody is grateful for the feedback they didn't get.

And make sure feedback can flow back to you, too. The hardest truths on any team are the ones people won't say face to face. Set up an anonymous feedback box with JellyForm in under two minutes.

No IP tracking, no cookies, and two-way replies so you can ask follow-up questions without unmasking anyone. 7-day free trial, no credit card required. Or try the live demo box first.

Get started today

Start collecting honest feedback today.

Set up your anonymous feedback box in under two minutes. 7-day free trial. No credit card required.

No IP trackingNo cookies100% anonymous7-day free trial