Positive vs Negative Feedback: 50+ Examples for Managers (2026)

Every manager faces the same challenge: how do you tell someone they are doing a great job without sounding hollow, and how do you tell someone they need to improve without crushing their motivation? The answer lies in understanding when and how to use positive and negative feedback effectively.

Research from Gallup shows that employees who receive meaningful feedback are 3.6 times more likely to be engaged at work. Yet a 2025 Workhuman study found that only 26% of employees strongly agree the feedback they receive actually helps them do better work. The gap between intention and impact is where most managers struggle.

This guide gives you more than 50 ready-to-use feedback examples, compares delivery methods and frameworks side by side, and provides a decision-making model so you always know which type of feedback the situation calls for. Whether you are conducting a formal performance review or having a quick corridor conversation, these examples will help you communicate with clarity and confidence.

---

Positive vs Negative Feedback: How They Compare

Before diving into examples, it helps to understand the fundamental differences between positive and negative feedback. Both serve essential purposes, and effective managers use them in combination rather than relying on one over the other.

The ratio matters. Researchers Emily Heaphy and Marcial Losada found that the highest-performing teams received nearly six positive comments for every negative one. That does not mean avoiding constructive feedback entirely; it means building a foundation of trust and recognition that makes corrective conversations more productive.

---

25 Positive Feedback Examples for Managers

The following examples are organized by category so you can quickly find the right words for the situation you are facing. Each example is specific, behaviour-focused, and explains the impact of the employee's actions.

Performance Excellence

1. "Your quarterly sales numbers exceeded the target by 18%. The extra client outreach calls you added to your weekly routine clearly paid off, and the whole team has noticed the momentum you are creating."

2. "The report you submitted on Thursday was exceptionally thorough. Your analysis of the regional data trends gave the leadership team the confidence to approve the expansion budget, and they specifically mentioned your work."

3. "You consistently deliver work ahead of schedule without sacrificing quality. On the Henderson project, you finished three days early and still caught a data error that everyone else missed. That kind of reliability sets the standard for the team."

4. "Your presentation to the board was one of the strongest I have seen this year. You anticipated every question, kept the slides clear and focused, and held the room's attention throughout. The CEO commented on how well-prepared you were."

5. "Since you took ownership of the onboarding process, new hire ramp-up time has dropped from eight weeks to five. That improvement directly impacts our revenue timeline and shows real operational thinking."

Teamwork and Collaboration

6. "When the design team was struggling with the client brief last week, you stepped in to help without being asked. Your willingness to share your expertise across departments makes everyone around you more effective."

7. "I noticed you stayed behind after the meeting to help Marcus work through his analysis. That kind of peer support builds real trust within the team, and Marcus told me your input made a significant difference to his final deliverable."

8. "Your ability to mediate the disagreement between the product and engineering teams during the sprint planning session was impressive. You found a compromise that respected both sides' constraints and kept the project on schedule."

9. "The knowledge-sharing session you organized on data visualization best practices was exactly what the team needed. Three people have already told me they applied your techniques in their client presentations this week."

10. "During the system migration, you proactively coordinated with four different departments to align schedules and minimize downtime. That cross-functional coordination saved us at least two days of disruption."

Leadership and Initiative

11. "You identified the bottleneck in our approval process before anyone else flagged it, and your proposed solution reduced turnaround time by 40%. That is the kind of proactive problem-solving that makes a real difference."

12. "The mentoring you have provided to the junior analysts this quarter has been outstanding. Two of them have already progressed to handling client calls independently, and they credit your guidance as a key factor."

13. "Your decision to pilot the new project management tool with your team before rolling it out company-wide was smart. The lessons learned from your pilot saved us from several implementation issues and gave other teams a clear roadmap to follow."

14. "When the vendor contract fell through, you didn't wait for direction. You researched three alternatives, presented a comparison, and negotiated better terms with the replacement vendor. That initiative kept us on schedule and under budget."

15. "You have built a genuinely inclusive environment in your team. Every voice gets heard in your meetings, quieter team members contribute more actively, and your retention rate is the highest in the department."

Personal Growth and Improvement

16. "Six months ago, public speaking was something you said you wanted to improve. Your presentation at the all-hands meeting last Friday showed real progress. Your pace was measured, your eye contact was natural, and your message landed clearly."

