Positive Feedback Examples: 30 Lines That Name the Behavior

By Andreas Pettersson, Founder, Leaders ADAPT

You said "great job on the launch" in three 1:1s this week. Each person felt heard and walked out. Ask them on Friday which part of the launch you want again and you'll get three different guesses.

That's the gap these positive feedback examples close. Positive feedback is telling someone what they did, what it caused, and that you want it again. Without that last part, praise is applause. Pleasant, forgotten by lunch.

Gallup found that 80% of employees who got meaningful feedback in the past week were fully engaged (2022, n = 13,490). Meaningful is the operative word. The 1:1 Protocol treats praise as a request with a thank you attached. Below are 30 lines built that way.

What is an example of positive feedback?

Here's one, built on the four letters of SBED: Situation, Behavior, Experience, Demands.

"In Thursday's planning session (S), you asked the two quietest people for their estimate before anyone else spoke (B). We got a number that held, and nobody had to redo the plan on Monday (E). Do that at the start of every planning session (D)."

Positive SBED is the SBED feedback structure applied to good work, where the final step, Demands, asks the person to repeat the behavior.

The D is the part most managers drop, and the only part that says what to do tomorrow. When I teach it, the rule fits in one line: "do more of this" is still a demand. The SBI feedback model page sets all four letters against the older three step version.

What is reinforcing feedback?

Reinforcing feedback is feedback that makes a behavior more likely to happen again. Its opposite, corrective feedback, aims to stop or change a behavior. You'll find the corrective lines on the constructive feedback examples page, and the full taxonomy on types of feedback.

Why "great job" teaches nothing

I made this mistake for years.

I grew up with a Nordic default: you acknowledge a win and you don't make noise about it. In the companies I ran in the US, we had huge wins where "I acknowledge it but I don't celebrate it."

To me that felt respectful. To the room it looked like a poker face. They'd shipped something hard, and their CEO nodded and moved to the next agenda item.

I had to learn the hard way to be more positive, more cheerleading, "more woo." That part I could fix with effort.

The harder part was specificity. Once I started saying more, I said it vaguely, like "Great quarter, team." It told people I was pleased. It didn't tell them why, so they couldn't repeat it on purpose.

Here's the problem: vague praise rewards the outcome and hides the behavior. Your report closed the renewal. Was it the early call to the decision maker, or the cleaner proposal? If you don't say, they'll guess.

Nordic directness cuts both ways. Be plain when something is wrong, and just as plain when something is right.

What the data says about recognition

Stat block: Well recognized employees were 45% less likely to have turned over after two years, in a Gallup and Workhuman study that tracked nearly 3,500 employees from 2022 to 2024. In the same research, 22% of employees said they get the right amount of recognition for their work. Source: Gallup and Workhuman, 2024.

Stat block: In the Leaders ADAPT Leadership Readiness Index, Q3 2026, the skills chapter (n = 66 of 480 completions, self assessed, 0 to 20 scale) put Relational Intelligence at 11.1 and Clarity and Directness at 7.6. Source: leadership skills statistics.

Leaders rate themselves better at the relationship than at saying plainly what they want. Vague praise lives in that gap.

30 positive feedback examples, sorted by what you want repeated

Pick the behavior you want more of first; it decides the words. Each line is illustrative and ends with the ask.

Ownership

1. "You cancelled the auto renewal on the tool we'd stopped using before anyone asked. Keep scanning that renewals list monthly."

2. "When the other team stalled the handover, you called them yourself. We didn't lose a week. Do that whenever work sits between teams."

3. "You told the stand up the delay was your miss, and how to avoid it. Raise it that way every time."

That third one matters most. Where I ran things, whoever raised the red flag and owned the mistake got celebrated for it. Separate the problem from the person and the truth gets cheaper.

A decision made without you

4. "You approved the discount inside our agreed limit and told me after. Decide like that on anything in your range."

5. "You set the launch date without me and wrote down why. I agreed with every reason. Keep making those calls."

6. "You paused the campaign when the numbers dipped and sent me two lines. Right call, right amount of detail. Same format next time."

A clean handoff

7. "Your handoff doc had owner, deadline and what done looks like on page one. The new person needed nothing from you. Use that page every time."

8. "You walked your backup through the three open issues before your leave. Do that before every absence."

9. "You read my request back in your own words. We caught the mix up in thirty seconds, not three days. Keep reading it back."

Calibration in a 1:1

10. "You said your energy was a five, not fine. That gave us something real to fix. Keep giving me the true number."

11. "You brought the problem to our 1:1 before the deadline. Bring things this early every week."

12. "You came with your top three priorities written down, and one clashed with mine. We sorted it before it cost a day. Keep bringing the list."

A hard conversation they led

13. "You told the client about the slip before they asked. Deliver bad news that early every time."

14. "You gave your report the tough feedback yourself instead of routing it through me. Keep owning those."

15. "You disagreed with the room in the budget meeting and showed the math. We changed the plan. Speak up with numbers like that."

Quality

16. "Your report put the answer in the first paragraph. I decided in two minutes. Write every summary that way."

17. "You tested the release on the old devices nobody checks and found the crash first. Add that to your checklist for good."

18. "Every number in the proposal tied to a source. I sent it without edits. Hold that bar on every proposal."

Speed

19. "You shipped a first version in two days and asked for input instead of polishing for two weeks. Keep shipping rough when the stakes allow it."

20. "You answered the customer the same morning, and they said it's why they renewed. Keep that same day standard."

