When feedback sounds kind but lands badly
Practical scripts for giving feedback that lands: what to avoid, what to say instead, and examples for missed deadlines, tone, and quality issues.
People say they want "direct feedback" and then flinch when they get it. This is not hypocrisy. It's basic human behaviour.
The real problem is that a lot of feedback isn't actually direct. It's vague judgement wearing a serious tone. That is what lands as harsh.
The two failure modes
Most feedback conversations fail in one of two ways:
- Soft and unclear: lots of cushioning, no message. Everyone leaves uneasy and nothing changes.
- Clear but personal: "You're careless" / "Your attitude" / "You don't care". Plenty of heat, not much light.
The goal is a third thing: specific, owned, future-focused.
Harsh isn't "honest". Harsh is usually "unspecific".
The fastest way to make feedback feel hostile is to talk about the person rather than the behaviour.
"You're disorganised" is a personality verdict. People defend their identity. It's their job.
"The draft landed after the review window" is a fact about a Tuesday. It's much harder to argue with a Tuesday.
A structure that keeps you out of trouble
The easiest model to remember is SBI: Situation, Behaviour, Impact.
CCL (Center for Creative Leadership) recommends SBI because it keeps feedback grounded in specifics, and you can extend it with an inquiry about intent (SBII) when you want the conversation to be two-way. (source)
- Situation: the moment.
- Behaviour: what they did (observable).
- Impact: what it caused (real, not moral).
- Intent (optional): "What were you aiming for there?"
- Next time: the concrete request.
Shortcut: "When X happened, the impact was Y. Next time, can we do Z?"
Examples (with the bits people usually get wrong)
Missed deadline
Avoid:
You always leave things to the last minute.
Try:
On Tuesday the draft landed after the review window, so we shipped without a proper check.
The impact is we miss issues when they're cheap to fix.
Next time, can you send a rough version 24 hours earlier so we can review it properly?If they get defensive, don't argue. Ask intent.
What got in the way this time? Was it time, clarity, or competing work?Tone in messages (the delicate one)
Avoid:
Your tone is rude.
Try:
In the thread with Support, the line "This is obvious" landed sharper than I think you intended.
The impact is it made the back-and-forth harder and slowed us down.
Could you rephrase those bits to focus on the next step, not the mistake?Note the move: you don't diagnose their personality. You name the impact on the work.
Quality / accuracy
Avoid:
This work is sloppy.
Try:
I found three places where the numbers don't match the source doc.
The impact is people stop trusting the analysis.
For the next version, can you run a quick self-check before sending it over? I can share the checklist I use.Meeting behaviour (interrupting, dominating, derailing)
This is where people get moralistic. Don't.
In today's 11am meeting, you jumped in while Priya was still explaining the issue.
The impact is the team loses key context and people stop offering ideas.
Next time, can you wait until someone's finished, then ask your question?Two small upgrades that change everything
- One topic per conversation. If you have four points, pick the one that matters most today.
- End with an agreement. "So next time we'll do X. I'll do Y."
When it still lands badly
Sometimes you do everything "right" and the other person still gets defensive. That does not mean you were harsh. It means you touched a nerve.
Keep your tone calm, keep the content specific, and invite intent: Help me understand what you heard.