Most people have heard the phrase. “Feedback is a gift.”
They nod. They agree. Then they walk into a performance review and deliver feedback in a way that makes the other person defensive for three weeks.
Knowing that feedback matters and knowing how to give feedback are two very different things. In most organizations I work with, the gap between those two is exactly where growth stalls.
The real problem is not the feedback itself
When someone on your team resists feedback, the instinct is to label them “defensive.” When someone shuts down after a correction, we say they “can’t take criticism.” We place the problem entirely on the receiver.
But most resistance to feedback is a response to how the feedback was delivered. It felt like a judgment. It felt personal. It felt like evidence of permanent failure rather than a data point for improvement.
And that is still worth paying attention to. The way you frame a correction shapes everything that comes after it — whether the person improves, whether they trust you more or less, and whether your team builds a culture where honest feedback is normal or quietly feared.
I see this pattern consistently in workshops with leadership teams across the Philippines. The leaders who struggle most with developing their people are often not the ones who give too much feedback. They are the ones who give feedback poorly — or who wait so long to give it that it lands like a surprise attack.
What Otobot taught me about receiving feedback
A while ago, I corrected my AI agent, Otobot, for a mistake it made.
It didn’t resist.
It didn’t take it personally.
It simply accepted the correction, and thanked me so it could improve next time.
Something about that moment stayed with me. Not because AI agents are better than humans — they’re not. But because Otobot’s response described exactly the posture we want from people on a learning team. Separate the correction from the self. See the feedback as information. Move forward.
That posture is hard for humans. It requires psychological safety, trust in the person giving the feedback, and a genuine belief that the correction is aimed at the work, not the worth.
Which means the responsibility for creating that environment lands on us as leaders — before we ever open our mouths to correct someone. You cannot demand that your team receives feedback well if you haven’t first created the conditions where that is safe to do.
Why most feedback fails to land
There are a few patterns I see repeatedly in Filipino organizations, and they have nothing to do with the quality of the people involved.
Feedback delivered too late. The behavior happened three weeks ago. By now the person has moved on, and the correction feels disconnected from anything they can still act on. Timely feedback is more useful than perfect feedback. If you can’t give comprehensive feedback in the moment, give a brief observation and promise a fuller conversation soon.
Feedback that mixes the behavior with the person. “Your report was missing the cost breakdown” is a behavior — it is specific, observable, and fixable. “You are careless with details” is a character label. It may be intended as shorthand, but it lands as a verdict on who the person is. One creates a path to improvement. The other creates shame, and shame makes people defensive, not better.
Feedback with no specifics. “Good job last week” tells someone almost nothing. “The way you handled the client concern in Tuesday’s call — staying calm and redirecting to the actual request — that was exactly the right move” gives the person something they can repeat deliberately. Vague praise is not development. Neither is vague criticism.
Feedback delivered without asking first. Most leaders give feedback as a monologue. They have observed something, formed a conclusion, and now they are explaining the conclusion to the person. What is often missing is the question: “What was going on when you put this together?” or “Walk me through your thinking on this section.” There is almost always context you don’t have. Asking before prescribing shows respect, surfaces that context, and often changes what advice is actually useful.
How to give feedback that actually lands
Here is what works, based on the deployments and leadership workshops I run through PAIBA.
Start with intent, not observation. Before naming what went wrong, say why you are saying it. “I want to share something because I think it will help you grow in this role” lands differently than jumping straight into the correction. It signals that what follows is an investment in the person, not an evaluation of their worth. Thirty seconds of framing changes everything about how the rest of the conversation is received.
Separate the behavior from the person. Make your correction about what happened, not about who the person is. Behaviors are situational and changeable. Character labels are not. Every correction you give should be specific enough that the person can do something about it this week.
Make it specific and recent. Feedback that refers to “a pattern I’ve been seeing” without a concrete example feels like a verdict that has been building in secret. The more specific and recent the example, the easier it is for the person to understand, accept, and act on. If the event was more than two weeks ago and you haven’t raised it yet, consider whether a pattern-level conversation is now more appropriate than relitigating a single incident.
Ask before prescribing. After naming the behavior, ask what happened. “What was going on when you put this together?” Often there is context you don’t have — a competing deadline, an unclear brief, a gap in tools or training. Asking first shows respect and surfaces information that may change your recommendation entirely.
Close with confidence, not caution. Too many feedback conversations end with a hedge. “Just something to think about.” “I might be wrong.” “It’s up to you.” The person walks away unsure whether the feedback was serious. End with something direct: “I know you can fix this. Let me know if you want to think through how.” Clear, warm, and it closes on belief in the person.
The leader who waits to be perfect
One pattern I see especially in Filipino organizations: leaders who hold back on giving feedback because they are not sure they are doing it right.
They worry about saying the wrong thing. They fear damaging the relationship. So they say nothing — and the team member keeps repeating the same mistake, wondering why no one is telling them anything useful.
Here is what I remind teams in our PAIBA workshops: no one is great at something on Day 1. That applies to the people you are developing. It also applies to you as a leader learning to give feedback well. You will get better at it through consistent practice and honest reflection after each conversation.
The alternative — waiting until you are perfect — just means your team grows slower. And that is a cost you pay every week you wait.
Growth happens on both sides of a well-delivered correction. The receiver improves. The leader improves. And the relationship strengthens, because the person now has evidence that you care enough to be honest with them.
Where to start this week
Pick one person on your team who would benefit from a piece of feedback you have been holding back.
Before the conversation, write down three things: the specific behavior you observed, the impact it had, and what you want them to do differently. That preparation alone changes the conversation. You move from reacting to leading.
Then, open with intent. Give the specific behavior. Ask what was going on. Close with confidence in their ability to improve.
One conversation, done well, builds more trust than a year of comfortable silence.
Frequently Asked Questions
What does “feedback is a gift” actually mean in a leadership context?
The phrase means that honest feedback — even when it is difficult to hear — gives the receiver something valuable: information they can use to improve. In practice, leaders who treat feedback as a gift stop withholding it out of discomfort and start treating it as a responsibility they owe to the people they develop.
Why do employees resist feedback, even when it is meant to help?
Most resistance to feedback is a reaction to how it was delivered, not to the content itself. When feedback feels like a judgment of character rather than an observation about behavior, people defend their identity instead of hearing the message. Delivering feedback with specifics, good timing, and genuine care for the person dramatically reduces resistance.
How do you give feedback to someone who takes everything personally?
Start by separating the behavior from the person in every correction you give. Use specific examples with observable behaviors, not character descriptions. Open the conversation by stating your intent clearly. Over time, consistent feedback delivered this way builds psychological safety — the person begins to trust that your corrections are investments, not attacks.
How soon after an incident should you give feedback?
As soon as possible, while the example is still fresh and actionable. If the event was recent, a brief same-day observation followed by a fuller conversation works well. If more than two weeks have passed, a pattern-level conversation is usually more useful than revisiting a single incident. Late feedback often lands as an ambush.
What is the difference between constructive feedback and criticism?
Constructive feedback is specific, behavior-focused, and oriented toward improvement. It names what happened, explains the impact, and opens a path to doing it differently. Criticism tends to be evaluative, character-focused, and backward-looking. The practical test: after hearing your feedback, does the person know exactly what to do next? If yes, it was constructive. If not, it was criticism.
How do leaders build a culture where feedback is welcomed, not feared?
By modeling it themselves, both giving and receiving feedback openly. When leaders ask for honest input from their team and respond without defensiveness, they signal that feedback flows in all directions. Pairing that with consistent, well-delivered corrections over time builds a team environment where honest feedback is expected, normalized, and valued.
Have you had a feedback conversation that changed how someone on your team performed? I would be curious to hear what made the difference.
