How to Give Difficult Feedback to an Employee: Script

Razen’s difficult-feedback script uses observable behavior, work impact, employee context and one agreed next action to make corrective feedback clear and two-way. SurveyMonkey’s four-step process recommends delivering corrective feedback within a few days, agreeing one change and one deadline, then checking progress within 1–2 weeks, while Gallup supports coaching conversations.

What should you say when giving difficult feedback to a direct report?

A Situation-Behavior-Impact structure can help a manager give feedback by linking one event, one observable action, and its work impact. Then it asks for context. A prepare–frame–deliver–follow-up process can help organize a complete feedback script:

“I want to discuss yesterday’s client call because you interrupted Jamie twice while she presented the numbers. The client then asked to speak to her manager, which made the call harder to recover. How did you experience that moment?”

Pause. Let the employee finish. Do not fill the silence or argue with the first explanation. Your aim is to understand what happened, not to force an apology.

Then state the expectation:

“In the next client call, let Jamie finish before you respond, and if you disagree, write down the point and raise it after she finishes.”

Ask one practical closing question:

“Is there anything you need to make that workable?”

A four-part conversation model describes the exchange as stating the behaviour, stating the impact, pausing for a response, and ending with a specific next step. Feedback-practice guidance can help managers prepare both the opening and the exchange that follows.

Keep the first conversation narrow. One behaviour gives the employee something they can change and gives you something you can observe later. Do not turn the meeting into a verdict on their character, commitment or attitude.

Gallup recommends concise, future-focused and collaborative feedback. The employee should do more of the talking. Gallup’s coaching guidance supports asking for the employee’s account before deciding what the explanation means.

The target is not agreement. It is a clear behaviour change. The employee can disagree with your interpretation and still understand what must happen in the next client call.

How do you prepare difficult feedback in 15 minutes?

Gallup’s hard-skills/soft-skills feedback matrix offers a way to classify an issue as objective or subjective before choosing how to raise it. (Give Employees the Right Kind of Feedback at the Right Time)

The workflow below is a publication recommendation, not a research finding. Use it to produce four things: an observable event, a context question, one expectation and one support or follow-up point.

A Gallup report says feedback improves performance about one-third of the time and makes it worse about one-third of the time. (Feedback Is Not Enough) Do not prepare a polished verdict. Prepare a fair test of what happened, what affected the work and what needs to change.

1. Record the event. Write the setting, the behaviour and the work impact. Replace “careless”, “cold” or “unprofessional” with what a colleague could have seen or heard. For example: “The report arrived one day late, so the finance review moved.” One feedback framework identifies delay, vagueness, and assumptions about another person’s thoughts as possible causes of awkward feedback. (How to Give Feedback to Employees in Difficult Conversations)

2. Classify the issue. Mark it as a hard skill or soft skill, then as objective or subjective. An objective failure needs evidence and the expected standard. A subjective concern needs observable signals and careful wording: “I experienced the exchange as dismissive”, not “you are dismissive”.

3. Test the conditions. Ask whether the deadline was realistic, a dependency was missing or the standard was clear. Write the question you will use: “What am I missing about what happened?” A smooth script cannot repair an impossible target. Deep Impact cites a 2005 study in Group & Organization Management about why people experience feedback as threatening or useful. (How to Give Feedback to Employees in Difficult Conversations)

4. Write four cues. Prepare one opening, one context question, one future expectation and one support or follow-up offer. Keep cue words rather than a speech. A useful close is: “Let’s agree the next action, the support you need and when we will check progress.”

A coaching approach can distinguish two-way development conversations from formal, past-focused feedback. (Feedback Is Not Enough) Use ordinary coaching for a workable improvement issue. Consult HR and the relevant policy for repeated failure, serious conduct, discrimination, safety or any process that could affect employment status. The preparation test comes first. Then choose the conversation.

What exact lines should you use during the conversation?

A manager should match the script to the failure, then keep the exchange focused on one observable change, one deadline and one support offer, as SurveyMonkey recommends.

• Missed deadline: “The report arrived one day late, so the finance review moved. I need the report by the agreed time; if a dependency threatens that, tell me before the deadline.” This wording follows Deep Impact’s missed-report example. Add: “What will you do differently on the next report?”

• Repeated mistakes: “I have found the same reporting error more than once. I need the figures checked before submission. What checking step will you add, and when will you use it?” An example involving repeated reporting errors illustrates why a specific correction can be more actionable than a general warning. Its feedback guidance also gives the example of sending a client update before 4 pm with the revised timeline.

