You need to give feedback to someone who argues or shuts down.
Sample opening: I want to talk about the feedback itself and also how our feedback conversations have been going.
Avoid saying: You always get defensive.
Manager script library
Use these examples to prepare for feedback, poor performance, defensiveness, documentation, PIPs, reviews, bad news, and other workplace conversations.
Manager script examples are useful when they show exact wording, not abstract advice. Start with a short opening, name the behavior and impact, set an expectation, prepare for pushback, and follow up in writing when needed.
Free preview. $9 full script pack. No account required.
Script categories
Include branches for disagreement, unfairness, blame, other people do it too, shutdown, emotion/crying, fine whatever, and going off-topic.
Script builderInclude expectations not being met, observable examples, impact, support offered, improvement timeline placeholder, check-in plan, and escalation placeholder.
Script builderInclude vague concern to observable rewrite examples and in-the-moment one-liners.
Script builderInclude incident note, coaching note, follow-up language, too vague vs better rewrites, documentation risks, and missing facts checklist.
Script builderInclude what you said, what they said, what to say next, why it works, and 5-7 branch responses for likely pushback.
Script builderInclude opening, purpose, expectations, support, timeline/check-ins, questions, close, follow-up, and policy guardrails. Do not decide whether the PIP is appropriate or legal.
Script builderInclude friendly recap, neutral/professional recap, formal documentation-oriented recap, short text/Slack version if appropriate, and subject line options.
Script builderInclude results acknowledgment, behavior concern, team/customer impact, reject “I’m just direct” without debating personality, behavior expectation, and cautious policy-safe consequence language.
Script builderInclude written review paragraph, constructive version, direct version, meeting script, next-cycle goals, and avoid vague review language table.
Script builderInclude short announcement script, longer meeting script, email version, likely questions and answers, what not to say, and follow-up message.
Example scripts
Sample opening: I want to talk about the feedback itself and also how our feedback conversations have been going.
Avoid saying: You always get defensive.
Sample opening: I want to review the gap between the expectation and what has been happening, then agree on what changes next.
Avoid saying: You need to do better.
Sample opening: I want to talk about a few meeting behaviors I have observed and the effect they are having on the team.
Avoid saying: You have a bad attitude.
Sample opening: I want to recap what we discussed, the expectation we reviewed, and the next step we agreed to.
Avoid saying: This proves they do not care.
Sample opening: I hear that you see it differently. I still need us to focus on the expectation going forward.
Avoid saying: Stop arguing.
Sample opening: This meeting is to review the improvement plan, answer questions, and make sure expectations and timelines are clear.
Avoid saying: This is just a formality.
Sample opening: Thanks for meeting today. We discussed the missed deadlines, the expectation, and our next check-in.
Avoid saying: As I warned you earlier...
Sample opening: Your results matter, and so does how those results are achieved.
Avoid saying: You are too valuable for this to matter.
Sample opening: Missed deadlines on recurring reports created rework for the team. The expectation is earlier escalation when timelines are at risk.
Avoid saying: Needs a better attitude.
Sample opening: I want to be direct about the decision, explain what it means, and then make space for your questions.
Avoid saying: I wish I did not have to tell you this.
Adapt any script
Every script on this page should be adapted before use. Replace vague labels with observable behavior. Add one specific example. Name the impact on the work, customer, or team. Set one clear expectation. Prepare for pushback. Follow up in writing when the conversation affects performance, behavior, or documentation.
Most difficult employee conversations break down before the manager gets to the actual standard. The opening is too vague, the example is too broad, or the employee pushes back and the manager starts defending the feedback instead of guiding the conversation. Cabinet pages are built around a different assumption: a manager needs a usable first sentence, a clear middle, a calm answer to pushback, and a follow-up note that does not sound emotional.
That is why these assets link directly into specific script builders. If your issue is repeated misses, the poor performance conversation script is a better next step than a general article. If the employee argues with feedback, use the defensive employee feedback script or the feedback pushback script.
A useful manager script includes the opening line, specific issue, impact, expectation, questions, pushback response, close, and follow-up note.
Use it as preparation, not a performance. The goal is to enter the conversation with clear language and a steady structure.
Use Cabinet’s defensive employee feedback script or feedback pushback script, depending on whether you need the opening conversation or the next response after they disagree.
Cabinet helps managers prepare clear, professional language for workplace conversations. It does not replace company policy, your HR partner, or legal counsel. For situations involving termination, PIPs, accommodations, medical leave, discrimination, retaliation, pay, benefits, safety, or protected activity, confirm the process with the appropriate HR or legal resource.