17. "I have noticed a marked improvement in how you handle high-pressure deadlines. Where you used to get visibly stressed and work longer hours, you now prioritize effectively and communicate proactively about timelines. That growth is impressive."

18. "The technical certification you completed on your own time demonstrates genuine commitment to your development. You are already applying those skills in the automation project, and the results speak for themselves."

19. "Your written communication has improved significantly over the past quarter. The client emails you are sending now are concise, professional, and action-oriented. I no longer need to review them before they go out, which frees up time for both of us."

20. "You asked for feedback on your project management skills three months ago and clearly took it seriously. The way you ran the product launch, with defined milestones, clear ownership, and regular status updates, showed a completely different level of organization."

Day-to-Day Excellence

21. "Your attention to detail in the monthly reconciliation process has caught three errors this quarter that would have caused billing issues. That diligence protects both our revenue and our client relationships."

22. "The way you handle difficult customer calls consistently impresses me. You remain calm, empathetic, and solution-focused even when the caller is frustrated. Your customer satisfaction scores reflect that skill."

23. "You are the person the team turns to when they need a complex spreadsheet built or a tricky data problem solved. Your technical expertise is a genuine asset, and I appreciate how willingly you share it."

24. "Your punctuality and preparation for meetings sets a professional tone. You always arrive with an agenda reviewed, questions ready, and follow-up items from the previous session tracked. It makes every meeting more productive."

25. "The documentation you created for the new invoicing workflow is the clearest process guide in the department. Two other teams have already asked to use it as a template. That kind of contribution has a multiplier effect."

---

25 Negative / Constructive Feedback Examples for Managers

Constructive feedback is harder to deliver, but it is just as important as praise. The examples below follow a consistent pattern: describe the specific behaviour, explain its impact, and point toward a solution. None of them attack the person's character, and all of them open the door to a productive conversation.

Missed Deadlines and Time Management

1. "The client deliverable was due on Monday, and it arrived on Wednesday without advance notice of the delay. When deadlines slip, it affects the entire project timeline. Going forward, if you see a deadline at risk, let me know at least 48 hours in advance so we can adjust."

2. "Over the past month, three of your five assigned tasks were completed after the agreed deadline. I want to understand what is causing the delays. Let's review your current workload together and see if we need to reprioritize or redistribute some items."

3. "The sprint review showed that you carried over four incomplete stories from the previous sprint. That pattern is starting to affect the team's velocity. Can we look at your estimation process and identify where the gaps are?"

4. "Your status report was submitted four days late, which delayed the whole department's monthly summary. I know it may feel like a small task, but the downstream impact is significant. What would help you hit this deadline consistently?"

5. "You committed to having the vendor evaluation finished by Friday and did not mention any obstacles until Monday morning. The gap in communication matters more than the delay itself. I need to be able to trust your timeline commitments or be told early when they change."

Quality and Accuracy Issues

6. "The proposal you sent to the client contained three factual errors in the pricing section. The client noticed before we did, and it affected their confidence in our attention to detail. I need you to build a review step into your process before any external document goes out."

7. "I reviewed the code you pushed to production last Thursday and found two issues that should have been caught in testing. Let's walk through your testing checklist together and see where the gaps are, because catching these post-deployment creates avoidable rework."

8. "The data in your quarterly report did not match the numbers from the finance team. When stakeholders see conflicting figures, it undermines the credibility of the entire department. Please cross-reference your sources before finalizing reports."

9. "Your last three client emails contained noticeable grammatical errors and formatting inconsistencies. Written communication represents our brand. I would like you to use the proofreading checklist and, for important communications, have a colleague review them before sending."

10. "The training materials you developed skipped two critical compliance topics that are required for regulatory purposes. This is a serious gap. Let's review the compliance checklist together and update the materials before the next training session."

Communication Problems

11. "During yesterday's team meeting, you interrupted Sarah twice while she was presenting her analysis. When team members feel cut off, it discourages them from sharing ideas. I would like you to be more mindful of letting others finish their points before responding."

12. "Your project updates to stakeholders have been inconsistent. Some weeks you send detailed summaries, and other weeks there is no update at all. Stakeholders have started asking me directly for status, which adds unnecessary communication overhead. Can we agree on a fixed weekly update schedule?"

13. "Several team members have mentioned that your emails are often unclear about what action is needed and by when. Adding a clear next step and deadline at the end of each email would help the team respond more effectively."