• Poor communication: “I did not receive the client update when we agreed. That left the team without the revised timeline. Send the update by 4 pm today, and flag any risk before then.”

• Low-quality work: “The draft contains gaps in the evidence, so I cannot send it for review. Please add the missing sources and resubmit by Thursday. Would a fifteen-minute review of the standard help?”

• Interpersonal concern: “In the last two team meetings, you answered before colleagues finished. I experienced the tone as dismissive, and two people stopped contributing. What was happening for you?”

Use active listening without surrendering the standard. Say, “Tell me what I am missing.” Then say, “I can accept that context without changing the expectation we still need to meet.” One coaching model recommends that managers speak 30% of the time and employees speak 70% of the time, with the discussion focused on what happens next (How to Give Difficult Feedback to an Employee). (Gallup)

If the employee asks, “Why are you hearing this now?”, answer plainly: “I saw an earlier signal and should have addressed it sooner. The recent pattern made the issue clear enough to raise today.”

Close with: “Let’s agree the next action, the support you need and when we will check progress.” This approach can support focused, frequent feedback instead of reserving every concern for a performance review.

What should you say when the employee denies, disputes or resists the feedback?

A manager should treat pushback as a context test, not a contest, because Gallup’s coaching model prioritises listening and two-way conversation over a delivered verdict (Give Feedback Like a Coach). The three common responses are denial of the event, disagreement with the impact, and an explanation involving an unrealistic deadline or blocked dependency.

VoicePrep.ai warns that managers often rehearse only the opening line, leaving them exposed when resistance starts; its four moves are behaviour, impact, response and next step (How to Give Difficult Feedback to an Employee). Prepare the recovery line, not just the first sentence.

What to say when the employee pushes back

Employee response	Manager’s next line	What the line protects
Denial: “That did not happen.”	“We remember it differently. I will explain what I observed, and I want your account before we decide the next step.”	Acknowledges disagreement, returns to the specific event and keeps the concern open.
Disputed impact: “Nobody was affected by it.”	“You did not intend that result. The issue is that the client then asked for escalation, so we need a different approach next time.”	Separates intent from impact and keeps the work consequence visible.
Context or dependency: “The deadline was unrealistic.”	“Tell me which constraint blocked delivery and what we should change next time. We still need an agreed delivery expectation.”	Accepts valid context without abandoning the performance requirement.
Anger or defensiveness: “You are blaming me.”	“I hear that this feels blaming. I want to focus on one behaviour and one next step. If we cannot do that now, let’s pause.”	Names the heat, reduces escalation and protects a focused discussion.
Silence or tears: “I cannot talk about this.”	“I want to handle this properly. Let’s take a short break and agree when we will continue.”	Slows the exchange while preserving a safe follow-up.

Source: How to Give Difficult Feedback to an Employee and Give Feedback Like a Coach.

The deadline row matters because a real dependency can expose a management failure, not employee resistance. Clarify what changes next time, then retain the delivery requirement that remains workable. The anger and silence rows require a pause, not pressure; a pause does not cancel the performance issue.

If the employee asks, “Why are you only telling me this now?”, say: “I should have raised the earlier signal sooner. I am raising the pattern now because it has become clear enough to address.” Own the delay without diluting the concern.

A Gallup report says that only 26% of employees strongly agree feedback helps them do better work, and that feedback improves performance about one-third of the time but makes it worse about one-third of the time (Feedback Is Not Enough). That is why the goal is not agreement or an apology. It is an accurate account, a workable expectation and one next action.

Which phrases and habits derail difficult employee feedback?

A hard-skills/soft-skills feedback matrix can help managers choose wording by separating objective failures from subjective perceptions before the conversation starts. (Give Employees the Right Kind of Feedback at the Right Time)

Q: What if the employee denies the facts?

Do not turn the meeting into a contest over memory. Name the evidence you hold, acknowledge the disagreement and ask for the employee’s account.

Example: “We remember that meeting differently. I will explain what I observed, then I want to understand your view before we agree the next step.”

Return to records, dates, messages or agreed deliverables where they exist. Do not accuse the employee of lying. A denial does not require you to withdraw the performance concern, but it does require you to test whether your evidence is complete. HR and policy requirements vary by workplace, especially where the conversation could affect employment status.