21. "You decided at seventy percent certainty and saved us a week. Decide at that level when the downside is small."

Helping a peer

22. "You spent an hour showing the new analyst the model. They're fixing their own errors already. Keep making that time."

23. "You covered the support queue and left a note for your teammate's return. That's the teamwork I want more of."

24. "You shared your template with the other region unasked. Their prep time halved. Keep passing things around."

Learning

25. "You wrote down why the test failed and changed the process. We won't repeat it. Do a short write up after every miss."

26. "You asked the finance lead to teach you the margin model instead of guessing. Your forecasts tightened. Ask the expert first, always."

27. "You piloted the new tool on one project before proposing it for all. Test small like that."

Pushing back on you

28. "You told me Friday would cost the client deliverable and offered Monday. You were right. Push back whenever my ask collides with something bigger."

29. "You showed me the hole in my plan, in front of the team, with a fix. Keep doing it."

30. "You said no to the extra project and named what would slip. That's the trade off I need to hear. Say it that clearly every time."

Vague vs specific: praise examples side by side

The same moment, written two ways. Only the middle column can be acted on.

Micro-feedback: positive lines in thirty seconds

Not every piece of praise needs all four letters. Most positive feedback for employees that changes behavior happens in half a minute, right after the moment.

Micro-feedback is a thirty second piece of feedback given right after a behavior, with no meeting and no setup, linking what the person did to what should happen next.

Two thirty second versions:

• Walking out of a client call: "The way you paused before answering the objection worked. Do that again on Thursday's call."
• Over chat: "Clean handoff notes on the vendor switch. Same format for the next one, please."

Both name what to keep and ask for it again. That's still reinforcing feedback.

Timing is the other half. The 24/48 Rule says give it inside 24 hours: "Feedback has a half-life. After 48 hours, it's archaeology, not coaching." Save praise for next week's one-on-one meetings and the person has forgotten the details you're praising.

Should positive feedback be public or private?

Both, for different jobs. Public recognition shows the team what good looks like. Private feedback lets you be exact and add a next step without an audience.

My own rule on credit is short:

"If people do good work, they need to hear it in the room, by name, while the win is still visible." Andreas Pettersson

The Rhythm Protocol builds this into the week. The weekly team meeting ends with a five minute recognition round: each person recognizes someone else for a specific behavior with a specific impact, explicitly not "thanks for being awesome." That round writes your recognition examples for employees for you.

Don't skip the private thank you either. I once coached a VP who had just run a large, successful event and came out of it angry. I asked what she'd have needed for it to count as a success: one sentence from her own manager, thank you. Her boss never said it, and no amount of praise from other executives filled the gap.

How do you give positive feedback to an employee?

Five steps. They fit in a hallway or in the calibration part of a 1:1.

1. Catch it inside 24 hours. If you can't say it right away, write the moment down.

2. Name the situation. A day, a meeting, a document. Not "lately."

3. Describe the behavior as a fact. What they did or said, not a trait like "you're so reliable."

4. Say what it caused. For the customer, the team, the numbers, or you.

5. Ask for it again. "Keep doing that." Then stop talking. Don't bolt a "but" onto praise.

Those five steps turn any of the feedback examples for employees above into your own words. The how to give feedback to employees guide puts praise and correction together inside the 1:1, and the manager as coach page covers when to ask instead of tell.

Positive feedback examples FAQ

How much positive feedback is too much?

Positive feedback becomes too much when it stops being specific. Frequent praise that names a real behavior and its effect keeps its value, while repeated generic lines lose meaning fast and can read as insincere. A practical test is whether the person could repeat the praised behavior tomorrow from the words alone. If they could not, the problem is the content, not the amount.

What is positive SBED?

Positive SBED applies the SBED feedback structure (Situation, Behavior, Experience, Demands) to good work. The manager names when it happened, what the person did, the effect it had, and then asks for the behavior again. The final step, Demands, is what separates it from general praise. "Do more of this" counts as a demand, because it tells the person what to repeat rather than only how the manager feels.

How often should managers give positive feedback?

Managers should give positive feedback close to the moment, ideally within 24 hours, and at least weekly. Gallup's 2022 engagement research found employees were 3.6 times more likely to strongly agree they were motivated to do outstanding work when their manager gave daily rather than annual feedback. Short, same day lines tend to shape behavior more than a long review months later.

Can positive feedback be given in writing?

Yes, written positive feedback works well for remote teams, for credit that should reach a performance review, and for wins that involve several teams. It leaves a record the person can reread. The structure is the same as spoken feedback: the situation, the behavior, the effect, and a request to repeat it. Written praise can read colder than intended, so plain, warm wording helps.

What should you avoid when giving positive feedback?

Avoid labels instead of behaviors ("you're a rock star"), praise delayed by weeks, and a "but" that turns praise into criticism. Avoid public recognition for people who have said they dislike it. Avoid praising only outcomes, because the person cannot tell which of their actions caused the result. Each of these makes positive feedback harder to act on.

What are good positive feedback examples for new employees?

Good positive feedback for new employees names small, early behaviors the manager wants to become habits: asking a question instead of guessing, reading back a request, flagging a problem early, or finishing a first task to the agreed standard. For example: "You asked what done looks like before starting, which saved a round of rework. Ask that on every new task."

Praise that asks for a repeat

Stop telling people you're pleased. Tell them what they did, what it caused, and that you want it again. Praise without the D is how a 1:1 ends with everyone feeling heard and nobody knowing what good looks like next week. Put the demand back and every thank you becomes a small piece of training.