← All articlesFeedback

How to give hard feedback without turning it into a fight

There's a conversation you've been putting off for three weeks. The person delivers, but something's off: deadlines slipping, pushback on reviews, visible burnout. You know you have to say it — but every time there's a reason to postpone. Sound familiar?

The catch isn't that you don't know what to say. It's that every script in your head ends in either resentment or a polite nod that changes nothing.

Why "I'll just say it straight" doesn't work

When you say "you keep missing deadlines," the person hears not a fact but a verdict on who they are. Defenses go up: excuses, counter-attack, or a silent "yeah" with nothing behind it. Honesty without structure isn't courage — it's just dumping your own discomfort on someone else.

Separate the behavior from the person

A strong engineer instinctively judges: good/bad, right/wrong. But feedback isn't a verdict — it's about a specific behavior in a specific situation.

  • not "you're irresponsible" → but "yesterday the release shipped without your part, and I heard it from QA";
  • not "you're toxic in reviews" → but "in the last review three comments read as attacks, and the author stopped replying."

Behavior can change. A personality can't — and trying to change it lands as an attack.

Fact → impact → request

A working shape for a short talk:

  1. Fact — what exactly happened, no interpretation.
  2. Impact — why it matters: for the team, the product, you.
  3. Request — what you expect next, concrete and checkable.

"The task sat three days with no update (fact). I couldn't put the forecast together and let the next team down (impact). So let's agree: blocked more than a day, you ping me right away (request)."

Let them leave with a plan, not with guilt

Worst outcome — they walk away crushed and demotivated. Best — they walk away with a clear next step. Ask: "What's getting in your way?" and "What do you need from me?" Often behind a "missed deadline" isn't laziness but tangled priorities or fear of admitting they're stuck.

Bottom line — don't drag it out and don't fear these talks. It's a skill, and you only build it live. Shame is, every one of those is a real human and a single take.