Q: What if the deadline was unrealistic?

Accept a genuine dependency or planning failure without removing the delivery expectation; agree what changes next time and who owns the escalation.

Example: “I accept that the data arrived late and affected your work. If a dependency threatens the next deadline, tell me before it slips so we can reset the plan.”

Ask what was known, when it became known and what warning the employee could have given. Then confirm the workable deadline, support and escalation route in writing. Do not label the employee unreliable if the system created the delay. HR and policy requirements vary by workplace when missed deadlines form part of formal performance management.

Q: When does feedback become formal performance management?

Feedback becomes formal performance management when the organisation’s process requires documented expectations, defined review steps or possible employment consequences. It does not become formal simply because a conversation feels serious.

Use ordinary coaching to clarify a behaviour, its effect and the next action. Consult HR or the relevant policy when the issue involves repeated failure, serious conduct, discrimination, safety, capability concerns or a possible change to employment status. Gallup distinguishes past-focused, one-directional feedback from two-way coaching conversations, but that distinction does not replace a workplace procedure. (Feedback Is Not Enough)

Example: “This conversation is about agreeing the support and standard for the next piece of work. I will explain the formal process separately if that process applies.”

Do not promise confidentiality, invent a warning stage or create a formal record without checking the policy. HR and policy requirements vary by workplace, and UK, EU and US employers may follow different rules.

Q: How should a subjective concern be phrased?

Present a subjective concern as your experience of observable behaviour, not as a fact about the employee’s character or intent.

Example: “In the last team meeting, you answered before Priya finished twice. I experienced the exchange as dismissive, and the discussion stopped. What was happening for you?”

Ask for context. Then agree a visible behaviour, such as allowing the speaker to finish before responding. Avoid “You are cold”, “You intimidate people” or “You have an attitude problem”. Gallup’s matrix separates subjective from objective failure, so the wording should show where your interpretation begins. (Give Employees the Right Kind of Feedback at the Right Time)

HR and policy requirements vary by workplace. A subjective concern should not become a disciplinary finding without evidence, a fair process and the required review.

Q: Should I use a feedback sandwich?

Do not use a feedback sandwich to disguise corrective feedback; state the concern plainly, listen to the employee and agree the next action.

Example: “The report contained errors that delayed the finance review. Let’s identify how you will check the figures before the next submission.”

Give genuine recognition in its own words. Do not attach praise that feels like a cushion or a bargaining tactic. Gallup argues that requested feedback creates a more reciprocal dynamic than assuming unsolicited feedback will land, but managers still need to raise a material concern when their role requires it. (The Most Effective Feedback Is the Kind You Ask for)

HR and policy requirements vary by workplace. A sandwich is not a substitute for the organisation’s recognition, conduct or performance process.

Q: How should I use a manager feedback survey or 360-degree feedback (How to Give Employee Feedback That Actually Lands)?

Use a manager feedback survey or 360-degree feedback to explore patterns as evidence. Do not use it as a surprise prosecution during a performance review (How to Give Employee Feedback That Actually Lands).

Start with the theme and its work effect. Protect the source and follow the survey’s stated rules.

Example: “The feedback shows a repeated concern about interruptions in meetings. I want to discuss the behaviour I have observed and hear your context.”

Do not present anonymous comments as proven facts. Do not dump every response into the meeting. Compare the feedback with direct observations, agreed standards and the employee’s account. A performance review can set a wider development plan; it should not hide an urgent issue that needs prompt discussion.

Gallup reports that its February 2022 Gallup Panel survey included 14,705 U.S (Give Feedback Like a Coach). adults and had a margin of sampling error of ±1.6 percentage points at the 95% confidence level (Give Feedback Like a Coach). (Give Feedback Like a Coach) That evidence describes a survey sample, not proof that every comment about an individual is accurate.

HR and policy requirements vary by workplace. Check consent, confidentiality, retention, reviewer access and formal-process rules before using survey or 360-degree data (How to Give Employee Feedback That Actually Lands).

Suggested slug: /how-to-give-difficult-feedback-to-an-employee

How should you rehearse the feedback out loud before the meeting?

A manager may find it useful to use three spoken rehearsal passes, since some feedback guidance notes that managers often practise only the opening and may remain unprepared for pushback.

Round one: follow the real conversation. Use the full wording. Read the opening. State the behaviour and its impact. Stop speaking. Ask for the employee’s view. Close with one action, one deadline and one support offer.

