Prepare constructive feedback for a defensive top performer

Turn observed collaboration issues into a direct, objective conversation guide that prevents defensiveness and sets clear behavioral standards.

You getMeeting Opening Script, the Core Issue and handling Defensiveness

Prompt

Prompt
Act as an experienced executive coach helping a manager deliver tough feedback to an employee who delivers great individual work but dismisses peers or resists critique.

- Separate hard results from interpersonal impact using clear, factual observations.
- Draft an opening script that acknowledges their technical strengths without blunting the core performance issue.
- Include three anticipated defensive reactions and word-for-word calming redirects.
- Specify one clear behavioral expectation and a two-week follow-up checkpoint.

Output format:
1. Meeting Opening Script
2. The Core Issue (Situation, Behavior, Impact)
3. Handling Defensiveness (3 objections and manager responses)
4. Agreed Next Steps & Check-in Date

Notes on the employee and recent incidents are below:

Example output

Example for: senior engineer who interrupts peers during design reviews and misses pull request comments

1. Meeting Opening Script

"Alex, thanks for sitting down with me today. You consistently hit every feature deadline and your technical execution on the checkout refactor was exceptional. I invited you here because I want to talk about how we collaborate during technical reviews. For you to keep growing into a principal role, how you guide the team matters just as much as your code."

2. The Core Issue (Situation, Behavior, Impact)
  • Situation: During Tuesday's architecture review for the payment gateway.
  • Behavior: When Jordan raised a question about retry logic, you cut them off mid-sentence and said 'that's basic, read the spec.'
  • Impact: It shut down critical review, left junior engineers reluctant to speak up, and makes code reviews adversarial rather than collaborative.
3. Handling Defensiveness
  • Objection: "I just want to move fast, and people ask questions that waste time."
    Manager Response: "Speed matters, but catching flaws early requires open discussion. Cutting people off slows us down later when unasked questions turn into production bugs."
  • Objection: "My metrics are higher than anyone else on the team."
    Manager Response: "Your individual output is not in question here. The expectation for senior engineers is making the entire team faster, not just yourself."
  • Objection: "Jordan is being too sensitive."
    Manager Response: "I am the one raising this, not Jordan. I observed the exchange myself, and our team standard requires listening fully before responding."
4. Agreed Next Steps & Check-in Date
  • Expectation: Allow peers to finish their thoughts during reviews; acknowledge PR comments constructively within 24 hours.
  • Check-in: Two weeks from today on Thursday at 2:00 PM to review peer feedback from upcoming sprints.
Written by AI from this prompt. Your results will vary.

Paste your rough notes about recent interactions after the prompt in ChatGPT, Claude, or Gemini. As a follow-up, ask the model to roleplay the conversation with you so you can practice your delivery.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management
Leadership & Management

Build a thirty-sixty-ninety day onboarding plan

Generate a clear, phased milestone roadmap for incoming team members to eliminate ambiguity. Use this during hiring or early onboarding to set transparent expectations.

Leadership & Management

Set team communication norms to stop after-hours work

Establish clear communication guardrails that protect personal time without slowing down urgent operational needs. Use this to reduce team burnout and reset expectations around late-night pings.