Conflict at Work: Scripts for Giving Tough Feedback

By

Quick Answer

Use SBI + next-step requests: Situation, Behavior, Impact, then one clear expectation.

You have been putting it off for a week. Someone on your team keeps missing deadlines, or talks over people in meetings, or shipped work that was not up to standard — and you know you have to say something. But every time you rehearse it, it comes out either too soft to matter or harsh enough to start a fight. So you say nothing, and the problem compounds.

Tough feedback fails when it is vague, delayed, or emotional. It works when it is specific, timely, and calm. The difference is not how blunt you are — it is whether you are running a structure or winging it. Here is the structure.

Use SBI: Situation, Behavior, Impact

The most reliable feedback script is SBI, plus a clear request. It keeps you on observable facts instead of character attacks, which is exactly what keeps the conversation from turning into a fight:

  • Situation: when and where it happened. "In yesterday's client call..."
  • Behavior: the specific, observable action — not your interpretation of it. "...you cut Maria off twice before she finished."
  • Impact: the concrete business or team consequence. "...and she stopped contributing for the rest of the meeting, so we lost her read on the risk."
  • Request: one clear change for next time. "Going forward, let people finish before you jump in."

Separate the Behavior From the Person

"You were unprofessional" is a verdict on who someone is, and it triggers instant defensiveness. "You interrupted Maria twice" is a fact about what someone did, and it can actually be acted on. This is the core principle behind giving constructive feedback without starting a war: attack the behavior, never the person. Labels make people defend their identity; observations let them fix an action.

Deliver It Calm, Private, and Soon

  • Private, always. Public correction humiliates, and humiliation kills the message — all they remember is the audience.
  • Soon, while it is fresh. Feedback two months late feels like an ambush and an injustice.
  • Calm. If you are still angry, wait until you are regulated. Emotion in your delivery becomes the story instead of the behavior.

If the feedback is genuinely hard news — a missed promotion, a project pulled — the same directness applies, but the stakes are higher; delivering bad news without losing trust covers that harder case. And if the underlying issue is someone repeatedly crossing a line, the conversation may need to shift toward setting boundaries rather than one-off feedback.

When They Push Back

Sometimes a clean, fair piece of feedback still meets resistance or disagreement. Your job is not to win the argument — it is to stay on the behavior and the impact without escalating. The skill of holding your position warmly while someone disagrees with you is its own thing, covered in how to disagree without damaging the relationship.

How to Practice

Tough feedback is hard precisely because it happens live, with a real person who might get upset — and most managers get only a handful of reps a year. With UnmuteNow you can rehearse the whole conversation against an AI that reacts like a real, slightly defensive report, and get scored on whether you stayed specific and calm or slid into vagueness and blame. Run it a few times and the real conversation stops being the thing you dread.

Kindness without clarity is just confusion wearing a nice tone.

Practice This Next

Run a 10-minute rehearsal where the other person asks one predictable question, one follow-up, and one pressure question. Answer out loud, then repeat the weakest answer once more with a shorter opening and one stronger example.

Live practice scenario

Scenario: you are asked about tough feedback in a high-pressure career conversation. Give the short answer first, support it with one specific example, then handle a follow-up without rambling.

Useful lines to rehearse

  • Opening: "The short version is this: [point]. The example that proves it is [specific moment]."
  • Bridge: "There are two ways to answer that. The one most relevant here is..."
  • Recovery: "Let me tighten that answer. What matters most is..."
  • Self-review: "The part of my tough feedback answer that sounded clearest was [specific sentence], and the part I need to tighten is [specific sentence]."
  • Second attempt: "Let me answer that again with less setup: [one-sentence point], [one example], [one next step]."

Self-check before the real conversation

  • Lead with the answer before the background.
  • Use one concrete example instead of three vague claims.
  • Pause before the final sentence so it lands cleanly.
  • Name the exact tough feedback moment you are practicing before you start.
  • Repeat the weakest 30 seconds immediately while the mistake is fresh.
  • Write down one phrase that worked and reuse it in the next session.

Weak version to avoid

Weak version: "I am a hard worker and I just really care about doing a good job."

Stronger version to practice

Stronger version: "For tough feedback, the clearest example is this situation, the action I took, and the measurable result that followed."

What the coach should catch

  • Specificity: Strong signal: Names the role, situation, action, and result. Watch out: Relies on traits like hardworking, passionate, or fast learner without proof.
  • Structure: Strong signal: Starts with the answer, then gives evidence. Watch out: Begins with background and reaches the point late.
  • Pressure control: Strong signal: Pauses before answering and recovers cleanly. Watch out: Rushes, apologizes, or fills silence with disclaimers.
  • Next step: Strong signal: Ends with confidence or a thoughtful question. Watch out: Trails off with "so yeah" or repeats the same claim.
  • Replay improvement: Strong signal: The second attempt at tough feedback is shorter, clearer, and more grounded in a real example. Watch out: The second attempt changes words but keeps the same vague structure.
  • Transfer to real life: Strong signal: The final answer includes a sentence you could use unchanged in the actual conversation. Watch out: The practice stays theoretical and never produces language you would actually say.

Field notes

  • The fastest career-communication improvement usually comes from cutting the first 20 seconds of setup. Hiring managers and leaders need the point before the context.
  • A strong answer has one named situation, one action you personally took, and one result that can be checked.
  • If the question surprises you, a calm bridge phrase is better than an instant answer that wanders.
  • For this article, the practice target is not to sound polished about tough feedback. The target is to make the next listener's job easier: what happened, why it matters, and what should happen next.
  • A useful replay test: compare your first answer with your second answer. The second version should usually be shorter, more specific, and less padded with disclaimers.
  • If you cannot identify the exact sentence you want to improve, replay the moment where your pace speeds up. That is usually where the real pressure point sits.
  • Do not judge the whole session by how nervous you felt. Judge the observable behaviors: did you answer the question, use a concrete example, pause cleanly, and land the next step?

7-day practice plan

  1. Day 1: Record the answer once without notes and mark every filler word.
  2. Day 2: Rewrite the opening sentence so the point appears first.
  3. Day 3: Add one measurable result or concrete detail.
  4. Day 4: Practice the answer after a skeptical follow-up.
  5. Day 5: Cut the answer by 25% without losing the proof.
  6. Day 6: Run a full mock conversation and review pacing.
  7. Day 7: Rehearse the final version twice, then stop polishing.

Practice this conversation

Keep learning

References and further reading

Related Playbooks