Case 49

Preparing a Difficult Conversation

Scenario

You manage a team of analysts at Greystone Advisory. One senior analyst has missed several deadlines and has been short with colleagues. You need to raise it this week.

Why this framework

Uses full PINPOINT because the consequence is higher: adds a professional stance, examples, self-checks, your own review before use, and a plan to tweak and test.

Example context

Incident notes (manager's own records), senior analyst Jordan Ellis, Greystone Advisory: - 4 September 2026: monthly client report for Harlow Retail due 5pm, sent 10am next day. Client account lead emailed asking why. - 18 September 2026: same report again late, sent 2pm next day. Client noticed and mentioned it on the 22 September call. - 2 October 2026: data model handover to junior analyst Mia Chen due, delivered 7 October without notes; Mia lost two days rebuilding the workings. - 14 October 2026, team meeting: when Raj Patel asked about the model assumptions, Jordan said "if you'd read it you wouldn't need to ask" in front of the team. Raj raised it with me afterwards. - 21 October 2026: Mia told me in our one to one she now avoids asking Jordan questions. - Jordan's work quality when delivered remains strong; last review rated "strong" on technical analysis. Performance policy (extract): managers should raise concerns early and informally, using specific examples; agree clear expectations and a review date; the employee may give their view; if no improvement after an agreed period (usually 4 to 8 weeks), a formal process may follow; notes of the meeting are shared with the employee.

Prompt

Purpose: Help me prepare for a conversation with a team member about missed deadlines and how they have treated colleagues, so we agree a way forward.

Context: Use the attached notes of the specific incidents and dates, and our performance policy. Keep to what happened; do not guess at the person's motives or private circumstances.

Narrow the ask: Give me
1. A clear opening of two or three sentences.
2. The specific examples to raise, in order.
3. Questions to understand their side.
4. Likely reactions and calm ways to respond.
5. What a good outcome looks like, and how we will follow up.
Stop and ask me if the incident notes are too vague to cite.

Persona and role: Act as an experienced, fair-minded people manager. Be honest about the problem and respectful of the person.

Example of what good looks like: "On the 4th and the 18th the client report was late, and the client noticed. I want to understand what got in the way." Example of what bad looks like: "Your attitude has been a problem lately."

Check your work: For each material claim, label it as [Verified Source], [Inference], [Assumption], or [Unverified]. Cite the source where available. If an unverified or assumed point could materially change the conclusion, flag it for review rather than guessing. Confirm every example matches the incident notes.

Before I use it: I will check the plan with HR before the meeting.

If the plan feels wrong when I rehearse it, I will change one thing at a time, starting with the opening.

Materials (pasted here in place of the attachments):
Incident notes (manager's own records), senior analyst Jordan Ellis, Greystone Advisory:
- 4 September 2026: monthly client report for Harlow Retail due 5pm, sent 10am next day. Client account lead emailed asking why.
- 18 September 2026: same report again late, sent 2pm next day. Client noticed and mentioned it on the 22 September call.
- 2 October 2026: data model handover to junior analyst Mia Chen due, delivered 7 October without notes; Mia lost two days rebuilding the workings.
- 14 October 2026, team meeting: when Raj Patel asked about the model assumptions, Jordan said "if you'd read it you wouldn't need to ask" in front of the team. Raj raised it with me afterwards.
- 21 October 2026: Mia told me in our one to one she now avoids asking Jordan questions.
- Jordan's work quality when delivered remains strong; last review rated "strong" on technical analysis.
Performance policy (extract): managers should raise concerns early and informally, using specific examples; agree clear expectations and a review date; the employee may give their view; if no improvement after an agreed period (usually 4 to 8 weeks), a formal process may follow; notes of the meeting are shared with the employee.

Example output from ChatGPT

Conversation Plan: Jordan Ellis: Performance and Conduct

Medium consequence: HR review required

Purpose: Address missed deadlines and the impact of Jordan's communication on colleagues, hear Jordan's perspective, and agree measurable improvements.

Approach: Informal performance conversation, consistent with Greystone Advisory's policy. Recognise Jordan's strong technical work while addressing delivery reliability and respectful communication.

All incident examples below have been checked against the supplied manager's notes. Claims are labelled by evidence status. Proposed actions are recommendations, not established facts.

1. Opening: what to say

Jordan, I want to discuss some concerns about missed deadlines and how communication within the team has been working. Your technical analysis remains strong, and I value that contribution, but there have been specific incidents affecting clients and colleagues that we need to address.

I want to hear your perspective, understand what happened, and agree on clear expectations and a fair way forward.

[Verified Source] Jordan's last review rated technical analysis as "strong". The incident notes document three delayed deliverables and concerns about interactions with colleagues.

2. Specific examples to raise, in order

Present the examples chronologically. Separate observed events from colleagues' accounts and avoid treating reported feelings as proven intentions.

DateWhat to sayEvidence
4 Sep"The Harlow Retail report was due at 5pm and was sent at 10am the next day. The client account lead asked why."[Verified Source]
18 Sep"The same report was late again, sent at 2pm the following day. The client raised it on 22 September."[Verified Source]
2 to 7 Oct"The handover to Mia was due on 2 October and delivered on 7 October without notes. Mia spent two days rebuilding the workings."[Verified Source]
14 Oct"When Raj asked about model assumptions, you said, 'if you'd read it you wouldn't need to ask,' in the team meeting. Raj raised it afterwards."[Verified Source]
21 Oct"Mia told me in our one-to-one that she now avoids asking you questions."[Verified Source, reported by Mia]

[Inference] These incidents suggest two areas requiring attention: delivery reliability and the way Jordan's communication affects colleagues.

Do not claim that Jordan deliberately delayed work or intended to discourage colleagues. Neither is established by the notes.

3. Questions to understand Jordan's side

  • "Can you walk me through what happened with the two September reports?"
  • "Were there competing priorities, unclear expectations or dependencies that affected the deadlines?"
  • "What happened with the model handover, including the missing notes?"
  • "How do you remember the exchange with Raj?"
  • "Mia has said she is hesitant to ask questions. What is your perspective on how the two of you work together?"
  • "What support or changes would help you meet these expectations consistently?"

Allow Jordan to respond to each incident before moving to conclusions.

4. Likely reactions and calm responses

These are possible reactions, not predictions of Jordan's behaviour.

Defensiveness: "My work is always good."

"Your technical quality is a strength. We also need timely delivery and effective collaboration. Both matter."

Disagreement: "That's not what happened."

"I want to hear your account. Let's work through the specific incident and identify anything the notes may have missed."

Blaming colleagues: "They should know this already."

"You may have valid concerns about how questions are raised. We can address those separately, but everyone still needs to be treated respectfully."

Distress or withdrawal: Silence or becoming upset.

"I understand this may be difficult to hear. We can take a moment. I want you to have a fair opportunity to respond."

5. What a good outcome looks like

[Recommendation] Agree a six-week improvement period, subject to HR approval. Six weeks sits within the policy's usual four-to-eight-week range.

AreaProposed expectationHow to check
DeadlinesMeet agreed deadlines or flag a risk early, with a revised planDelivery tracker and weekly check-ins
HandoverProvide the agreed model workings, assumptions and supporting notesReceiving colleague confirms required materials are available
CommunicationRespond respectfully to questions, including when disagreeingReview specific interactions and any reported concerns
SupportIdentify workload, prioritisation or process barriers and agree supportWeekly manager discussion

Proposed follow-up timeline

  1. Meeting day: Hear Jordan's response and agree expectations and support.
  2. Within two working days: Share a factual meeting record with Jordan, inviting corrections. This timing is proposed, not prescribed by the policy.
  3. Weekly: Review deadlines, handovers, communication and support needs.
  4. At six weeks: Assess progress against the agreed expectations and record the outcome.

[Verified Source] The policy requires clear expectations, a review date, an opportunity for the employee to respond, and meeting notes shared with the employee. It states that a formal process may follow if improvement is insufficient after the agreed period.

[Recommendation] Close with:

"I want you to succeed here, Jordan. You have strong technical skills, and I'd like us to build on those. We need to see dependable delivery and respectful collaboration alongside that quality. Let's agree what will change, what support you need, and when we'll review progress."

6. Checks before the meeting

HR and evidence review

  • Confirm report deadlines and actual submission timestamps.
  • Check the handover requirement, including whether supporting notes were specified.
  • Verify the 14 October quotation and distinguish Raj's account from independently observed facts.
  • Discuss how to handle Mia's feedback fairly and confidentially.
  • Agree the improvement period, measures and potential next steps with HR.

[Unverified] The incident notes are sufficiently specific to prepare this conversation, but they are the manager's records rather than independently corroborated evidence. The exact reporting timestamps, handover requirements and disputed accounts should be verified where possible.

Recommended result: Jordan understands the concerns, has been heard, knows exactly what needs to improve, and leaves with a documented and achievable plan. The meeting should establish accountability without prejudging the outcome or making a formal disciplinary finding.