Critical feedback: how to give it without damaging the working relationship
Echipa HR 365 · reviewed 2026-09-08 · 5 min read
Critical feedback works when it is about an observable fact and its effect, and fails when it is about the person. The difference is not politeness: “the report was late three times and the team was left waiting” can be discussed, “you are disorganised” can only be denied.
Why it usually fails
Three causes, in order of frequency. First: it is given too late, once five situations have accumulated, and the person receives a list instead of an observation. Second: it is given vaguely, so as not to upset, and the other person leaves without knowing what to change. Third: it is given in public, even in gentle forms, and then the content stops mattering entirely.
The four-step structure
The order that works
- The fact — what happened, concretely, with a date: “Tuesday’s report arrived on Thursday”
- The effect — what that produced for somebody else: “the team postponed the meeting and worked from old figures”
- The question — “what happened?” — and then stop talking; this is usually where you learn something you did not know
- The agreement — what changes next time, said by them, not by you
The third step is missing from most of these conversations and is the one that turns them from an announcement into a discussion. Often the answer changes the situation entirely: they were waiting for data from someone else, or working on an emergency you did not know about.
What you do not say
- Adjectives about the person: disorganised, careless, superficial. They cannot be verified and cannot be corrected.
- “Everyone has noticed.” It turns a discussion into a tribunal and cannot be confirmed.
- “I do not want to criticise you, but…” It cancels everything that follows and sounds insincere.
- Comparisons with a colleague. They produce resentment towards the colleague, not change.
- Five problems at once. One is retained, usually the last, and that is not the important one.
About the feedback “sandwich”
The classic method — a compliment, the criticism, another compliment — has a practical problem: after the second or third use, any compliment starts being read as a preamble to something unpleasant. You end up unable to praise anyone without alarming them.
The alternative is not harshness, it is separation: praise is given when deserved, on its own; critical observations are given while fresh, on their own. Both gain in credibility.
Two model conversations
I want to talk about Tuesday’s report — it arrived on Thursday morning. Wednesday’s meeting ran on last week’s figures, and two decisions were postponed. What happened?
A repeated delay — fact, effect, question
In yesterday’s meeting, when Ana proposed the two-supplier option, you said it “makes no sense and we have been through this”. Ana said nothing for the rest of the meeting. I want to understand how you saw that moment.
A behaviour in the team — described, not labelled
The second is the hardest category and it is built on facts too. What was said, what happened afterwards. No “you were aggressive” — which is an interpretation the person will contest, and rightly, because that is not what they experienced.
When and where
As close to the event as possible — the same day or the next. After a week, the details are gone and the discussion becomes about who remembers correctly. Never in front of anyone else, never on a Friday at the end of the day, and never in writing if it could be misread.
What if they react defensively?
Go back to the fact rather than the interpretation: “I am not saying you did not care, I am saying the report arrived on Thursday and that produced X”. Defensiveness almost always attaches to the interpretation, not the fact.
Should I record the conversation somewhere?
The point of agreement, yes — what was decided would change. Not the emotional content. At the next check-in, that is the only thing you need.
What if nothing changes after three conversations?
You change the nature of the conversation and say so explicitly: this is no longer feedback, it is a discussion about expectations and consequences. Repeating the same conversation four times tells the person that nothing follows.
Where to start
Take the last critical observation you gave and check whether it had a dated fact and an effect. If it had only an adjective, you have found the reason nothing changed.
Next time, stop after the question and let the silence sit. It is the most uncomfortable part and the one that produces the most.
The other half: the feedback that never gets given
In a team where only critical feedback is given, even that becomes harder to receive — because every conversation the manager initiates starts to mean a problem. Appreciation has the same requirement as criticism: it must be about a concrete fact, not about the person.
| Vague | Useful |
|---|---|
| You did a good job | You anticipated the delivery problem and told the client before they asked |
| You are very reliable | You took over the report when Ana was away and nobody noticed a difference |
| I appreciate your commitment | You stayed to finish with the team on Thursday when you could have left — that saved the deadline |
The right-hand column has an additional effect: it tells the person what to repeat. “Good job” cannot be repeated deliberately; “you told them before they asked” can.
One-to-one notes, with the points of agreement tracked
What was agreed stays visible to both of you and reappears at the next meeting — so the third conversation on the same subject starts from what was agreed rather than from zero.
You can create an account in a few minutes and use every module for 7 days, no card required.