14. "When the scope change was approved, you did not communicate it to the testing team for five days. That gap caused them to continue working against the old requirements. In a cross-functional project, timely communication to all affected parties is essential."

15. "In the client call on Tuesday, you shared internal project challenges that the client did not need to know about. There is a difference between being transparent and oversharing. Let's align on what information is appropriate to discuss externally."

Attitude and Professional Conduct

16. "I have noticed that when you disagree with a team decision, you tend to disengage rather than voice your concerns constructively. Your perspective is valuable, and the team benefits when you share it openly during the discussion rather than withdrawing afterward."

17. "During the last two retrospectives, your body language and tone suggested frustration with the process. If you have concerns about how retrospectives are run, I am open to hearing them. But visible disengagement affects the team's willingness to participate honestly."

18. "A colleague has shared that you responded dismissively when they asked for help with the CRM tool. Everyone has different levels of experience with our systems, and supporting each other is part of how this team operates. I need you to approach these requests with patience."

19. "You have made several comments in team channels that could be read as sarcastic or dismissive toward other departments. Even if intended as humour, written messages lack tone, and the impact has been negative. Please be more thoughtful about how your messages may land."

20. "When you received critical feedback during your mid-year review, your immediate reaction was to list reasons why the feedback was wrong. I understand that feedback can feel uncomfortable, but I need you to take time to reflect on it before responding. The patterns I described were observed by multiple people and deserve genuine consideration."

Attendance and Reliability

21. "You have arrived more than fifteen minutes late to four meetings in the past two weeks. When meetings start late or without all participants, it wastes everyone's time. What is causing the scheduling conflict, and how can we address it?"

22. "You called in sick three Mondays in the past two months without much advance notice. I want to be supportive if something is going on, and I also need to plan team coverage. Can we have a candid conversation about what is happening and how I can help?"

23. "You left the team offsite early on both days without informing me. These events are planned with full participation in mind, and your early departure affected the afternoon workshops. If you have constraints, please discuss them with me beforehand so we can make arrangements."

24. "Your camera has been off for the last six consecutive virtual team meetings. In a remote team, visual presence matters for connection and engagement. Unless there are technical or personal reasons I should know about, I would appreciate you turning your camera on for team sessions."

25. "You were unreachable for two hours during core working hours on Tuesday with no calendar block or status update. When the team cannot reach you during agreed-upon hours, it slows down time-sensitive decisions. Please keep your calendar and status current so the team knows your availability."

---

Feedback Delivery Methods Compared

How you deliver feedback matters as much as what you say. Different situations call for different channels, and choosing the wrong one can undermine even perfectly worded feedback.

Choosing the Right Channel

A practical rule of thumb: praise publicly when the person is comfortable with it, and correct privately, always. For anything beyond simple recognition, a live conversation (in-person or video) is almost always the better choice. Written feedback works well as a follow-up to document what was discussed and agreed.

If you are using performance management software to track feedback, make sure the tool supports both real-time recognition and structured review workflows. The best systems allow managers to log feedback moments throughout the year so that formal reviews draw from a rich, documented history rather than relying on recent memory.

---

Feedback Frameworks Compared: SBI, STAR, DESC, and the Sandwich Method

Frameworks give you a repeatable structure so that feedback feels organized rather than improvised. Here is how the four most widely used frameworks compare.

SBI (Situation-Behaviour-Impact)

Developed by the Center for Creative Leadership, the SBI model structures feedback around three elements:

• Situation: Describe when and where the behaviour occurred
• Behaviour: State the specific observable behaviour
• Impact: Explain the effect the behaviour had

Example: "During the client demo on Tuesday (situation), you skipped the product roadmap section that the client specifically asked about (behaviour). The client felt their priorities were not being heard and flagged it in their follow-up email (impact)."

STAR (Situation-Task-Action-Result)

Originally designed for behavioural interviewing, STAR adapts well to feedback:

• Situation: Set the scene
• Task: Describe what was expected
• Action: Detail what the person actually did
• Result: Share the outcome

Example: "When we lost our primary data provider last month (situation), you were responsible for finding a replacement within two weeks (task). You evaluated five vendors, negotiated pricing, and had the new integration running in ten days (action). We avoided any data gaps in our client reporting, and the new provider actually costs 15% less (result)."

