Positive feedback is not the same as a compliment. A compliment says “you did well.” Positive feedback says “you did this specific thing, in this specific way, and this is why it mattered.” The first is appreciated and forgotten. The second is remembered.
This guide has 75 specific, ready-to-use positive feedback examples organised by situation — peer reviews, performance conversations, 360 feedback, manager feedback, and everyday recognition. It also covers what separates feedback that actually changes how people work from feedback that disappears into the noise.
What is positive feedback?
Positive feedback is specific recognition of something a person did well — the behaviour, the outcome, and the impact — delivered in a way that reinforces that behaviour and makes the person more likely to repeat it.
The word “specific” is doing most of the work in that definition. Positive feedback without specificity is noise. “Great job” tells someone they did well. “The way you caught that error in the client report before it went out saved us from a difficult conversation — and I noticed you’ve been doing that kind of quality check consistently” tells someone what they did, why it mattered, and that someone was paying attention. That second version changes how people work. The first does not.
Positive feedback is distinct from praise (which can be generic), compliments (which are typically social rather than professional), and recognition (which is the broader category positive feedback belongs to). In a workplace context, effective positive feedback is:
Specific — it names the exact behaviour or action, not a general sense of performance. Timely — it arrives close to when the behaviour happened, while the detail is still vivid. Genuine — it reflects something the giver actually noticed, not a formulaic response. Actionable — it tells the person what to keep doing, not just that they’ve been doing something right.
What makes positive feedback effective
The research on feedback in workplace settings is consistent on one point: the specificity of feedback is the single strongest predictor of whether it produces a behaviour change. Generic positive feedback produces a momentary positive feeling. Specific feedback produces a lasting understanding of what is valued and why.
Three things determine whether positive feedback lands:
Specificity over generality. “You’re always so reliable” is a character assessment. “You flagged the dependency issue three days before the sprint ended, which gave us time to fix it without affecting the deadline” is feedback. The second one tells the person exactly what to keep doing.
Proximity to the behaviour. Feedback given the same day a behaviour occurs is significantly more effective than feedback given weeks later. The person can connect the feedback to the specific moment, remember the context, and understand precisely what is being recognised. Delayed feedback is better than no feedback — but same-day or same-week feedback is more effective than both.
Public vs private, matched to the person. Some people thrive on public recognition — a shoutout in the team channel amplifies the feedback and signals to the whole team what is valued. Others find public recognition uncomfortable and respond better to a private message or 1:1 conversation. When in doubt, ask. The same words can have very different effects depending on the format.
Positive feedback examples for colleagues and peers
These examples are written for peer-to-peer feedback — from one colleague to another, in any format from a Slack message to a formal peer review.
On collaboration and teamwork
“The way you brought the two teams together during the handover made a process that usually generates friction feel completely smooth. I’ve never seen that transition go so well.”
“You noticed I was overloaded last week and redistributed two tasks before I even said anything. That kind of awareness is rare and it made a real difference.”
“When the project direction changed halfway through, you adapted without complaint and helped everyone else recalibrate. That flexibility kept the team moving when it could have stalled.”
“You consistently share context across the team rather than holding information close. Everyone benefits from the way you communicate, even when it takes extra time on your part.”
“The way you defended [colleague’s] idea in the meeting when it was getting dismissed too quickly — that kind of allyship matters more than most people realise.”
“You make it safe to raise problems early. The culture on this team is better because of how you respond when someone flags an issue.”
On quality and attention to detail
“The level of care you put into the documentation means the rest of us can actually use it — which isn’t always the case. Thank you for doing it properly.”
“You caught the error in the data model before it went live. I don’t know how you spotted it but that kind of catch is exactly what separates good work from excellent work.”
“Your work comes back clean consistently. That might seem like a baseline but it isn’t — it saves everyone downstream a significant amount of rework.”
“The way you formatted the client-facing report made the findings genuinely accessible. It’s one of the clearest presentations I’ve seen in a long time.”
On communication
“You have a way of asking the question everyone is thinking but nobody wants to ask. That’s a skill and it moves every conversation forward.”
“Your written updates are always clear and complete. I never have to follow up for context.”
“The way you handled the difficult client question on the call was impressive — calm, specific, and honest. The client left satisfied and I learned from watching you do it.”
“You give direct feedback without making it feel like an attack. That’s harder than it sounds and it makes you someone people actually want feedback from.”
Positive feedback examples for employees
These examples are written from manager to direct report — suitable for 1:1 conversations, performance reviews, or written feedback.
On initiative and ownership
“You identified the bottleneck in the process before anyone asked you to, and you proposed a fix before it became a problem. That’s the kind of ownership that makes teams significantly more effective.”
“When the client escalated last month, you handled it completely independently and resolved it without it reaching me. Six months ago that would have needed my involvement. That growth is real.”
“You took the new process and made it better without being asked. The change you made has saved the team an estimated two hours a week — and you documented it so others can follow it.”
“I noticed you prepared three scenarios for the stakeholder meeting rather than one. That preparation changed the quality of the conversation and gave us options when the first direction got pushed back.”
“You asked for a stretch assignment, delivered it ahead of schedule, and gave me a written summary of what you learned. That’s exactly what professional development looks like in practice.”
On reliability and consistency
“In the past quarter, you missed no deadlines, flagged blockers early every time, and delivered everything at the quality level expected. That consistency is the foundation everything else builds on.”
“When you say you’ll do something, it gets done. That sounds like a low bar, but it’s actually rare enough that it makes you genuinely invaluable.”
“Your work has been consistently above the standard we set for this role. I want to name that explicitly because it’s easy to let consistent excellence go unacknowledged.”
On growth and development
“The progress you’ve made on [specific skill] since we talked about it in your last review is significant. I’ve noticed the difference in how you approach [specific situation] and it shows.”
“You asked for feedback on your presentation style three months ago and made a specific change. I saw that change today and it made a measurable difference in how the room responded.”
“You’ve been actively building your technical knowledge outside working hours and it’s showing in the quality of your output. That kind of self-direction is hard to teach.”
On impact
“The work you did on [project] directly contributed to [outcome]. I want to make sure that’s visible to you, because it can get lost in the complexity of a large team.”
“The client specifically mentioned your name in their feedback. That kind of direct, named recognition from a client is unusual and it reflects the relationship you’ve built.”
Positive feedback examples for managers
These examples are written from employee to manager — suitable for upward feedback, skip-level conversations, or 360 reviews. They are often the hardest category of feedback to give and receive honestly.
On leadership and direction
“You gave the team a clear direction at the start of the quarter and then trusted us to get there. That combination of clarity and autonomy produced the best quarter this team has had.”
“When priorities changed, you communicated the reason rather than just the change. That context made it possible to adapt without losing motivation.”
“You make difficult decisions in a way that feels considered rather than arbitrary. Even when I disagree with the outcome, I can see the reasoning and I trust the process.”
On support and development
“You gave me the stretch project I asked for and then checked in without micromanaging. That balance is harder to get right than it looks.”
“When I flagged that I was overloaded, you took it seriously within 24 hours. That responsiveness signals that raising problems is safe here.”
“You give specific feedback rather than general impressions, which means I know exactly what to keep doing and what to work on. That’s rarer than it should be.”
“You advocated for my promotion in a way I later found out about. Knowing that someone is actively supporting your career behind closed doors is a different level of support.”
On team culture
“The way you run our team meetings — starting with wins, giving everyone a turn, ending with clear actions — has made them the most useful meetings I attend.”
“You name recognition publicly and give criticism privately. That distinction signals that this team is a safe place to try things and fail.”
“You hire people who are better than you in specific areas and you let them lead in those areas. The team is stronger for it.”
Peer review and 360 feedback examples
These examples are suitable for structured peer review processes, 360 feedback forms, or any situation where written feedback will be documented and shared.
Strengths to name in peer reviews
“[Name] consistently demonstrates [specific skill]. A clear example was [specific situation], where they [specific action] which resulted in [specific outcome].”
“One of [Name]'s most consistent strengths is their ability to [specific capability]. I’ve observed this particularly in [context], where it had a visible impact on [team/project/outcome].”
“[Name] is someone I actively seek out when I have [type of problem]. Their expertise in [area] has directly improved the quality of my own work on [occasions].”
“What distinguishes [Name]'s contribution to the team is [specific differentiator]. This is visible in [specific situations] and it makes the team’s output better.”
360 feedback examples — what to keep doing
“Continue leading client conversations the way you did in [project]. Your approach to managing expectations while delivering difficult news is something the team should learn from.”
“Keep asking the difficult questions in meetings. The culture of honest challenge you create is unusual and valuable — don’t lose it.”
“Maintain the level of documentation you’ve been producing. It’s raised the bar for the whole team and made the work more sustainable.”
“Keep seeking out perspectives from people who disagree with you. That intellectual honesty is one of your strongest leadership qualities.”
360 feedback examples — what to develop (framed constructively)
“[Name]'s impact would be even greater if they made their reasoning visible before presenting conclusions — the quality of the thinking is there, but sharing it earlier would bring others along more effectively.”
“As [Name] takes on more scope, finding ways to delegate decisions rather than making all of them would help the team develop and free up their time for higher-leverage work.”
Positive feedback examples for specific skills
On problem-solving
“You identified the root cause rather than treating the symptom. That’s a more sophisticated approach than most people take and it prevented the same problem from recurring.”
“The solution you proposed was elegant — it addressed the immediate need and didn’t create three new problems the way the obvious approach would have.”
“When everything was pointing toward one conclusion, you asked the question that revealed it was wrong. That kind of intellectual independence is hard to develop and harder to maintain under pressure.”
On communication and presentations
“You made a complex topic accessible without oversimplifying it. That’s one of the hardest things to do well and you did it consistently throughout the presentation.”
“Your written communication is consistently clear, complete, and at the right level of detail for the audience. I use your updates as a model for how I’d like the whole team to communicate.”
“You held the room’s attention for 45 minutes on a technical topic and left everyone with a clear action. That’s a skill most people never develop.”
On leadership and influence
“You changed the direction of the discussion without taking it over. That kind of influence — moving things without forcing them — is one of the rarest leadership skills.”
“You built trust with the external partner without any formal authority over them. They come to you now because they want to, not because they have to.”
“You made a decision under significant uncertainty, committed to it clearly, and updated it gracefully when new information arrived. That sequence is what good leadership looks like in practice.”
On resilience and adaptability
“When the project scope changed significantly, you recalibrated without losing momentum or morale. The team followed your lead, which tells me something important about how they see you.”
“You handled what was a genuinely difficult situation with a composure that helped everyone else do the same. I don’t know if you realised the effect you had on the room, but it was significant.”
On mentoring and teaching
“The way you onboarded [new team member] — spending time, sharing context, making yourself available — cut their ramp time significantly and built a relationship that will benefit the team long term.”
“You explained something I’ve been struggling with for months in a way I immediately understood. The ability to find the right framing for someone else’s specific gap is a gift.”
Short positive feedback examples — everyday recognition
These are brief, specific examples for Slack messages, Teams kudos, quick emails, or face-to-face moments. Short does not mean vague — even a brief message should name the specific thing.
For quick Slack or Teams messages
“The way you handled [situation] today was exactly right. Appreciated.”
“That question you asked in the meeting changed the conversation. Thank you.”
“You caught [specific thing] before it became a problem. That’s the kind of attention to detail that makes a real difference.”
“The [deliverable] you sent over was exactly what was needed. Well done.”
“I noticed you [specific action]. That doesn’t go unrecognised.”
“[Name] helped me with [specific thing] last week and it saved me hours. Worth saying publicly.”
“The update you sent was the clearest communication on this project. Thank you.”
For peer kudos using Karma in Slack or Teams
@username++ for the way you led the client call today — calm, specific, and completely in control
@username++ your documentation on the new process is the best we've had — the whole team can actually follow it
@username++ for flagging the risk in the proposal before we sent it out — that kind of catch matters
@username++ for stepping in when [colleague] was overloaded last week without being asked
@username++ for asking the question in the meeting that nobody else would ask — it changed the outcome
How to give positive feedback that sticks
Name the specific behaviour, not the general trait. “You’re detail-oriented” is a trait. “You checked the data against the source before including it in the report” is a behaviour. Feedback on behaviour tells someone what to repeat. Feedback on traits tells them something about their personality that they may or may not believe.
Connect it to impact. What was the effect of the behaviour? Who benefited? What didn’t happen as a result? Impact is what transforms recognition from social nicety into professional feedback. “Your catch prevented an error from reaching the client” is more powerful than “good catch.”
Give it quickly. The closer feedback is to the behaviour, the more useful it is. Same day is better than same week. Same week is better than same month. Feedback given at an annual review about something that happened eight months ago is almost useless — the person can barely remember the context and the behaviour has either already changed or become entrenched.
Make it public when appropriate. Public recognition — in a team channel, in a meeting, in a review that others see — amplifies the effect of feedback in two ways. It signals to the team what is valued, not just to the individual. And it creates a social acknowledgement that carries more weight than a private message. For teams using Karma, a peer kudos in the Slack or Teams channel does exactly this — the specific feedback is visible to everyone, tied to a company value, and creates a permanent record of what the team recognises in each other.
Ask first if you’re unsure about format. Some people genuinely prefer private feedback. “I wanted to give you some recognition for what you did — would you prefer I did it publicly or would you rather I told you privately?” takes five seconds and can make the difference between feedback that lands well and feedback that creates discomfort.
FAQ
What is an example of positive feedback? An example of positive feedback is: “The way you restructured the proposal so the problem statement came first made the whole document easier to act on — and I noticed the client responded much faster than usual. That’s the kind of thinking we need more of.” This is specific (identifies what was done), connected to impact (explains the effect), and actionable (tells the person what to keep doing).
What is the difference between positive feedback and constructive feedback? Positive feedback reinforces behaviours that are working — it tells someone what to keep doing and why it matters. Constructive feedback addresses behaviours that need to change — it tells someone what to do differently and what the improvement would produce. Both require specificity to be useful. “Good work” is not positive feedback. “That was frustrating” is not constructive feedback. Effective feedback of any type names the specific behaviour and connects it to a concrete outcome.
How do you give positive feedback to a colleague? Name the specific thing they did, explain why it mattered, and deliver it close to when it happened. A useful formula: “When you [specific action], it [specific outcome]. I wanted to name that because [reason it’s worth naming].” For example: “When you spoke up in the meeting and redirected the conversation, it prevented a decision that would have created significant rework. I wanted to name that because those moments are easy to miss.”
How do you give positive feedback to a manager? Upward feedback follows the same principles as any feedback — specific, genuine, connected to impact — but requires slightly more care about format and timing. In a dedicated feedback session or 360 review, be direct: “The way you communicated the priority change with the reasoning behind it made it much easier to adapt. That transparency makes a real difference.” In informal settings, a brief, genuine acknowledgement is usually appropriate: “The way you handled [situation] today — I noticed and it made a difference to the team.”
How do you write positive feedback for a performance review? For written performance review feedback, structure it as: observation, impact, pattern. “In [project], [name] demonstrated [specific skill] by [specific action]. The result was [specific outcome]. This is consistent with how they approach [category of work] generally — [pattern or example].” The pattern element is what separates performance review feedback from ad hoc recognition — it shows you’ve been paying attention over time, not just to one incident.
What makes peer feedback examples effective? Peer feedback is most effective when it names something the reviewer directly observed — not a general impression of the person’s capabilities. “I’ve always found [name] very reliable” is a character assessment. “In [project], [name] flagged a dependency issue before it affected the timeline and documented the fix for the team” is peer feedback. The observation creates credibility; the specificity creates usefulness.
The recognition connection
The examples in this guide share a common structure: they name what happened, why it mattered, and signal that someone was paying attention. That last element — the signal of attention — is often what makes positive feedback more impactful than a higher salary or a bigger title for the people who receive it.
Teams that build this kind of specific, public, peer-to-peer recognition into their daily rhythm — not reserved for performance reviews, not dependent on a single manager’s awareness — consistently report higher morale, lower turnover, and stronger trust than those that leave it to chance.
Karma makes this structural rather than optional. Peer kudos in Slack and MS Teams, tied to company values, visible to the whole team — so the specific positive feedback that used to live in a private 1:1 or disappear into the noise becomes a permanent, visible record of what the team values about each other.