Do not restart because your tone sounded imperfect. The aim is a complete, usable exchange. Say the words you will use in the Friday performance meeting, not a polished speech about management principles.

Leave a pause after the impact statement. Notice whether you fill it with excuses, extra evidence or an apology. A quiet pause gives the employee room to explain context.

Round two: remove the script. Keep cue words only:

• behaviour
• impact
• listen
• action
• deadline
• support

Speak from those prompts. This exposes brittle wording. Memorised prose often collapses when the employee asks an unexpected question. Cue words preserve the structure while allowing a natural response.

Round three: practise pushback. Ask a colleague to role-play denial, anger, silence and a counterexample. If nobody is available, write the employee’s likely response and answer it aloud. Coaching skill can be developed through role-play or real-life environments over time, rather than treating one rehearsal as mastery.

Use this recovery line:

“I hear the context, and the expectation still needs a workable plan.”

Then practise responses to:

• “That is not what happened.”
• “The deadline was unrealistic.”
• “You are blaming me.”
• “Why are you only telling me this now?”

Listen for rushing, hedging, repeated apologies, raised volume and over-explaining. Those signals matter more than perfect phrasing. Repeat the recovery line until you can deliver it warmly and firmly.

Finish with the written follow-up. Record the behaviour discussed, agreed change, deadline, support and check-in point. SurveyMonkey describes feedback as prepare, frame, deliver and follow up. For corrective feedback, a manager may consider a check-in within 1–2 weeks, adjusting the timing to the circumstances. For situation-specific workplace or employment guidance, consult a qualified HR professional or employment lawyer. Developmental follow-up should align with the performance-review cycle. The follow-up records the agreement. It does not replace your organisation’s formal performance-management process where that process applies.

Razen Rehearsal Sandbox: The 14 June client-call debrief

At 10:00 on 14 June, Alex must address Ben interrupting Jamie twice during a renewal call. The client then asked for Alex, and the renewal decision is due Friday, so Alex needs to test what happened and set one visible behaviour before the next call.

Setting. A private meeting room after the client renewal call. Alex, Ben and Priya, the HR partner, are present. Priya attends because Ben asked for a witness after an earlier feedback conversation.

Cast

• Alex, Manager giving the feedback. At stake: Must protect the client renewal without turning the meeting into a verdict.
• Ben, Employee receiving the feedback. At stake: Needs to explain the interruptions and avoid being labelled a performance problem.
• Priya, HR partner testing the process. At stake: Must keep the discussion fair while ensuring the concern is addressed.

The Wrong Way

Alex: I want to discuss the renewal call. You interrupted Jamie twice, the client asked for me, and it damaged the conversation.

(Reads from notes; keeps both hands flat on the table.)

Ben: I didn't interrupt her twice. I came in when she paused.

(Leans back; answers quickly and tightens his jaw.)

Alex: The recording is clear. Jamie was presenting the figures, and you cut across her both times.

(Raises one finger for each example; does not pause.)

Priya: The call log also shows the client requested escalation at 10:18.

(Glances at her laptop; adds evidence in a clipped tone.)

Ben: So this is a case against me, then? I was trying to stop the wrong figure going to the client.

(Folds his arms; voice gets louder on the last sentence.)

Alex: That is not what I said. You need to let people finish. We have covered this before.

(Interrupts him; points briefly towards the door.)

Priya: We should record that the expectation was already explained.

