New Manager DailyHow to give positive feedback to an employee
Good positive feedback is specific, soon and honest: say exactly what the person did, why it mattered, and that you noticed, ideally the same day. "Thanks for the report" is polite. "Your summary on page one let me answer the director in two minutes, and that's the third time this month you've saved me like that" is feedback. Do it often, and keep it separate from criticism, so praise doesn't start to sound like a warning.
Most new managers know praise matters and still give too little of it, or give it so vaguely it doesn't land. Below: a three-part sentence you can use every time, ten vague lines rewritten, how often to do it, when to praise in public and when in private, written feedback, praise for quiet, remote and senior people, what to do when someone brushes it off, and the ways praise backfires.
Why positive feedback is worth the effort
Positive feedback isn't only about morale. It tells people which behaviour to repeat. Criticism says "not that"; praise says "more of this", which is often the more useful message.
It's also scarce. Gallup's research on recognition at work found that only about one in three US workers strongly agree they received recognition or praise for good work in the past seven days, and that employees who don't feel adequately recognised are twice as likely to say they'll quit in the next year. Gallup recommends recognising good work about every seven days.
For a new manager, praise has one more job: it shows the team what you value. Whatever you notice out loud is what people will do more of.
The three-part sentence
Every piece of positive feedback can follow the same shape:
- What they did: one specific action or result, not a trait.
- Why it mattered: the effect on a customer, the team, a deadline, you.
- What you'd like (optional): more of it, or a chance to share it.
"When the client got angry on the call, you stayed calm and offered the two options without getting defensive. (What.) They signed off on the second one this morning, so we kept the account. (Why it mattered.) Would you walk the team through how you handled it on Thursday? (What next.)"
Three sentences, under 20 seconds. You don't need a meeting for it.
Praise what people did, not what they are. "You're so smart" says nothing they can repeat. "You checked the numbers against last year before sending, and caught the error" tells them exactly what to keep doing. Researchers on growth mindset make the same point: praising effort and method encourages people to keep trying when things get hard, while praising talent can make them avoid risks.
Ten vague lines, rewritten
| Vague | Specific |
|---|---|
| "Great job!" | "The way you broke the launch into weekly steps made it easy for everyone to see what's next. Thanks." |
| "Nice presentation." | "Starting with the customer's complaint got the room's attention straight away. Two people asked me for your slides." |
| "Thanks for staying late." | "Thanks for staying to finish the orders. Because of you, Monday's shipment left on time." |
| "You're a great team player." | "You spent an hour helping Sam with the spreadsheet when you had your own deadline. He finished his part because of it." |
| "Good work on the project." | "You flagged the budget problem in week two instead of week eight. That gave us time to fix it." |
| "Your attitude has been really good." | "In the last two meetings, you've asked for other people's views before giving yours. It's made those meetings better." |
| "Customers love you." | "Three customers this month mentioned you by name in their reviews, for following up after the fix." |
| "Well done on your first month." | "In your first month you learned the system fast enough to take calls alone in week three. That's quicker than most." |
| "Thanks for your hard work." | "You cleared the backlog from 60 tickets to 12 this week. That's the lowest it's been since summer." |
| "Good email." | "Your email to finance was short and had the one number they needed at the top. They replied in an hour." |
The pattern: swap the adjective for the action, and add the result. Our employee feedback examples page has 40 more lines, for praise and for the harder talks.
When and how often
- Soon. The same day if you can, the same week at most. Praise saved for a performance review is history by then; the person may not remember what they did.
- Often. Aim for something specific for each person at least once a week, in line with Gallup's seven-day suggestion. If you have eight people, that's eight short sentences a week.
- Earned. Never invent praise to hit a number. People can tell, and it makes your real praise worth less.
- Separately from criticism. If every piece of praise is followed by a "but", people learn to brace when you say something nice. Give purely positive feedback on its own, often, and give criticism in its own conversation.
A simple habit that helps: at the end of each day, ask yourself "who did something worth naming today?" and tell them before you leave, or first thing tomorrow. Keep a list of names with dates if you manage more than a few people, so nobody goes a month without hearing anything.
Public or private?
Ask, or watch. People differ a lot here, and the wrong choice can make praise feel like a punishment.
| Setting | Good for | Careful with |
|---|---|---|
| One to one, in person | Personal effort, growth, anything sensitive | Nothing; this is the safe default |
| In the team meeting | Work that helped the whole team; behaviour you want others to copy | Shy people; always praising the same person |
| In writing (email, chat) | Something they can keep; remote staff | Too short ("thx!") reads as automatic |
| To your boss, with them copied | Big wins; people hoping for promotion | Taking credit yourself by accident |
A good question for your first one-on-ones: "When you've done something well, how do you like to hear about it? In front of the team, or just from me?" Write the answer down.
Telling your own manager about someone's work is one of the most valuable kinds of praise you can give, and new managers forget it. It costs you one email: "Wanted you to know that Priya rebuilt the onboarding checklist on her own time. New hires now get set up in a day instead of three."
Written positive feedback
A written note lasts. People keep them, reread them on bad days, and use them at review time. It doesn't need to be long:
Subject: The supplier call
Hi Sam, I wanted to say properly: the way you handled the supplier this morning was excellent. You had the delivery numbers ready, you stayed polite when they pushed back, and we got the refund. That's saved us about two weeks of chasing. Thank you.
For a review or appraisal, use the same structure, one example per point: "Sam handled three difficult supplier disputes this quarter, each resolved without escalation, including the March refund." Keep a running note through the year so you aren't trying to remember in December.
Praise for different people
Quiet or shy people
Private and written usually works best. Don't spring public praise on them; if you want to mention their work to the team, ask first: "Mind if I mention the checklist in Thursday's meeting?"
Remote staff
They miss the passing "nice one" in the corridor, so they often hear less praise without anyone meaning it. Be deliberate: a short message the day it happens, a mention in the team channel, a minute at the start of your video one-on-one.
Senior or experienced people
Generic praise can feel patronising to someone who's done the job for 15 years. Be more specific, and focus on the effect: "Because you mentored the two new starters, they were taking calls a week earlier than planned." Praising judgement and influence fits better than praising effort.
New employees
Praise the early signs of what you want: questions asked, steps followed, small things done right. New people are often unsure whether they're doing well; a specific "you're on track, and here's why" in the first few weeks matters a lot. See our guide on giving difficult feedback for when something in those weeks needs correcting.
Your strongest performer
They get the least praise on many teams, because managers assume they know. They don't always. Name the specific things that make them strong, and talk about what they want next.
Someone who's struggling
Find the real improvements and name them, however small: "Your last two reports came in on time. That's exactly what we talked about." It shows that you notice progress, not only problems. Don't inflate it, though; false praise for someone on an improvement plan sends a confusing message.
When they brush it off
Some people deflect praise: "It was nothing", "Anyone would have done it", "It was really Sam." Don't argue, and don't let it go entirely:
"Maybe, but you're the one who did it, and I wanted you to know I noticed."
"Sam helped, I know. And the decision to call the client back was yours."
Then move on. Over time, consistent specific praise lands even with people who can't accept it in the moment.
How positive feedback backfires
- The feedback sandwich used every time. Praise, criticism, praise. Used now and then it can soften a hard message; used always, people stop hearing the praise and wait for the middle.
- Praising the same person over and over in front of the team. Others start to feel invisible, and the person praised can become resented.
- Praise that's really a request. "You're so good at this, could you also take on…" makes people wary of being praised.
- Praising results only. If you only notice the big wins, people who do steady, invisible work (the checking, the helping, the tidying up) hear nothing.
- Comparing. "I wish everyone was as organised as you" praises one person and criticises the rest.
- Praising the person's looks or personal life. Keep it about the work.
Make it a habit: a simple weekly routine
| When | What | Time |
|---|---|---|
| Every day, end of day | "Who did something worth naming?" Tell them. | 1–2 min |
| Each one-on-one | Open with one specific thing they did well since the last one | 1 min |
| Weekly team meeting | One piece of recognition for work that helped the team | 2 min |
| Friday | Check your list: anyone not mentioned this week? | 2 min |
| Monthly | One email to your boss naming someone's work | 5 min |
For a recognition slot in your team meeting, our team meeting agenda template has a monthly version with it built in.
Some leadership styles find praise easy and criticism hard; others the reverse. The free leadership style quiz takes about 2 minutes and shows which feedback you're likely to give too little of.
Questions about positive feedback
How do you give positive feedback to an employee?
Say what they did, specifically, and why it mattered, as soon as you can after it happens. Keep it short and separate from any criticism.
How often should a manager give positive feedback?
At least once a week per person, when it's earned. Gallup recommends recognising good work about every seven days.
Can you give too much positive feedback?
Too much vague praise, yes: it stops meaning anything. Specific, honest praise is rarely too much. If you're unsure, check that each piece names a real action.
Should positive feedback be in public?
Sometimes. Private is the safe default; public works well for work that helped the whole team, with people who are comfortable with it. Ask each person what they prefer.
What's an example of positive feedback?
"Your summary on the first page let me answer the director in two minutes. That's exactly what I needed; please keep doing it that way."
Next: see 40 more lines in our employee feedback examples, take the free leadership style quiz, or browse all our guides for new managers.
Sources
- Gallup, "Employee recognition: low cost, high impact", 2016 (updated 2024): https://www.gallup.com/workplace/236441/employee-recognition-low-cost-high-impact.aspx
- Recruitee, "How (and why) to give positive feedback to employees": https://recruitee.com/blog/positive-feedback-to-employees
- Indeed, "7 ways to effectively give employees positive feedback": https://au.indeed.com/hire/c/info/positive-feedback
- Carol S. Dweck, Mindset: The New Psychology of Success, Random House, 2006.