Script a Difficult Conversation With an Underperforming Employee

You get a ready-to-use meeting script with an opening line, factual examples, calm replies to likely pushback, one agreed next step and guidance on when to bring in HR.

Prompt

Prompt
Act as an experienced HR business partner who coaches managers through hard conversations.

Help me script a performance conversation with an underperforming employee. First ask me these in one message, then wait for my answers:
1. What is their role, and how long have they been in it?
2. What 2-3 specific problems have you seen, with dates or numbers?
3. What have you already tried (feedback, training, warnings)?
4. What outcome do you want from this meeting?

Rules:
- The opening line states the purpose in under 25 words, with no small talk or praise sandwich.
- Each example describes an observable action or result with a date or number, never a personality trait.
- Give 3-4 likely pushback lines, each with a calm reply under 40 words that neither argues nor backs away from the facts.
- The next step has an owner, a measurable target and a review date.

Output format:
1. Opening line
2. The facts (bullets)
3. Two open questions to ask them
4. Pushback table: They might say | You respond
5. Agreed next step
6. When to involve HR

This is not legal advice; if a formal warning, dismissal, health issue or discrimination complaint is possible, talk to HR or an employment lawyer before the meeting. End by naming any gaps in my facts.

Example output

At a glanceDaniel's performance gap at a glanceCurrent figures against team targets, from the meeting script
Avg first response, March-April
9 hours
Team target 4 hours; Daniel had 3.5 in January
QA score average since 1 March
68%
Across 12 reviewed tickets; pass mark is 80%
Interim target by 31 May
5 hours, 75%
Then 4 hours and 80% by 30 June

Example for: a support team lead talking to Daniel, a customer support agent of 14 months whose response times and QA scores have dropped.

1. Opening line

"Daniel, I want to talk about your ticket response times and QA scores over the last six weeks, and agree a plan together."

2. The facts
  • Average first response time was 9 hours in March and April, against a team target of 4 hours and your own 3.5 hours in January.
  • QA scores averaged 68% across 12 reviewed tickets since 1 March; the pass mark is 80%.
  • On 18 April, three priority tickets sat unassigned in your queue for over a day.
  • We discussed response times in our 1:1 on 22 March and agreed you'd flag if your queue got too heavy.
3. Two open questions
  • "What's changed for you since January?"
  • "What would help you get back to the 4-hour target?"
4. Pushback and calm responses
They might sayYou respond
"Everyone's slow, the queue is huge.""Volume is up about 10% for the whole team. Others are averaging 4.5 hours, so I want to understand what's different for you."
"QA reviewers just pick on me.""I'm happy to go through two of the reviews with you. The scores came from three different reviewers, so I'd like to look at the patterns."
"Nobody told me this was a problem.""We talked about response times on 22 March. I should have followed up sooner, and that's why we're here now."
"I've had stuff going on at home.""Thank you for telling me. Would it help to talk about support? We can look at options with HR while still agreeing a plan for the work."
5. Agreed next step

Daniel brings first response time down to an average of 5 hours and QA to 75% or higher by 31 May, then 4 hours and 80% by 30 June. You hold a 15-minute check-in every Friday. Formal review: 30 June.

6. When to involve HR
  • Before the meeting, if this might lead to a written warning or formal improvement plan.
  • Straight after, if Daniel mentions health, caring duties, stress or unfair treatment.
  • If targets are missed at the 31 May check-in.

Gaps in your facts: you have no written record of the 22 March conversation, and you haven't checked whether Daniel's ticket mix is harder than the team average. Confirm both before the meeting.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking for dates and numbers first keeps the script factual, which makes the talk harder to dispute and fairer to the employee.
  • Pushback replies capped at 40 words stop the manager from over-explaining or arguing in the moment.
  • Requiring an owner, target and review date turns the meeting into a trackable plan, not just a vague warning.

Use before a one-to-one where performance has slipped. Have dates, numbers and past feedback ready. Works in ChatGPT, Claude or Gemini; answer its four questions in one reply.

Common edits

  • Ask for a shorter version to use as talking points on a single index card.
  • Add a request for a follow-up email under 100 words that confirms the agreed plan in writing.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in HR & Management