(Starts typing; avoids Ben's gaze.)

Ben: Fine. I'll say nothing on the next call. Is that what you want?

(Smiles without warmth; pushes his chair back.)

Why it fails. Alex opens with a prepared behaviour-and-impact statement, but the line “The recording is clear” turns a disputed event into a prosecution before Ben gives his account. Priya’s added evidence and Alex’s “We have covered this before” make the meeting about blame and history, so Ben offers compliance in words rather than a workable next action.

The Right Way

Alex: I want to review the 14 June renewal call. You spoke over Jamie twice while she presented the figures, and the client then asked for me. Before we decide what to change, tell me what was happening for you.

(Uses a low pace; looks at Ben, then leaves both hands open.)

Ben: I thought she was about to read the old renewal figure. I was trying to stop it before the client heard it.

(Looks down at the table; voice stays guarded but steady.)

Alex: That context matters. I also failed to set who would handle corrections before the call. The interruption still stopped Jamie finishing and made the client ask for escalation.

(Nods once; keeps the final sentence firm and slower.)

Priya: Was the correction process written anywhere before the call, or were you both working from assumptions?

(Turns her laptop towards herself; asks without looking for blame.)

Ben: It wasn't written. I saw the draft figures change ten minutes before we joined.

(Uncrosses his arms; points once at the call notes.)

Alex: I accept that dependency, and I still need one behaviour from you: let the speaker finish, then raise a correction. If the figure is urgent, put it in the chat while they speak.

(Writes the two options down; holds eye contact on “still need”.)

Ben: All right. For Friday's call, I'll use the chat for urgent corrections and wait until Jamie finishes.

(Nods once; places both feet flat on the floor.)

Alex: I'll send roles and the final figures by 9:00 Friday, and we will check the recording together after the call. That is the plan, not an apology exercise.

(Closes the notebook; speaks plainly without softening the last sentence.)

Why it lands. Alex keeps the concern visible while asking for Ben’s account, then accepts a real process failure without removing the performance expectation. Priya changes the outcome by testing whether the standard and dependency were clear. The cost is shared responsibility: Alex must fix the call setup, while Ben must use a visible correction behaviour and accept a follow-up review.

<aside class="razen-coach-card" data-razen-scenario="the-14-june-client-call-debrief"> <p class="razen-coach-card__title"><strong>Practice this live.</strong></p> <p><a class="razen-coach-card__button" href="https://razenai.com/coach?scenario=the-14-june-client-call-debrief&amp;article=practise-hard-feedback-report&amp;utm_source=razen_blog&amp;utm_medium=rehearsal_sandbox&amp;utm_campaign=practise-hard-feedback-report">Click here to boot up the Razen AI voice coach for this exact scenario.</a></p> </aside>

Delivery playbook

Tone shifts

• Start factual and unhurried when naming the 14 June call; do not sound like you are reading a charge sheet.
• After Ben explains the changed figures, shift from investigative to joint problem-solving without lowering the expectation to let Jamie finish.
• Return to a firm, practical tone on “I still need one behaviour from you” and the Friday check-in.

Pause placement

• Pause for 3 seconds after “tell me what was happening for you” so Ben can give his account before you defend the impact.
• Pause for 2 seconds after “The interruption still stopped Jamie finishing” before naming the expected behaviour.
• Pause for 3 seconds after Ben agrees to use the chat, then state the 9:00 Friday preparation commitment.

Physiological cues

• Before opening, exhale slowly and keep both feet on the floor; suppress the urge to tap the notes when Ben denies the interruption.
• When Ben mentions the changed figures, nod once and loosen your jaw before answering; this shows you heard context without conceding the standard.
• Keep your gaze on Ben for the words “still need,” then look at the written two-step plan rather than staring him down.

Recovery moves

• If Ben says, “That is not what happened,” say: “We remember it differently. I will explain what I observed, and I want your account before we decide the next step.”
• If Ben says, “You are blaming me,” say: “I hear that this feels personal. I am addressing two interruptions and the next call behaviour, not your character.”
• If the room heats up, say: “I want to handle this properly. Let’s take five minutes and continue at 10:20, with the same two questions: what happened, and what changes Friday.”

Frequently asked questions

What is the best opening sentence for difficult feedback to an employee?

Start with the purpose, the specific behaviour and why it matters: “I want to discuss yesterday’s client call because you interrupted Jamie twice, and the client then asked for an escalation.” Avoid personality labels or guesses about intent.

What should I say if the employee denies doing it?

Do not argue over motives. Say, “We remember it differently. I will explain what I observed, and I want your account before we decide the next step.” Then return to the behaviour and the expectation you need to set.

How do I give feedback about a subjective issue such as tone?

Separate perception from fact. Say what you observed, describe the effect and explain your perception: “I experienced the response as dismissive.” Ask what was happening for the employee, then agree on a visible behaviour for future conversations.

Should I use the feedback sandwich?

Avoid using praise to disguise corrective feedback. State the concern plainly, explain its impact, listen to the employee’s context and agree one next action. Specific recognition belongs in its own conversation or alongside a genuine strength that relates to the work.

How many times should I rehearse difficult feedback?

Use three passes: one with the real script, one from brief cue words and one against a tougher response such as denial or anger. Listen for rushing, hedging, excessive apology and over-explaining rather than chasing a perfect performance.