DESC (Describe-Express-Specify-Consequences)

DESC is particularly useful for addressing problematic behaviours:

• Describe: State the behaviour factually
• Express: Share how it affects you or the team
• Specify: Request a specific change
• Consequences: Explain what happens if the change does or does not occur

Example: "You have submitted the last three expense reports with missing receipts (describe). This creates extra work for the finance team and delays everyone's reimbursements (express). I need you to attach all required receipts before submitting each report (specify). If the pattern continues, finance will need to hold reimbursements until complete documentation is provided (consequences)."

Sandwich Method (Positive-Constructive-Positive)

The sandwich approach wraps constructive feedback between two positive statements:

• Positive: Start with genuine praise
• Constructive: Deliver the improvement area
• Positive: End with encouragement or confidence

Example: "Your client relationship management has been excellent this quarter, and your retention rate proves it (positive). One area to work on is your internal documentation, which has been inconsistent and makes it harder for the team to cover your accounts when you are out (constructive). I know you have the organizational skills to fix this, and once you do, you will be a strong candidate for the senior account manager role (positive)."

Framework Comparison Table

Which Framework Should You Use?

There is no single best framework. The right choice depends on the situation:

• For everyday coaching: SBI is fast and flexible
• For formal reviews: STAR gives the most complete picture
• For persistent performance issues: DESC provides clarity and accountability
• For new managers still building confidence: The sandwich method is an accessible starting point, though they should graduate to SBI or DESC as they gain experience

---

When to Give Positive vs Constructive Feedback: A Decision Framework

Knowing which type of feedback to give and when is one of the most important managerial skills. Use this decision framework to guide your approach.

Give Positive Feedback When:

• An employee demonstrates a behaviour you want repeated
• Someone goes beyond their normal responsibilities
• A team member achieves or exceeds a specific goal
• You observe improvement in an area that was previously discussed
• A new employee demonstrates strong early performance
• Team collaboration leads to a successful outcome
• Someone handles a difficult situation with professionalism

Give Constructive Feedback When:

• A specific behaviour is negatively affecting outcomes, the team, or the individual's career
• Performance metrics fall below agreed standards
• A pattern of problematic behaviour has emerged (do not wait for it to become chronic)
• An employee seems unaware that their actions are causing issues
• There is a gap between expectations and actual performance that the employee can close
• A mistake was made that could have been avoided and learning will prevent recurrence

The Decision Checklist

Before delivering any feedback, run through these questions:

1. Is this about behaviour or character? Only give feedback on observable behaviours, never on personality traits.
2. Do I have specific examples? Vague feedback is useless. If you cannot cite a specific instance, wait until you can.
3. What is my goal? If it is to vent frustration, wait. If it is to help the person succeed, proceed.
4. Is now the right time? Check that the person is not in the middle of a crisis, about to walk into a meeting, or having an unusually bad day.
5. Am I the right person to deliver this? Feedback carries more weight from someone the employee trusts and who has direct observation of the behaviour.
6. Have I balanced the relationship? If the only feedback you ever give is negative, your credibility and the relationship will erode. Build a foundation of recognition first.

Integrating feedback into your regular workflow is easier with a dedicated performance management platform that prompts managers to provide balanced feedback throughout the year.

---

Common Feedback Mistakes to Avoid

Even well-intentioned managers fall into patterns that undermine the effectiveness of their feedback. Here are the most frequent mistakes and how to correct them.

1. Saving All Feedback for the Annual Review

When feedback is delivered months after the event, it loses its relevance. The employee may not remember the situation clearly, and the opportunity for timely course correction has passed. Build a habit of giving feedback within 24 to 48 hours of observing the behaviour. Use your performance review tools to log observations throughout the year.

2. Being Vague

Telling someone they "need to communicate better" gives them nothing to work with. Specify which communication behaviour needs to change, in what context, and what good looks like. Compare: "Your project update emails need more detail. Specifically, include the current status against milestones, any blockers, and your planned next steps."

3. Making It Personal

Feedback should target behaviour, not identity. "You are careless" is a character judgment. "The last two reports contained data errors that affected client trust" is behavioural feedback that the person can act on.

4. The Feedback Dump

Unloading six months of accumulated issues in a single conversation overwhelms the recipient and makes it impossible for them to prioritize improvement. Address one to two topics per feedback conversation and tackle additional items in follow-up sessions.

