Feedback good examples for high-performing teams

Good feedback names the specific behaviour, explains the impact it had, and gives a clear next step, delivered close to the event. "Great work on the presentation" does none of that. The examples below show what the specific version sounds like for praise, constructive input and peer-to-peer feedback, ready to adapt for your team.

Last reviewed July 2026.

This guide covers the ongoing feedback that keeps a team performing: manager to team member, and peer to peer. It is not about interview or candidate feedback, which is a different conversation with different rules.

Why generic feedback fails

A performance review that says "good job" or "needs improvement" without context changes nothing. Research suggests roughly 74% of employees feel in the dark about how they are actually performing because the feedback they receive is too vague. People end up career sleepwalking, working hard with no clear sense of whether it is the right work.

The fix is a simple structure you can apply every time: the specific behaviour you observed, the impact it had on the team, the project or the client, and what to do next. Every example below follows it.

Positive feedback examples

Positive feedback is the most underused tool in management. If things are going well, most managers say nothing, which means good habits go unanchored. Swap the generic praise for something the person can repeat:

"I noticed how you handled the difficult questions during this morning's client presentation. Staying calm and giving data-backed answers built real trust with the stakeholders. That is exactly the customer focus we want to be known for."

"The handover notes you wrote before your leave meant the team didn't miss a single deadline while you were out. That is the standard I'd love everyone to work to."

"You spotted the pricing error before the proposal went out. That save protected the client relationship and saved us an awkward correction. Thank you for checking the detail nobody else did."

Each one tells the person exactly what they did, why it mattered, and links the behaviour to something bigger than the task.

Constructive feedback examples

Constructive feedback is where most managers get nervous, and the fear of conflict leads to sugarcoating that only causes confusion. Focus on the behaviour and its impact, not the person. Coach, don't judge:

"In yesterday's team meeting I noticed you interrupted Sarah several times while she was sharing her data. We didn't get to hear her full analysis, which slowed our decision. Next time, could you hold your points until she has finished?"

"The last two status reports went out with figures that hadn't been checked against the source data. Finance flagged both, and it cost us credibility with them. Can we add a five-minute check step before anything goes out?"

"When the project files came through at 9pm, I had to stay back to finish my part. Can we agree on a 3pm handoff for tomorrow so we both stay on track?"

The pattern holds even in that last example, which is a peer speaking, not a manager. Specific event, honest impact, clear request.

Peer-to-peer feedback examples

Feedback should not only flow downhill. Peer feedback builds trust and psychological safety, but colleagues often hesitate for fear of overstepping. Give them a frame:

"I really appreciated your help with the spreadsheet formatting this morning. Your attention to detail saved me two hours of manual work, and it meant the report reached the board on time."

"Your walkthrough of the new process saved me from repeating the mistakes you'd already found. If you ran that for the whole team, I reckon everyone would move faster."

Respectful and direct at the same time. That combination is what makes peer feedback feel safe enough to repeat.

Tailor the delivery to the person

The same message lands differently depending on who receives it. Everyone has a dominant work preference, which we call their work personality. A Doer wants the feedback short and practical. An Evaluator wants the reasoning and the evidence behind it. Neither is wrong; delivering feedback in the recipient's natural style makes it far more likely to be heard and acted on.

The same logic applies at team level. When you know your actual culture, positive feedback becomes a way of reinforcing the specific behaviours your business needs, not just being nice. Compono Engage maps that culture so your feedback and your values point in the same direction.

The rules that make any example work

• Be specific: describe the exact behaviour you observed, not a vague adjective.
• Show the impact: explain how the action affected the team, the project or the client.
• Make it actionable: give a clear suggestion for next time.
• Keep it timely: deliver feedback close to the event, once emotions are calm.
• Match the delivery: use work personality insights to communicate in a way the recipient hears.

Frequently asked questions

What makes a good feedback example?

It names a specific behaviour, explains the impact that behaviour had, and offers a clear next step. If any of the three is missing, the feedback is unlikely to change anything.

How often should teams give feedback?

Continuously, not just at review time. Feedback delivered close to the event, while the detail is fresh and emotions are calm, is far more effective than saving observations for a quarterly or annual conversation.

How do I give constructive feedback without causing conflict?

Focus on the behaviour and its impact rather than the person's character, then end with a specific request. Sugarcoating creates confusion; a clear, respectful description of what happened and what to change creates improvement.

Should feedback change based on personality?

The message should stay honest, but the delivery should flex. A Doer responds to short, practical feedback while an Evaluator wants the evidence behind it. Matching delivery to work personality makes feedback more likely to be acted on.