Constructive feedback examples work when they are specific, forward-looking and tied to a next step. The best constructive feedback names the situation, describes what the person did, explains the effect, and invites a better approach, so the person leaves with something to try rather than something to feel bad about. This page gives you more than 40 ready-to-use phrases for managers and peers, organized by skill growth, process, communication, time management, quality, collaboration and stretch goals.
Key takeaways
- Constructive feedback is developmental. It points at what to do next, not at what went wrong.
- Structure keeps it specific. SBI (Situation, Behavior, Impact) and COIN (Context, Observation, Impact, Next steps) turn a vague impression into something a person can act on.
- Feedforward beats retrospective critique for skill growth. Suggest what to try next time instead of replaying the miss.
- Pair every growth area with a real strength and a next step. Hollow praise as a cushion is easy to spot.
- Use the right page for the right job. For hard criticism and conduct issues, see negative feedback examples. This page covers the everyday developmental conversation.
What is constructive feedback?
Constructive feedback is specific, behavior-focused input given to help someone improve, with a clear path forward. It describes observable actions and their effect, avoids judging character, and ends with a question or a next step. Constructive criticism examples and constructive feedback examples are the same idea, and the line between "constructive" and "negative" is about purpose: constructive feedback builds a skill, negative feedback corrects a problem that has already caused harm.
A 2014 Harvard Business Review survey found that 72% of employees believe their performance would improve if managers gave more corrective feedback. People want it. They want it to be usable.
Weak versus constructive: 8 quick rewrites
Most feedback fails because it describes a feeling, not an observation. These rewrites show the difference.
| Weak feedback | Constructive version |
|---|---|
| "You need to be more proactive." | "On the Q3 launch, you waited for assignments before starting the vendor checklist. Next time, pick up the open items on Monday and tell me what you took." |
| "Your reports are messy." | "The last two reports mixed quarterly and monthly figures in one chart, which made the trend hard to read. Try one chart per time period and a summary line at the top." |
| "Speak up more." | "In planning, you had a concern about the timeline and raised it afterwards. Would it help if I asked for your view first in the next meeting?" |
| "You're always late with updates." | "The weekly update has landed after the Friday review twice this month. Can we move your deadline to Thursday noon so the group sees it in time?" |
| "Be a better team player." | "When the design handoff stalled, the developers waited three days before anyone asked. A quick flag in the team channel would have unblocked it sooner." |
| "Your presentation was boring." | "The data was strong, but slides 4 to 9 were dense. Cutting each slide to one takeaway would let your analysis land." |
| "You're too negative." | "In the retro, each idea got a reason it wouldn't work. Try pairing each concern with one option so we leave with a path forward." |
| "Good job, keep it up." | "The way you restructured the onboarding checklist cut setup questions in half. Next, try documenting your approach so others can reuse it." |
Three structures for constructive feedback: SBI, COIN and feedforward
A structure keeps you honest about what you actually saw. Pick one and use it consistently.
| Structure | How it works | Best for |
|---|---|---|
| SBI | Situation, Behavior, Impact | A single moment you can describe precisely |
| COIN | Context, Observation, Impact, Next steps | A pattern that needs an agreed action |
| Feedforward | Name a future situation, suggest what to try | Skill growth, coaching and stretch goals |
SBI: Situation, Behavior, Impact
SBI works best right after a specific moment. State when and where it happened, describe only what you saw, then explain the effect. Our SBI feedback model guide has more templates, and you can grab the free one-page SBI template (PDF) before your next conversation.
"In Tuesday's client call (situation), you answered the pricing question before the client finished asking it (behavior). They asked it again at the end, so we spent the last ten minutes on something we'd already covered (impact). What do you think happened?"
COIN: Context, Observation, Impact, Next steps
COIN adds an explicit next step, which makes it a good fit for patterns. It is also gentler than a bare criticism because the conversation ends on action.
"Context: we've been shipping weekly releases since March. Observation: the last three release notes went out after customers had already asked about the changes. Impact: support spent Friday answering questions the notes would have covered. Next steps: could you draft the notes on Thursday so I can review them before the release?"
Feedforward: suggestions for next time
Marshall Goldsmith popularized feedforward: instead of critiquing the past, you offer ideas for the future. It is especially useful for skill growth because nobody can change what already happened.
"Next time you run the kickoff, try opening with the decision you need from the group. People will know what to listen for."
Constructive feedback examples by skill area
Every example below is written to be adapted. Swap in your own situation, name the real effect, and end with an invitation. Keep the tone you would use in person.
Skill growth
| Situation | Constructive feedback |
|---|---|
| Strong analyst, rarely shares methods | "Your forecasts are consistently accurate. To grow into the senior role, start documenting how you build them so others can learn from your approach." |
| Competent but narrow technical range | "You handle the backend tasks confidently. A good next step would be to pair with the frontend lead on one ticket this month." |
| New to client-facing work | "Your preparation for the call was thorough. When you present, try leading with the recommendation and then the reasoning, so clients hear your conclusion first." |
| Waits for approval on routine decisions | "For purchases under the team limit, you can decide and tell me afterwards. I'd rather see you decide than wait." |
Process improvement
| Situation | Constructive feedback |
|---|---|
| Manual weekly reporting | "The weekly report takes you three hours, and the data comes from the same two sources. Could we automate the pull and spend that time on the commentary?" |
| Repeated rework on handoffs | "Two projects needed rework because the brief changed after kickoff. Let's add a sign-off step before work begins." |
| Unclear ownership | "The task sat for a week because both of you thought the other had it. Let's name one owner per task in the tracker." |
| Quality checks happen too late | "The errors were caught in final review, which meant redoing a day of work. A mid-point check would catch them sooner." |
Communication
| Situation | Constructive feedback |
|---|---|
| Long, unfocused updates | "Your updates cover everything, which makes it hard to find the decision. Try starting with what you need from the group, then the detail." |
| Email tone feels abrupt | "The message to the vendor was clear but read as curt. A one-line opener before the request would keep the relationship warm." |
| Slow replies on time-sensitive items | "When you're heads-down, I can't tell if you've seen a deadline message. A quick thumbs-up reaction would tell me it's on your radar." |
| Doesn't ask for help | "You mentioned being stuck on the integration only after the deadline passed. I'd rather hear about it on day two, when we still had options." |
Time management
| Situation | Constructive feedback |
|---|---|
| Underestimates effort | "The last three estimates came in about 40% under. Try adding a buffer and checking the estimate with someone who has done similar work." |
| Too many priorities | "You're carrying five projects and all five are slipping slightly. Which two matter most this month? Let's agree what to pause." |
| Meetings crowd out focus time | "Your calendar shows almost no uninterrupted blocks. Let's pick two mornings a week for deep work and decline the optional meetings." |
| Last-minute submissions | "The client deck arrived the morning of the meeting, so I had no time to review. Can we set an internal deadline 24 hours earlier?" |
Quality and attention to detail
| Situation | Constructive feedback |
|---|---|
| Typos in external documents | "The proposal had three typos in the pricing table. A final read-aloud pass before sending catches most of these." |
| Incomplete testing | "The release had a bug on the checkout page that a basic test would have caught. Let's add a smoke-test checklist to your pre-release routine." |
| Misses part of the brief | "The deliverable covers points one and three. Point two, the competitive analysis, is missing. Can we agree a timeline to add it?" |
| Strong work, inconsistent finish | "Your analysis is excellent. The formatting varies between sections, which distracts from it. A shared template would fix that." |
Collaboration
| Situation | Constructive feedback |
|---|---|
| Dominates meetings | "You bring great energy to discussions. Decisions are being made before others weigh in. Try waiting for two other voices before sharing your view." |
| Works in isolation | "Your work is strong, but the team only sees it at the end. A brief mid-point demo would let others build on it." |
| Doesn't credit others | "In the review, the project summary didn't mention Ayesha's work on the data cleanup. Naming contributions publicly would strengthen trust on the team." |
| Slow to give feedback to peers | "Two colleagues are waiting on your review comments. Even a quick 'looks good, details tomorrow' keeps them moving." |
Stretch goals
| Situation | Constructive feedback |
|---|---|
| Ready for more scope | "You've handled every project I've given you. Let's pick one stretch goal for next quarter: leading the vendor selection, start to finish." |
| Plateaued in current role | "Your core work is solid. To keep growing, I'd like you to mentor the new analyst and present at the monthly review." |
| Hesitant about visibility | "Your analysis was the strongest in the room. I'd like you to present it to the leadership team, and I'll rehearse it with you first." |
| Wants a promotion path | "To be ready for team lead, we'll need to see you coordinate across two teams. Let's find a project that gives you that practice." |
Coaching and feedforward phrases
Coaching phrases turn feedback into a conversation. They are questions or suggestions, not verdicts.
- "What would you do differently if you ran this again?"
- "What got in the way, and what would help remove it?"
- "What's one thing you could try in the next meeting?"
- "If you could change one step in this process, which would it be?"
- "Next time, try opening with the recommendation."
- "I'd like to see more of [specific action]. How can I help you make that routine?"
- "What support do you need from me to get there?"
- "What would you like feedback on from me this month?"
Constructive feedback for coworkers
Peer feedback works when it is invited, specific and focused on shared goals. Ask permission first ("Can I share something I noticed?"), keep it private and avoid piling on.
| Situation | Constructive feedback |
|---|---|
| Handoff notes missing details | "The handoff notes didn't include the client deadline, which cost me a day. Could we add it to the template?" |
| Interrupts in discussion | "I noticed I lost my train of thought in the review when it moved on quickly. Could we pause for questions at the end of each section?" |
| Late reviews | "Your review comments tend to arrive after we've started the next sprint. Could you review in the first two days?" |
| Great work, uneven communication | "Your designs are clear and thoughtful. A short note on what changed between versions would help me stay up to date." |
| Credit and visibility | "I appreciated your help on the migration. Mentioning the team in the update would make the work more visible." |
For role-specific phrasing, see our peer review examples and templates, covering healthcare, sales, public safety and more.
Constructive feedback for managers
Upward feedback is easier to hear when it describes impact on your work and proposes something workable. Treat it as a problem you want help solving.
| Situation | Constructive feedback |
|---|---|
| Priorities shift midweek | "When priorities change midweek without notice, it's hard to protect deadlines. Could we flag changes in our Monday check-in?" |
| Feedback comes late | "I only learned about the concern at the review. Getting it earlier would let me fix it sooner. Could we add a short monthly check-in?" |
| Not enough context | "I could make better calls on the vendor choice if I understood the budget constraints. Could you share the context before we start?" |
| Micromanaging details | "I'd like to try owning this deliverable end to end and showing you the result at the milestone. Would that work?" |
| Unclear growth path | "I'd like to talk about what skills I'd need for a senior role. Could we set aside time to map them?" |
Constructive feedback in performance reviews
Performance reviews are where vague feedback does the most damage, because the written record stays. Write growth areas the same way you would say them: specific, evidence-based, and followed by a development step. For ready-made wording by competency and rating level, see our performance review comments examples.
| Weak review comment | Constructive review comment |
|---|---|
| "Needs to communicate better." | "Two project updates in Q3 reached the client before the team saw them. For Q4, agree an internal review step and share updates by Wednesday." |
| "Has potential but lacks leadership." | "Led the onboarding project well. To develop leadership, take ownership of the cross-team planning meeting next quarter." |
| "Often misses details." | "Four of the last six deliverables needed corrections before sign-off. A pre-submission checklist should reduce this by the Q4 review." |
| "Doesn't take initiative." | "Waited for direction on three routine tasks this half. Goal for H2: propose and own one process improvement." |
| "Great team member." | "Colleagues cite your willingness to help. To grow, start sharing what you know through one short team session each quarter." |
How to give constructive feedback without discouraging people
Before the conversation, separate what you observed from what you inferred. The constructive feedback planning worksheet (CSV) gives you seven prompts, one illustrative example and space for your own notes: situation, behavior, impact, the other person's perspective, next step, support and follow-up. Open it in a spreadsheet app and replace the example with facts from your own conversation.
The right words can still land badly if the delivery is wrong. These habits keep feedback useful rather than demoralizing.
Focus on behavior, not personality
Describe actions, not traits. "Some deadlines were missed because tasks weren't prioritized" can be fixed. "You're disorganized" can only be defended against.
Pair strengths with growth areas, honestly
Naming a real strength gives context and shows you see the whole person. Skip the automatic compliment that exists only to soften the blow. People notice, and it weakens both messages. Be specific about the strength and about the growth area.
Involve the person in the solution
Oksana, a product manager at a 60-person software company, noticed a teammate's updates were often unclear. Instead of rewriting them, she asked: "What would make the update easiest for you to write?" The teammate suggested a short template. Ownership of the fix made it stick.
Manager: "I noticed some challenges with prioritizing tasks last month. What do you think contributed to that?"
Employee: "I've been juggling multiple projects and wasn't sure which to focus on first."
Manager: "Let's work on a system together to help prioritize tasks more effectively. How about we start with a weekly planning session?"
Time it and place it well
Give feedback soon after the event, in private, and when the person has the energy to hear it. A rushed hallway comment is not a development conversation.
Follow up
Feedback is a conversation, not a one-time event. A week or two later, check progress, acknowledge effort and offer support: "We talked about task prioritization last time. I've seen real progress on meeting deadlines this week. How is the system working for you?"
Regular follow-ups also keep feedback from accumulating until a review. A continuous feedback rhythm of small, frequent conversations means no single one has to carry too much weight.
When constructive feedback isn't enough
This page covers developmental feedback for people who are generally on track. If you're dealing with repeated missed expectations, conduct issues or a conversation you've been avoiding, use the scripts in our negative feedback examples, which are built for harder conversations and include before-and-after phrasing.
If you want the opposite, to reinforce what is going well, see positive feedback examples. Strong teams use all three.
Make constructive feedback a habit
Feedback sticks when it is regular. When feedback is frequent, each individual conversation carries less weight. Structured peer reviews on the FeedbackPulse Pro plan collect growth feedback from several colleagues, so the picture doesn't rest on one person's view. On the Free plan (up to 10 people), anonymous surveys show you what your team needs from managers. Anonymous results stay locked until 3 completed responses exist, and every slice below 3 is masked. To compare the platforms that collect this feedback, see our guide to the best employee feedback tools.
Conclusion
Constructive feedback works when it is specific, forward-looking and followed through. Pick a structure, use real situations, and end every conversation with a next step. Start with one phrase from this page in your next check-in, then follow up.
Frequently asked questions
What is constructive feedback?
Constructive feedback is specific, behavior-focused input that helps a person improve. It describes what happened, the effect it had, and a clear path forward, without attacking the person as an individual.
What is an example of constructive feedback?
A strong example names the behavior and its impact, then invites a solution: 'In the last two sprint reviews, the status update ran long and we lost time for questions. Could you cut it to the three decisions we need from the group? I'm happy to look at the next one with you.'
How do you give constructive feedback to a coworker?
Ask permission first, stay on a specific piece of work, and describe its effect on the shared goal rather than on you personally. For example, 'The handoff notes were missing the client deadline, which cost me a day. Could we add it to the template?' Offer something in return and keep it private.
How do you give constructive feedback to your manager?
Frame it around the impact on your work and offer a workable alternative. For example, 'When priorities change midweek without a heads-up, I struggle to protect deadlines. Could we flag changes in our Monday check-in?' You are raising a problem you want help solving, not issuing a verdict.
What is the SBI feedback model?
SBI stands for Situation, Behavior, Impact. You state when and where something happened, describe the observable behavior, and explain its effect, which keeps feedback factual and easier to hear. See our SBI feedback model guide for templates.
How do you write constructive feedback in a performance review?
Replace labels with evidence and add a next step. Instead of 'needs to communicate better,' write 'two project updates in Q3 reached the client before the team saw them; agree on an internal review step for Q4.' Every growth area should point to a concrete action and a date.
How do you give constructive feedback without discouraging someone?
Focus on behavior rather than personality, be specific, name real strengths alongside the growth area, involve the person in the solution, and follow up. Tone and timing matter as much as the words.