The best positive feedback examples name what a person did and what it changed. "Great job on the launch" is a pleasantry, while "You caught the pricing error in the launch deck before it reached the client, which saved us a reissue and an awkward call" is feedback someone can repeat on purpose.
That gap is why so much well-meant praise goes nowhere. People walk away feeling good for a minute, but they don't know which behavior to keep, and the manager who gave it can't tell whether it landed. Specific positive feedback fixes both problems, and it takes about fifteen extra seconds.
This guide gives you more than 50 examples, each shown as a weak version next to a strong version, so you can see exactly what to change. They're grouped by who you're talking to (direct reports, peers, managers, new hires, remote teammates) and by situation (project wins, going above and beyond, skill growth, collaboration, customer impact, leadership, resilience). You'll also get the SBI structure behind them, a clear view on public versus private praise, and a realistic cadence.
Key Takeaways
- Positive feedback works when it pairs one observable behavior with one concrete impact. Adjectives like "great" and "amazing" add warmth but no information.
- The Situation-Behavior-Impact (SBI) structure fits in one or two sentences, and it works for direct reports, peers, managers, new hires, and remote teammates.
- Match the message to the audience: direct reports want a link to growth, peers want their help acknowledged, and managers need to hear which habits to keep.
- Praise publicly when the behavior is visible and tied to team values. Praise privately when the topic is personal or the person dislikes the spotlight.
- Cadence beats formulas. One specific piece of praise per person each week, given within a few days, is a habit most teams can actually keep.
Positive feedback is specific recognition of a behavior and the effect it had, given soon enough that the person knows exactly what to repeat.
Quick reference
The core rule: praise the behavior, then name the impact
- 1.Name the moment, not the trait ("In Tuesday's client call" vs. "You're great with clients")
- 2.Describe the action someone could have filmed ("You repeated her concern back" vs. "Good listening")
- 3.State the impact in a result ("She stayed and upgraded" vs. "It went well")
- 4.Add a repeat cue when it helps ("Please keep doing that on handovers")
Jump to: Weak vs strong · SBI · By audience · By situation · Reviews · Public vs private · Frequency
Why generic praise fails (weak vs strong)
Generic praise isn't harmful, it's just empty. It doesn't tell the person what to do more of, and it can quietly signal that you didn't look closely at the work. Strong positive feedback is nearly always longer by one clause: the impact.
| Weak (generic) | Strong (behavior plus impact) |
|---|---|
| "Great job this quarter." | "You closed the three oldest support escalations in April. Our backlog is under a week for the first time this year." |
| "You're a real team player." | "You stayed after standup to walk Ali through the deployment script. He shipped his first change alone the next day." |
| "Thanks for your hard work." | "Rewriting the proposal over the weekend meant we sent it to the client on Monday morning, a day ahead of the competitor." |
| "Amazing presentation!" | "You led with the churn number and put the background in an appendix. The room was debating the fix within two minutes." |
| "You're so reliable." | "In the last four sprints, every task you owned landed on its date. I've stopped building buffer around your work." |
| "Love your attitude." | "When the vendor slipped, you posted the problem and two options in the channel the same hour. We switched suppliers with a week to spare." |
Notice what changed. The strong versions have a date, a number, a named action, or a visible result. You don't need all four. One concrete detail is usually enough to make praise believable.
How to give positive feedback with SBI
The Situation-Behavior-Impact model is usually taught for corrective conversations, but it's just as useful for praise. It keeps you from drifting into adjectives. Our full SBI feedback model guide covers the framework in depth, and the same three steps apply here.
| Step | What it means | Positive example |
|---|---|---|
| Situation | When and where it happened | "In Thursday's client call..." |
| Behavior | The observable action | "... you paused and repeated her billing concern back to her before answering..." |
| Impact | The result or effect | "... and she stayed on the line, then asked about the annual plan." |
| Repeat cue (optional) | What to keep doing | "That's exactly how I'd like us to open every escalation." |
A good test is whether a colleague who wasn't there could picture the scene from your sentence. If they can, the feedback is specific enough.
Here's how it plays out in practice. Leilani Kahale, the operations lead at a 60-person grocery delivery company, used to end every Friday with "Thanks team, great week." In October she noticed that dispatcher Arash Karimi had rebuilt the late-delivery alert so drivers got a text 30 minutes earlier. Her old message would never have mentioned it. Instead she wrote to him directly: "Your new late-delivery alert (Situation) texts drivers 30 minutes sooner (Behavior). Late-delivery complaints dropped from 14 to 9 this month (Impact). Would you walk the other dispatchers through it?"
Two weeks later, two other dispatchers asked Arash to share the setup. The praise didn't just feel good. It spread the behavior.
If you want to see how this differs from corrective SBI, read our negative feedback examples, which use the same structure for the harder conversations.
Positive feedback examples by audience
The same structure applies everywhere, but what people want to hear changes with the relationship. Direct reports want praise connected to growth. Peers want their help noticed. Managers want to know which habits to keep. New hires need proof that they're on track.
Positive feedback examples for employees and direct reports
When you manage someone, add a line that links the behavior to their development or to a goal. It turns praise into direction.
| Weak | Strong |
|---|---|
| "Great work this quarter." | "You rebuilt the onboarding checklist in March, and new hires now reach their first ticket two days sooner. That's the ownership I'd like to see more of." |
| "Thanks for stepping up." | "When Dina went on leave, you took her three client accounts without being asked and sent me a handover note by Friday. Nothing slipped and the clients never noticed the gap." |
| "Nice presentation." | "In Tuesday's board prep, you opened with the churn number. It got the room talking about the real problem in the first two minutes." |
| "You're a great communicator." | "Your weekly status email names the blocker and the owner in the first line. I can unblock things in five minutes instead of chasing context." |
| "Good job with the customer." | "On the refund call, you repeated the customer's issue back before offering a fix. She went from angry to asking about the upgrade." |
| "I appreciate your attitude." | "You raised the vendor delay in standup as soon as you spotted it, not after it became a crisis. That gave us a week to switch suppliers." |
| "Keep it up." | "You've gone from asking me to review every SQL query to only the ones touching billing. That judgment is what makes you ready for the senior analyst track." |
| "Good teamwork." | "You paired with the new designer for two afternoons on our component library. Her first pull request shipped without rework, and she said it made her feel part of the team." |
For longer-form versions of these, see our positive feedback in a performance review section below.
Positive feedback for a coworker or colleague (peer examples)
Peers don't have positional authority, so positive feedback for a coworker lands best when it's sincere, specific, and sent quickly. A direct message works. So does a short note on a recognition wall. For longer peer write-ups, our 30+ peer review examples and templates cover the formal version.
| Weak | Strong |
|---|---|
| "Thanks for the help." | "Thanks for staying on the call to debug the export script. Because of you, finance had their numbers before the Monday close." |
| "You're so helpful." | "When I got stuck on the pivot table, you screen-shared and showed me the lookup trick instead of just fixing it. I've used it three times since." |
| "Nice job in the meeting." | "In planning, you asked Kofi for his view before we locked the timeline. He flagged a dependency we'd missed, which saved us a sprint of rework." |
| "Good doc." | "Your failover runbook listed the exact commands and the expected output. I followed it at 2 a. m. without paging anyone." |
| "You're a great colleague." | "You cover my queue whenever I'm in a client workshop and leave a note on what's pending. I never come back to surprises." |
| "Thanks for the feedback." | "Your comments on my draft pointed at the two paragraphs where the argument got lost. After I rewrote them, the editor approved it in one pass." |
| "You're so organized." | "The launch tracker you built has an owner and a date on every line. In Friday's review, nobody had to ask who was doing what." |
| "Great energy." | "When the retro got tense, you asked each person for one thing to keep. We left with three agreed changes instead of an argument." |
Positive feedback to a manager (upward examples)
Positive feedback to a manager is rarer than it should be, and managers rarely hear which of their habits actually help. Frame it around the effect on your work, not around their character. You're giving them data, not flattery.
| Weak | Strong |
|---|---|
| "You're a good boss." | "When you told us on Monday that the reorg wouldn't change our scope, I could plan my quarter. Knowing early made it easier to say yes to the new client." |
| "Thanks for the support." | "You backed my decision to push the release by two days when you could have overruled me. That trust is why I raised the next risk early." |
| "I like your feedback." | "Your notes on my proposal named the one assumption that didn't hold and pointed me to the finance data to check it. The revised version was approved." |
| "You're approachable." | "You blocked 30 minutes after my first client escalation to talk it through instead of telling me what to do. I handled the next one on my own." |
| "Great leadership." | "You credited the whole team in the all-hands, including the two contractors. They stayed on through the next quarter." |
| "Thanks for being flexible." | "Letting me shift my hours around school pickup while I still cover the 10 a. m. standup means I can stay in this role. I'm doing my best work in the mornings now." |
Positive feedback examples for new hires
New hires are working without a map. Specific praise early tells them which instincts to trust, and it's one of the cheapest things a manager can do for retention.
| Weak | Strong |
|---|---|
| "Welcome, you're doing great." | "In your second week, you wrote every question you had in the shared doc. The next hire used it, and it's now our onboarding FAQ." |
| "Nice first project." | "Your first customer email followed our tone guide and answered the question in the first line. She replied with thanks, and it's now a sample for the team." |
| "You learn fast." | "You applied Monday's code review feedback to Wednesday's pull request without being reminded. That's exactly the pace we hoped for at day 30." |
| "Good questions." | "Your question about why we invoice on the first of the month led us to an outdated line in the finance doc. Thanks for asking before assuming." |
| "Fitting in well." | "You introduced yourself to the support team and asked for a ride-along. Now engineering has a contact who understands the customer side." |
Positive feedback examples for remote teammates
Remote work hides most of the behavior you'd otherwise notice. Name the channel, the day, and the artifact so the praise doesn't read as generic, and remember that remote people get far fewer hallway compliments.
| Weak | Strong |
|---|---|
| "Great async communication." | "Your handoff post in #launch listed what's done, what's blocked, and who owns the next step. I picked it up from Lisbon at 8 a. m. with no follow-up questions." |
| "Thanks for being responsive." | "You acknowledged my request within the hour yesterday and gave a realistic ETA of Thursday. I could give the client a date with confidence." |
| "Thanks for joining the call." | "Thanks for joining the 6 a. m. call from Auckland twice this month so the EMEA team could attend. I noticed, and I'm rotating the slot so it isn't always you." |
| "Great Loom." | "Your five-minute video on the dashboard bug showed exactly where the filter broke. I fixed it on the first try instead of scheduling a call." |
| "Nice documentation." | "You updated the wiki page the same day the process changed, with a date at the top. Three people used it before I'd announced the change." |
| "You're a self-starter." | "With nobody online in your time zone, you rolled back the deploy and posted a clear timeline in the incident channel. We woke up to a stable system and a full record." |
Positive feedback examples by situation
Sometimes you don't start with the audience, you start with the moment. These examples are grouped by what just happened. Mix and match them with the audience tables above.
Project wins
| Weak | Strong |
|---|---|
| "Congrats on the launch." | "The launch hit the March 3 date because you split the migration into three releases and tested each one. Support saw zero rollback tickets in the first week." |
| "Great project." | "You ran the pricing-page test for six weeks and reported the result even though it lost. That clarity let us stop debating and move on to the next hypothesis." |
| "Good result." | "You turned the Q2 audit from a two-week scramble into a three-day review by building the evidence folder as you went. The auditors asked to use it as a model." |
| "Well done on the deal." | "You spotted that the client's real concern was data residency, not price, and brought in security early. The contract closed a week ahead of forecast." |
Going above and beyond
| Weak | Strong |
|---|---|
| "Thanks for the extra mile." | "You drove to the warehouse on Saturday to relabel the order when the shipment was wrong. The customer had the right goods on Monday and kept their contract." |
| "You always go above and beyond." | "You wrote a one-page guide for the migration even though it wasn't in your task. Two other teams are already using it." |
| "Thanks for the extra effort." | "You volunteered to cover the support queue during the offsite and left a clean log of open issues. We came back to zero unresolved escalations." |
Skill growth
| Weak | Strong |
|---|---|
| "You've improved a lot." | "Six months ago you needed help structuring every report. This one went to the client unedited, and the structure was clearer than mine would have been." |
| "Nice progress." | "You've started leading the Thursday demo yourself, and your questions to the audience have gone from rehearsed to responsive. That's the facilitation skill in your development plan." |
| "Good learning." | "You finished the data visualization course and rebuilt the churn chart with it that same week. Sales now reads it without a walkthrough." |
Collaboration
| Weak | Strong |
|---|---|
| "Great teamwork." | "You asked design and engineering to review the spec together before kickoff. We caught the mobile constraint on day one instead of week five." |
| "You work well with others." | "You gave the intern a real piece of the migration and checked in daily. She presented it at the team meeting, and we gained capacity we didn't have before." |
| "Thanks for sharing." | "You posted your client QBR template in the shared drive with a short how-to. Three account managers used it this month and cut their prep time." |
Customer impact
| Weak | Strong |
|---|---|
| "Customers love you." | "The customer's review mentioned that you stayed on the chat until her payroll import worked. Reviews like that make renewal conversations easier." |
| "Great support." | "You noticed the same login question five times in a week and wrote a help article. Tickets on that topic dropped, and agents got back to harder problems." |
| "Nice handling of the complaint." | "You called the customer back within the hour and explained exactly what had gone wrong, without excuses. He went from threatening to cancel to booking a review call." |
Leadership
| Weak | Strong |
|---|---|
| "You're a natural leader." | "When the plan changed Thursday, you gathered the team for ten minutes, restated the goal, and reassigned owners. By Friday morning, nobody was waiting on a decision." |
| "Good mentoring." | "You let Tunde present his own analysis to the VP and stepped in with only one question. He got the visibility, and you built a stronger bench." |
| "Great decision." | "You said no to the extra feature in the release and explained the trade-off to the sponsor in plain language. We shipped on time and the sponsor stayed supportive." |
Resilience
| Weak | Strong |
|---|---|
| "Thanks for hanging in there." | "After the client pulled the project in May, you kept the team focused by sharing what we'd learned and which parts we could reuse. Two of those parts shipped in the next product." |
| "You handled it well." | "When your demo broke in front of the client, you narrated what was happening, switched to the backup recording, and finished on time. The client praised your calm in the follow-up." |
| "Good recovery." | "You owned the missed invoice in the team channel the same hour, fixed it, and added a check to the template. It hasn't happened since." |
Positive feedback in a performance review
Written praise lives longer than spoken praise. It gets reread at promotion time, shared with skip-level managers, and used to calibrate ratings. That makes vague phrases like "exceeds expectations" especially costly, because they can't be defended later.
| Weak | Strong |
|---|---|
| "Strong communicator." | "Delivered monthly stakeholder updates that cut ad-hoc status requests from about ten a month to two. Next cycle, extend the format to the partner team." |
| "Exceeds expectations in ownership." | "Took over three accounts during a colleague's leave with no escalations and a written handover. Ready to own a portfolio from the start of next year." |
| "Great collaborator." | "Ran the cross-team spec review before kickoff on two projects, catching a mobile constraint in week one. Recommend making it the default for all launches." |
| "Always delivers." | "Hit every committed date across four sprints, including the migration. This reliability is the basis for putting this person forward for tech lead." |
Three rules keep written praise credible:
- Tie it to a goal or competency. "Supports the Q3 retention goal" gives the praise a place in the review framework.
- Include one number or one named outcome. If you can't, the feedback probably isn't specific enough yet.
- Finish with a next step. "Build on this by..." turns recognition into a development conversation.
For more on structuring peer comments that feed into reviews, see our peer review examples.
Public vs private praise: when to use each
Public praise spreads good behavior and signals what the team values. It can also backfire. Some people dislike attention, and praise that feels uneven can read as favoritism. Choose the setting on purpose.
| Situation | Best channel | Why |
|---|---|---|
| A visible win that reflects a team value | Public (team channel, all-hands, Kudos wall) | Others learn what good looks like |
| Personal growth, confidence, or a sensitive topic | Private (1:1 or direct message) | Specific growth is personal and doesn't need an audience |
| Someone who dislikes the spotlight | Private or written | Public praise can feel like pressure |
| Praise that goes into a formal record | Written (review document or Kudos note) | It's referenced later and needs to be precise |
| A group achievement | Public, naming each contribution | Shared credit only works when it's specific |
Sven Lindqvist, an engineering manager at a 25-person fintech, learned this the hard way. He praised Valentina Rossi in front of the whole company for staying up to fix a production issue. Valentina, who avoids attention, told him afterward that it made her dread the next incident. Sven changed his approach: he now asks each person once, at onboarding, how they like to be recognized. Valentina gets a written note and a private thank-you, and her incident work gets named in the quarterly review.
One more rule: spread praise fairly. If the same two people appear on every shout-out, everyone else notices. A quick monthly scan of who has been recognized, and who hasn't, takes five minutes and protects trust.
How often to give positive feedback
There's no magic number, and anyone who gives you one should be asked for the source. But there is some useful evidence on direction.
In a 2013 Harvard Business Review article, Jack Zenger and Joseph Folkman reported that in their dataset the highest-performing teams gave far more positive than negative feedback, about 5.6 positive comments for every negative one, compared with roughly 1.9 for average teams and under 1 for the lowest performers. That's a correlation from one dataset, not a quota, and managing to a ratio would make your praise feel mechanical. What it does suggest is that for most teams, praise is the under-supplied half of the feedback conversation.
Gallup's long-running Q12 engagement survey points the same way. One of its twelve items asks whether employees have received recognition or praise for good work in the last seven days, which tells you how seriously researchers treat the cadence of appreciation.
A practical habit for most managers:
- Weekly: Send at least one specific piece of praise to each direct report.
- Within a few days: Sooner is better, because details fade and the impact feels less real.
- Monthly: Check who hasn't been recognized, and fix the gap.
- Quarterly: Fold the best examples into written reviews so the recognition is on the record.
This weekly habit is the positive twin of the continuous feedback loop idea: small, frequent conversations that mean no single conversation carries too much weight.
Common mistakes with positive feedback
- Praising only outcomes. "Great result" rewards luck as much as skill. Praise the behavior that caused the result.
- Saving it for reviews. Annual praise feels like an audit, not appreciation.
- Using praise as a buffer. Wrapping criticism in compliments teaches people to distrust both. If you need to correct something, use the scripts in our negative feedback examples or the approach in our guide to giving constructive feedback without discouraging employees.
- Praising the same people. High performers get recognized constantly. Steady contributors and behind-the-scenes people often get nothing.
- Comparing people. "You're better than Jordan at this" creates a rivalry. Praise against the standard, not against a colleague.
- Over-polishing. A short, specific note sent today beats a perfect one sent next month.
Make specific praise a team habit
Knowing how to give positive feedback is the easy part. Doing it every week, across a whole team, is where most efforts fade. Mateo Salvatierra, the founder of a nine-person design studio spread across four time zones, solved it with one rule: every Friday, each person sends one specific Kudos to a teammate using the Situation-Behavior-Impact structure. After a month, nobody needed reminding. Quiet contributors started showing up in the notes, and the weekly rhythm made recognition part of how the studio works.
FeedbackPulse's employee recognition module is built for exactly this. Employees pick a colleague, choose Kudos, write a short message, decide whether to send it anonymously, and preview it before sending. Recipients keep a record of what they've received, and approved Kudos can appear on a public Kudos wall that admins can run in named, anonymous, or off mode. Kudos recognition is included on the Free plan for teams of up to 10 people.
If you're designing a broader program, our guide to employee recognition programs covers program types, rollout, and measurement.
Specific praise is cheap to give and expensive to lose. Pick one person on your team today, think of one thing they did this week and what it changed, and write it down in two sentences. That's the whole method.
Last Updated: October 2026
Frequently asked questions
What is a good example of positive feedback?
A good example names the behavior and its impact. 'You rebuilt the onboarding checklist in March, and new hires now reach their first ticket two days sooner.' It works because the person knows exactly what they did well and why it mattered, so they can repeat it. 'Great job' feels nice but teaches nothing.
How do you give positive feedback to a coworker?
Describe the specific thing they did and what it changed for you or the team, then say it soon after it happens. For example, 'Thanks for staying on the call to debug the export script. Finance got their numbers before the Monday close.' Peers don't need a formal setting, a direct message or a Kudos note works well.
How do you give positive feedback to your manager?
Focus on the effect their behavior had on your work, not on their personality. For example, 'When you told us early that the reorg wouldn't change our scope, I could plan my quarter.' Specific upward praise tells a manager which habits to keep, which is more useful to them than general thanks.
How do you write positive feedback in a performance review?
Replace labels like 'exceeds expectations' with a concrete behavior, a result, and a link to a goal or competency. Write 'Delivered monthly stakeholder updates that cut ad-hoc status requests from about ten a month to two' instead of 'strong communicator'. Add one sentence on how to build on the strength next cycle.
How do you give specific positive feedback?
Use the Situation-Behavior-Impact structure. Name when and where it happened, describe the observable action, and state the result. Keep it to one or two sentences, avoid vague adjectives such as great or amazing, and add a short cue about what to keep doing.
Should positive feedback be public or private?
Use public praise for visible behavior that reinforces team values, and private praise for personal growth, sensitive situations, or people who dislike the spotlight. When in doubt, ask people once how they prefer to be recognized, and share praise fairly across the team so it doesn't look like favorites.
How often should you give positive feedback?
Often enough that it feels routine, not rare. A practical habit is at least one specific piece of praise per direct report each week, delivered within a few days of the work. Research from Zenger and Folkman links high-performing teams to far more positive than negative feedback, but treat that as direction, not a quota.