You're replaying the meeting in your head because one moment keeps snagging.
They cut someone off. Or they shipped something half-checked. Or they replied in a thread with the conversational warmth of a parking ticket.
You open Slack to message them and your brain offers you two drafts:
Draft 1:
Hey!! Quick thing... just a tiny note!! Totally fine!!
Draft 2:
Your tone was not acceptable. Don't do that again.One is so padded it barely contains information. The other is so sharp it becomes the story.
The goal is neither. The goal is calm clarity: specific behaviour, real impact, and a clean next step.
What "harsh" usually is
People think harsh feedback is "honesty". Most of the time it's something else: vague judgement wearing a serious tone.
"You're careless" 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.
The three-part line that keeps you out of trouble
You can remember a lot of models. In the moment, you need something you can actually say.
- Observation: what happened (observable, specific).
- Impact: what it caused (time, risk, trust, confusion).
- Request: what you want next time (concrete).
Shortcut: "When X happened, the impact was Y. Next time, can we do Z?"
If you want the slightly-more-formal version, this overlaps with SBI (Situation, Behaviour, Impact). CCL 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)
Scripts that feel human (not HR)
The point of scripts isn't to sound scripted. It's to avoid the two failure modes: cushioning until nothing is said, or snapping and making it personal.
Missed deadline
You always leave things to the last minute.
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?It criticises the outcome, not the person. It also gives them a specific behaviour to succeed at, instead of a vague instruction to "be better".
If they get defensive, don't argue. Ask intent.
What got in the way this time - time, clarity, or competing work?It gives them a way to save face without escaping responsibility. You're solving the system, not prosecuting the person.
Tone in messages (the delicate one)
Your tone is rude.
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.
Next time, can you rephrase those bits to focus on the next step, not the mistake?You give them intent ("I think you didn't mean it") while still naming impact. That lowers defensiveness without letting it slide.
The first time you try new phrasing shouldn't be in a high-stakes moment.
TalkCraft is built for reps: scenarios, choices, coach notes, repeat.
Quality / accuracy
This work is sloppy.
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.It names a standard (accuracy) without making it a moral lecture. It also offers help without turning it into a rescue.
Meeting behaviour (interrupting, dominating, derailing)
This is where people get moralistic. Don't. Moralising makes people fight you on values instead of changing behaviour.
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?You're not telling them who they are. You're telling them what happened and what to do differently.
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."
If it still lands badly
Sometimes you do everything "right" and the other person still gets defensive. That does not automatically 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.
Three defensive reactions (and what to say)
You don't need a debate. You need the conversation to stay in the "behaviour and next time" lane.
1) "You're overreacting."
I'm not trying to make this dramatic.
I'm pointing out the impact so we can avoid it next time.
Can we agree on [specific change]?2) "So you think I'm bad at my job?"
No - I'm talking about this specific moment.
I know you care about doing good work.
Next time, can we [request]?3) Silence / shutdown
We don't have to solve it right now.
Can you think about it and we'll check in tomorrow? The one thing I need is [request].This keeps the conversation from turning into a pressure test. You leave space, but you do not leave the actual request blurry.
Private vs public (quick rule)
If the feedback could embarrass them, do it privately. If it's a team norm that's harming others, you can address the pattern in public without naming the person.
Your goal is behaviour change, not a display of authority.
Try this today (60 seconds)
Write one sentence for each:
- Observation: the Tuesday-level fact.
- Impact: what it caused.
- Request: what "good" looks like next time.
If the feedback would still make sense with the person's name swapped out for anyone else, it is probably too vague. Keep the real moment. Lose the generic lecture.
If you want to get good at feedback, you need repetition. TalkCraft gives you short, private reps and coach notes, without turning your team into a practice lab.
If feedback turns into a mess, this next helps: repairing trust after a mistake at work.