20+ examples of feedback for colleagues (and how to deliver them)
Most people know that feedback matters. Far fewer know what good feedback actually sounds like in practice. Generic praise ("great job!") and vague criticism ("you need to improve your communication") both fall flat — one because it says nothing specific, the other because it gives nowhere to go.
This guide skips the theory and gets to the language. Below are 20+ ready-to-use examples of feedback for colleagues across common workplace scenarios, plus the delivery principles that make feedback land 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]. That gap shows up in the numbers: employees who receive regular, high-quality feedback are 2.5 times more likely to be engaged than those who don't [1]. Gallup research also found that employees who received strong recognition were 45% less likely to leave their jobs between 2022 and 2024 [2].
For managers and HR professionals, that math is straightforward: a consistent feedback habit reduces turnover, lifts engagement, and costs nothing but time.
Examples of feedback for hard work
Recognizing effort specifically — not just outcomes — tells people that the process matters, not just the result.
- "You worked through three revision rounds on the proposal without losing quality or composure. That reliability is what made the deadline achievable. Thank you."
- "I'm not sure the team would have shipped on time without you picking up those extra tasks in the final week. That kind of support is exactly what holds a project together."
- "The way you approached the product launch — moving fast without cutting corners — set the tone for the whole team. That's worth calling out."
- "You took the initiative on the client research before anyone asked. It changed how we framed the whole pitch. That's the kind of ownership that makes a real difference."
Examples of feedback for teamwork
Team-focused feedback works best when it names the specific behavior and the effect it had on others.
- "You always make space for people to contribute in meetings, even when the conversation is moving fast. That habit changes how the team works together."
- "When the customer call got difficult today, you stayed calm and found a solution that satisfied them. That composure keeps the team's reputation intact."
- "Covering for Kai while he was out wasn't in your job description, but you did it anyway and did it well. The team noticed, and it mattered."
- "You brought two departments together on the Q3 initiative when that collaboration wasn't happening naturally. The outcome speaks for itself."
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 presentation translated a complicated technical architecture into something the client could act on. That communication skill is genuinely rare and worth developing further."
- "The way you led the team through the scope change — keeping people focused without dismissing their concerns — showed real leadership judgment."
- "Your ability to generate options under pressure has saved several projects this year. That creative thinking is something the team now relies on."
- "You spotted the data discrepancy that everyone else had missed for two weeks. That level of attention to detail has real value for the team's credibility."
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.
- "You have a way of making difficult conversations feel safe. The discussion you facilitated last week could have gone badly; instead, it produced a real decision. That matters."
- "Your optimism when the project hit setbacks in March kept morale from sliding. It's easy to underestimate how much that steadiness affects the team."
- "People come to you with problems because they feel heard. That quality makes you a more effective colleague than most job descriptions would ever capture."
- "Your commitment to getting better is visible in the work itself. The difference between your writing from six months ago and now is measurable."
給同事的建設性回饋範例
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.
On interrupting in meetings:
"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?"
On working in isolation:
"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."
On vague presentations:
"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."
On missed deadlines:
"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."
On burnout risk:
"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?"
On time management:
"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."
On passive presentations:
"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."
On unclear project organization:
"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.
具體且及時
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.
Focus 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.
Reconsider the sandwich method
The positive-negative-positive structure ("feedback sandwich") 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.
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.
常見的錯誤，以避免
Even well-intentioned feedback can miss the mark. These are the patterns that consistently get in the way.
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 feedback delivered months later in a structured document.
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 the question: what specifically should this person start, stop, or keep doing?
Delivering constructive feedback in public. 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.
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, or 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.
常見問題
How often should managers 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 specific observation — positive or constructive — 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 if someone reacts badly 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 written feedback as effective as face-to-face feedback?
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.
來源
[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
