Get 1 month of Premium free

Use the code at checkout

00Days
00Hours
00Mins
00Secs
Claim 1 month free

BlogTeam Management

How to Give Feedback That Doesn't Damage Trust

Give feedback close to the event, in private, about a specific observable behaviour rather than the person. Say what you saw, what the effect was, and what you want instead, then stop talking and let them respond. Feedback saved up for a review is about the past, not the work.

Timing does most of the work

The single biggest determinant of whether feedback lands is how long you waited.

Feedback given a day after the event is about a specific thing that both people remember. The same feedback delivered six weeks later has become a general statement about the person, because the specifics have faded and only the impression remains. That is the version people find hard to hear, and it is entirely a product of the delay.

The rule

If it is worth saying in a performance review, it was worth saying in the week it happened. Nothing in a review should be new information.

The practical version: when you notice something worth correcting, decide in that moment whether you will say it in the next two days. If the answer is no, decide that you are letting it go, and actually let it go. What causes damage is the third option, where it neither gets said nor gets dropped, and accumulates.

The structure

Three parts, then silence. It takes under a minute.

  1. What you observed

    A specific, observable thing. "In the client call on Tuesday you answered the pricing question before Sam finished explaining the requirement."

    Not "you interrupt people". The first is a fact that can be discussed. The second is a character description, and the only available responses to it are agreement or defence.

    Specific event, not a pattern
  2. The effect it had

    What followed from it. "The client did not get to finish, and we ended up quoting for the wrong scope."

    The effect is what makes feedback worth acting on. Without it you are expressing a preference, and people are entitled to weigh your preference against their own.

    Effect on the work, not on your feelings
  3. What you want instead

    Concrete and future-facing. "In client calls, let them finish the requirement before we talk about price."

    Then stop. The instinct is to soften it with a paragraph, and the softening is what makes the message ambiguous.

    One sentence, then stop talking

The silence after the third part is not a stylistic flourish. It is what turns feedback from a delivery into a conversation, and it is where you find out whether there was context you did not have.

Phrasings that quietly make it worse

Instead ofSay
"You always...""On Tuesday, in the client call..."
"People are saying...""I noticed..." or name the person, with their agreement
"I need you to be more proactive""When X happens, I want you to do Y without asking"
"Not a big deal, but..."Say it plainly, or do not say it
"I'm just being honest"Nothing. This phrase only ever precedes something unkind
"You did great, but..."Split it. Praise separately, correction separately

The middle two are the most common. "Not a big deal, but" tells the person the feedback does not matter, and then they are confused when it comes up again. And vague requests like "be more proactive" cannot be acted on, because the person already believes they are proactive, by their own definition of it.

Positive feedback is not the easy one

Most managers give less useful positive feedback than critical feedback, because they treat it as morale management rather than as information.

"Great job on that" tells someone nothing repeatable. The useful version has the same shape as the critical version: what you observed, what effect it had, and that you want more of it. "You sent the client a summary within an hour of the call, and they signed the next day. Do that on every call."

That is a person who now knows exactly which behaviour to repeat. The vague version leaves them guessing which part of the week you liked.

What to do when they push back

Disagreement is a normal response, not a failure of the conversation.

If they have context you did not have, say so and update. Nothing costs a manager more credibility than defending feedback that has been shown to be based on a misreading.

If they disagree with your interpretation but you still hold it, say both things: that you have heard their view, and that you still want the change. You do not need agreement to ask for a behaviour, and pretending you have reached agreement when you have not is how the same conversation happens again in a month.

If they get upset, hold the silence rather than filling it. The urge to reassure is strong and it usually results in the substance being withdrawn. Acknowledge that it is difficult, wait, then ask how they see it.

One last thing worth checking on yourself. If you find that you dread giving feedback to one specific person, that is usually a signal that too much has accumulated. The fix is not a bigger conversation. It is starting to say small things again, in the week they happen, until the backlog stops existing.

Frequently asked questions

How soon after something happens should I give feedback?
Within a day or two for most things, and the same day if it is significant. The value decays quickly because memory of the specifics decays quickly, and feedback without specifics is just an opinion about the person.
Should feedback be given in private or in public?
Critical feedback always in private. Praise usually in public, unless you know the person finds public attention uncomfortable, in which case saying so privately is worth more than the public version.
Is the feedback sandwich a good technique?
No. Wrapping criticism in praise teaches people that compliments are a warning sign, and the message in the middle is the part that gets discounted. Say the positive thing when it is true and separately from the correction.
What if the person gets upset?
Let them, without retreating from the substance or rushing to reassure. Acknowledge that it is hard to hear, stay quiet for a moment, and then ask how they see it. Withdrawing the feedback because of the reaction is what teaches people that a strong reaction ends the conversation.
How do I give feedback to someone more senior than me?
Same structure, with more emphasis on the effect and less on what you want instead. Describe what you observed and the impact it had on your work, then ask rather than instruct. Most senior people receive far less of this than they need.
Danish Khan

Danish Khan

CEO & Founder, Siela

Danish Khan is the CEO and founder of Siela, an AI-native workspace where teams and AI agents run CRM, meetings, tasks, and daily work together on one shared context layer.

Connect on LinkedIn

Published