5. Ignoring the Feedback Ratio

Teams that only hear what they are doing wrong develop a culture of anxiety and avoidance. Research consistently supports maintaining a ratio of at least five positive interactions for every corrective one. This does not mean inflating praise. It means being as intentional about recognizing good work as you are about addressing problems.

6. Not Following Up

Feedback without follow-up is incomplete. If you told someone they need to improve their meeting facilitation, check in two weeks later to acknowledge progress or offer further guidance. Lack of follow-up signals that the feedback was not important enough to track.

7. Delivering Constructive Feedback Publicly

Never correct someone in front of their peers, their team, or in a shared channel. Public criticism humiliates and damages trust irreparably. Always deliver constructive feedback in a private, one-on-one setting.

8. Using the Sandwich Method as a Crutch

While the sandwich method has its place, over-reliance on it trains employees to brace for bad news whenever they hear a compliment. When you have constructive feedback, deliver it directly and respectfully. Employees prefer honesty over choreographed delivery.

---

Frequently Asked Questions

What is the ideal ratio of positive to negative feedback?

Research from organizational psychologist Marcial Losada and positive psychology researcher Emily Heaphy suggests a ratio of approximately 5:1 (five positive interactions for every negative one) for high-performing teams. This does not mean manufacturing false praise. It means being disciplined about recognizing the many things employees do well alongside the areas that need improvement. Teams that fall below a 3:1 ratio tend to show lower engagement and higher turnover.

Should I give positive and negative feedback in the same conversation?

It depends on the context. In a formal performance review, it is natural and expected to cover both strengths and development areas. In everyday conversations, it is generally more effective to keep them separate. Mixing the two can dilute the positive message or soften the constructive message to the point where it does not register. If you do combine them, make sure each point gets adequate time and attention rather than rushing through the positive to get to the negative.

How do I give constructive feedback to a senior employee or someone older than me?

Focus on the behaviour and its business impact, not on seniority or experience level. Use data and specific examples rather than opinions. Frame the conversation around shared goals: "I want to make sure we are aligned on how we approach client communication so that it reflects the standards we both want for the team." Seniority does not exempt anyone from feedback, and most experienced professionals respect directness when it is delivered with respect.

What should I do if an employee reacts badly to constructive feedback?

First, allow them space to process. Strong emotional reactions are human and do not mean the feedback was wrong. Say something like: "I can see this is a lot to take in. I would rather you take time to reflect on it than respond right now. Let's schedule a follow-up in a day or two." If the reaction is consistently hostile or defensive, address the reaction pattern itself as a separate feedback conversation, and consider involving HR if the behaviour escalates.

How often should managers give feedback?

The most effective managers give feedback continuously rather than saving it for scheduled reviews. A good cadence is at least one piece of meaningful feedback per direct report per week. This includes quick recognition messages, coaching moments, and brief check-ins. Formal structured feedback should occur at least quarterly through your performance management system, with comprehensive reviews annually or semi-annually.

Can positive feedback be harmful?

Yes, if it is vague, insincere, or excessive. Telling everyone "great job" for everything devalues the recognition and makes it meaningless. Positive feedback should be specific, earned, and connected to observable behaviour or results. Over-praising average work can also create complacency and make it harder to deliver constructive feedback when it is genuinely needed.

What is the difference between negative feedback and constructive feedback?

Negative feedback describes what went wrong. Constructive feedback describes what went wrong and provides a path forward. The best managers always aim for constructive: "The report had three errors" becomes "The report had three errors. Let's set up a peer review step so these get caught before submission." The difference is the inclusion of a specific, actionable next step that the employee can take.

---

Conclusion

Positive and negative feedback are not opposing forces. They are complementary tools that, when used skillfully, create a culture of continuous improvement, trust, and high performance. The best managers are not the ones who avoid difficult conversations or who only point out problems. They are the ones who build a rhythm of recognition and accountability that keeps every team member clear on where they stand and where they are headed.

Start with the examples in this guide, adapt them to your context, and commit to giving more frequent, more specific feedback in both directions. Over time, feedback will stop feeling like an event and start feeling like a natural part of how your team operates.

For tools to help you build a structured, consistent feedback practice, explore our performance review guide or see how performance management software can make continuous feedback part of your team's daily workflow.