Feedback is one of those things everyone agrees matters and almost nobody does well. Not because people don't care, but because knowing what to say in the moment is harder than it sounds.
"Great job" says nothing. "You need to improve your communication" gives nowhere to go. Most feedback lands somewhere between those two and achieves about as much.
This guide skips the theory and gets to the language. Below are 20+ ready-to-use examples across common workplace scenarios, plus the delivery principles that make feedback stick rather than bounce.
Why feedback gaps are costly
Only 23% of U.S. employees strongly agree they received meaningful feedback in the past week [1]. Not occasionally. In the past week.
That number has real consequences. Employees who receive regular, high-quality feedback are 2.5 times more likely to be engaged than those who don't [1]. Gallup also found that employees who felt strongly recognized were 45% less likely to leave their jobs over a two-year period [2].
For managers and HR professionals, the case is simple: a consistent feedback habit costs nothing but time and pays back in retention and engagement. Most teams aren't doing it.
Examples of feedback for hard work
Recognizing effort beyond just outcomes tells people that the process matters, not just the result.
"The way you pushed through the product launch last week didn't go unnoticed. You kept the timeline intact when three things went wrong at once. That kind of composure under pressure is what the team needed."
"You've been putting in extra hours on the migration project and it's showing. The handoff docs you prepared saved the team at least a full day of catch-up. Thank you for thinking ahead."
"I want to call out how much effort you put into preparing for the client presentation. It showed in how confidently you handled their questions. That preparation made a real difference to how the meeting landed."
"You took on a task that was outside your usual scope and figured it out without being prompted. That kind of initiative is exactly what moves a team forward."
"The report you submitted was thorough and well-structured. It's clear you spent time on it. That level of care makes it much easier for the people who rely on it downstream."
Examples of feedback for teamwork
Team-focused feedback works best when it names the specific behavior and the effect it had on others.
"The way you brought the design and engineering teams into alignment last sprint saved everyone a week of back-and-forth. You spotted the disconnect early and closed it before it became a problem. That kind of cross-team awareness is hard to teach."
"When Maya was out sick during the product review, you picked up her section without being asked and presented it like you'd prepared it yourself. The meeting didn't skip a beat. That's the kind of reliability that makes a team function."
"You've been consistently sharing context with people who need it before they have to ask. It's a small habit but it has a visible effect on how smoothly the team moves. Keep doing it."
"The way you handled the disagreement between the two teams in Thursday's session was well-judged. You didn't take sides, you kept the focus on the shared goal, and both teams left with a workable path forward."
"You actively brought quieter voices into the discussion in last week's planning session. Two of the best ideas in that meeting came from people who might not have spoken without your prompting. That's good facilitation."
Examples of feedback for skills
Skill-specific feedback is most effective in performance conversations and development check-ins. Name the skill, give the evidence, explain the impact.
"Your data analysis on the Q3 report was a step up from what we've seen before. You didn't just present the numbers, you identified the pattern underneath them and explained what it meant for the decision we needed to make. That's the difference between reporting and insight."
"Your writing has gotten noticeably sharper over the past quarter. The proposal you submitted last week was concise, well-structured, and easy to act on. Whatever you've been doing differently, keep doing it."
"The way you structured the project plan showed strong systems thinking. You anticipated three dependencies that the rest of the team hadn't spotted yet. That kind of upstream thinking saves everyone time later."
"Your facilitation skills have developed considerably. Six months ago you struggled to keep the room on track; last week's workshop ran to time, covered everything it needed to, and ended with clear next steps. That's a meaningful improvement."
"The client call last Thursday showed how much your negotiation skills have grown. You held your position without creating friction, found the trade-off they could accept, and closed it in one session. That used to take two or three rounds."
"Your presentation delivery is getting stronger. You used to read from your slides; now you're using them as a prompt and speaking to the room. The difference in how the audience engages is noticeable."
Examples of feedback for personality and soft skills
Acknowledging character and interpersonal qualities matters for team culture, but it works best when tied to a concrete situation rather than delivered as a general compliment.
"When the project hit a wall in week three, your attitude was the thing that kept the team from losing momentum. You didn't catastrophize, you problem-solved. That steadiness in a difficult moment had a visible effect on everyone around you."
"You have a rare ability to read the room. In last Monday's meeting, you noticed that two people were confused before anyone said anything, and you slowed down to check in. That kind of awareness makes you easier to work with than most people realize."
"The way you handled the miscommunication with the client last month showed real emotional intelligence. You absorbed the frustration, stayed calm, and redirected the conversation without making anyone feel blamed. The relationship is stronger now because of how you managed that moment."
"You're consistently generous with your time when colleagues need help. That generosity has a real effect on the people around you, and it doesn't go unnoticed. The team functions better because you're in it."
"You bring a level of optimism to difficult situations that is genuinely useful, not performative. When the timeline got compressed last quarter, your instinct was to find what was still possible rather than focus on what wasn't. That framing helped the whole team stay productive."
"Your curiosity makes you better to work with. You ask questions that other people were thinking but didn't ask, and that habit consistently moves conversations to a more useful place."
Constructive examples of feedback for colleagues
Constructive feedback should address a specific behavior, explain the effect it has, and offer a concrete path forward. The goal is a direction, not a verdict.
"I've noticed you tend to jump in before others finish their point. In last Tuesday's planning session, a couple of ideas got dropped because the thread was cut short. Would it help to agree on a signal for when someone wants to add to the discussion?"
"Your individual work is strong, but the team misses out when you don't bring others in earlier. When we combined your analysis with Priya's market data last month, the recommendation was sharper than either alone. Worth doing more of that."
"Your idea in the Friday review had real potential, but the team struggled to evaluate it without concrete examples. Next time, could you bring one specific scenario showing how it would work in practice? That would make it easier for people to build on it."
"Three deadlines slipped last month, which created knock-on delays for two other team members. I don't want to just flag it. I want to understand what's blocking you. Is it the volume of work, the priorities, or something else? Let's work out what needs to change."
"Your standards are high and your output shows it, but I'm seeing signs that the pace isn't sustainable. Missing a few breaks isn't a virtue, it's a risk. Can we look at your current load and find something to adjust before it becomes a bigger problem?"
"The quality of your work is consistently good, but the time it takes is creating pressure on the team's schedule. Have you tried time-blocking or batching similar tasks? I'm happy to walk through some approaches together if that would be useful."
"The content of your session was solid, but the audience disengaged in the second half. Adding a quick poll or a few structured questions would keep people active and give you a read on whether the points are landing in real time."
"The work itself is good, but I'm finding it hard to track where things stand without a shared structure. Would you be open to using a shared project board for the next sprint? It would make it easier for everyone to stay aligned without extra check-ins."
How to deliver feedback that actually works
The examples above only go so far. Delivery determines whether the words land or get dismissed.
The first principle is specificity and timing. Feedback delivered close to the event is more actionable. "Your summary in this morning's standup was clear and saved five minutes of back-and-forth" is more useful than the same observation offered three weeks later. The more specific the detail, the harder it is to rationalize away.
The second is focusing on behavior, not character. "You interrupted three times in the meeting" is something someone can change. "You're a bad listener" is not. The first describes a behavior; the second makes a judgment about who someone is. Behavioral feedback generates less defensiveness and more follow-through.
It's also worth reconsidering the feedback sandwich. The positive-negative-positive structure is widely used, but research suggests it often dilutes the message. A study published in Teaching and Learning in Medicine found that the corrective-positive-positive sequence tends to outperform the classic sandwich, partly because the critical message gets softened into irrelevance when buried between compliments [3]. Directness, delivered respectfully, works better than padding.
Finally, make it a conversation. Feedback works best as a two-way exchange. After raising an observation, ask: "How do you see it?" or "What would be most useful from me here?" The person receiving feedback often has context you don't. Getting it means the solution is more likely to stick.
Common mistakes to avoid
Even well-intentioned feedback can miss the mark. A few patterns consistently get in the way.
The first is waiting for formal review cycles. Annual or quarterly reviews are too infrequent to be the primary feedback channel. By the time the conversation happens, specific examples have faded, patterns have hardened, and the person has had no chance to course-correct. Feedback given close to the moment it applies is far more useful than the same observation delivered months later in a structured document.
The second is keeping it too vague to act on. Phrases like "you need to be more proactive" or "work on your presence" sound like feedback but contain no actionable information. The person receiving it often walks away unsure what to actually do differently. Every piece of feedback should answer one question: what specifically should this person start, stop, or keep doing?
Delivering constructive feedback in public is the third. Calling out a problem in front of others, even gently, shifts the focus from improvement to self-protection. The person is more likely to become defensive than receptive. Positive feedback can work well in group settings; corrective feedback almost always lands better one-on-one.
Finally, treating feedback as a one-time event. A single conversation rarely changes behavior on its own. Following up, acknowledging progress, noting when old patterns resurface, checking in on agreed changes, is what turns a feedback moment into genuine development. Without follow-through, the conversation becomes an annual ritual rather than a useful tool.
Collecting feedback at scale with AhaSlides
For L&D teams and HR professionals, individual feedback conversations are only part of the picture. Gathering structured feedback from teams after training sessions, workshops, or performance cycles requires a repeatable system.
AhaSlides lets you run live polls, rating scales, and open Q&A during meetings or training sessions, so feedback is collected while the context is still fresh. Results appear in real time, which means facilitators can adjust on the spot rather than reading a report a week later when the moment has passed.
A practical setup for HR teams: run a short pulse survey at the end of each training module using a 5-point agreement scale ("I can apply today's content to my work this week"). Track scores across cohorts over time to identify which modules consistently underperform, then fix those, not the ones that already work.
The same approach applies to team feedback cycles: anonymous Q&A slides let people raise concerns they wouldn't voice in a group, and word clouds surface patterns across a whole department without requiring anyone to read hundreds of individual responses.
Frequently asked questions
How often should I give feedback to colleagues?
There is no single right frequency, but research consistently points toward more being better than less. A weekly or bi-weekly check-in that includes at least one positive or constructive observation is a reasonable baseline for most teams. The key is regularity: feedback that shows up only during formal reviews is too infrequent to change behavior or build trust.
What should I do if someone reacts defensively to feedback?
A defensive reaction is usually a signal about how the feedback was framed, not proof that it was wrong. If someone pushes back, resist the urge to either back down completely or double down. Instead, ask what part of the observation feels off to them. This shifts the conversation from argument to dialogue and often surfaces context that improves the accuracy of the feedback itself.
Is it better to give feedback in writing or in person?
Written feedback has its place. It creates a record, gives people time to process, and can work well for complex or detailed observations. But for anything constructive, a live conversation is usually better. Tone, intent, and nuance are easier to communicate in person, and the two-way exchange that makes feedback stick is much harder to achieve over email or a messaging platform.
Sources
[1] Peaceful Leaders Academy. 63 employee feedback statistics in 2025. https://peacefulleadersacademy.com/employee-feedback-statistics/
[2] Gallup. Organizations can redefine feedback by including recognition. (2024). https://www.gallup.com/workplace/651812/organizations-redefine-feedback-including-recognition.aspx
[3] ScienceDirect. Sandwich feedback: The empirical evidence of its effectiveness. Teaching and Learning in Medicine. https://www.sciencedirect.com/science/article/abs/pii/S0023969020301429
